You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The table should scroll horizontally within a container/itself (not the whole backend)
TH and TD should feature word-wrap: break (CSS3)
This should be patched to both, bake templates and core admin index view templates
(3. Developers should be advised to not add too much unnecessary fields to admin index tables view templates)
As for croogo 3.x there should be a way to hide/unhide fields in index views and it should only show like id, created, modified, 3-5 further fields (discuss) and autohide the rest (to be unhidden by the user on request). The changes above (1. and 2.) should still go in.
I'll eventually have to patch at least the bake templates for feature 1. and 2. myself and supply that as a PR later this or coming month.
The text was updated successfully, but these errors were encountered:
ionas
changed the title
2.2 UI Bug: long tables (lots of fields or long unbreakable field data) hide action buttons
2.2 admin UI bug: long tables (lots of fields or long unbreakable field data) hide action buttons
Apr 23, 2015
That hide/unhide feature could be an third party plugin, since you should be able to hook into the model/table and update the $_displayFields variable per request. If Croogo is ported to Cake3, I'll take a look. Like that idea.
This should be fixed in two ways:
This should be patched to both, bake templates and core admin index view templates
(3. Developers should be advised to not add too much unnecessary fields to admin index tables view templates)
As for croogo 3.x there should be a way to hide/unhide fields in index views and it should only show like id, created, modified, 3-5 further fields (discuss) and autohide the rest (to be unhidden by the user on request). The changes above (1. and 2.) should still go in.
I'll eventually have to patch at least the bake templates for feature 1. and 2. myself and supply that as a PR later this or coming month.
The text was updated successfully, but these errors were encountered: