Bug #13081
Alphabetical order in "Allowed excludefields"
| Status: | Needs Feedback | Start date: | 2011-02-16 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Usability | |||
| Target version: | TYPO3 6.0 | |||
| Tags: | ||||
| Votes: | 0 |
Description
When creating a begroup (or beuser) there is in Access tab the field "Allowed excludefields".
Now everything is in alphabetical order. Before they were in kind of groups, one extension properties in one group then the next and so on. This was better and easier to use in my opinion. (Though there was no indicator to which extension the property belonged.)
This alphabetical order is very hard to cope with since many extensions + core use same terms. There is this nice question mark button that gives more info - thanks for that improvement.
Even the size of this field is smaller nowadays, this makes it a bit harder too.
So my suggestion would be:
- bigger field
- one extension properties in one group + extension key indicator in the beginning, for example:
CORE - Page: files
EXT - pageteaser, Page: files
EXT - pageteaser, Page: teaser
and so on. And question mark info button would of course be there too.
Related issues
| related to Usability Team - Suggestion #11559: make "checkbox" default value for accessListRenderMode in... | Needs Feedback | 2010-12-17 | ||
| related to Usability Team - Bug #10587: TCA Tree icons | Accepted | 2010-11-02 | ||
| related to Usability Team - Feature #30013: TCA tree add filter "check" | Needs Feedback | 2011-09-19 |
History
Updated by Katja Lampela over 2 years ago
Sorry, in this issue everything seemed to go wrong.. wrong category, should have been in suggestions (which is odd, I created this issue in that page, but I guess the category has to be chosen separately, sorry).
And I notice now - too late - that there are extensions that have this indicator and thus are grouped together, like the great tt_news.
So, probably this is just deficient settings in some extensions.
Updated by Jens Hoffmann over 2 years ago
- Category set to Usability
- Status changed from New to Needs Feedback
- Priority changed from Should have to Could have
- Target version set to TYPO3 4.6
THX for the Info.
Could someone validate this?
@Steffen K. .. haven't you been working on that?
Greez Jens
Updated by Jens Hoffmann over 2 years ago
@Katja Lampela .. can you add a Screenshot for that, please? :)
Updated by Steffen Gebert over 2 years ago
Question mark info depends on the extension, as it has to provide Context Sensitive Help text.
I don't know, if we can access the extension key at this place. Currently, we read the record type from TCA and show all fields, which are defined as excludefields.
The only change to 4.4 is the lost grouping, instead it's alphabetically sorted now (before it started with Page, Page content and then all records). I assume the change origins in the TCA changes by Joey.
Updated by Jens Hoffmann over 2 years ago
Can you somehow post the difference?
Can you post a "before" and "after" screenshot?
I don't get it really - so do I fear .. sorry.
I think it's important to have Groups there.
If there is a relation, that should be visible. :)
Greez Jens
Updated by Jens Hoffmann 12 months ago
- Subject changed from Allowed excludefields to Alphabetical order in "Allowed excludefields"
Updated by Benjamin Mack 12 months ago
- File Allowed_Exclude_Fields.PNG added
- Target version changed from TYPO3 4.6 to TYPO3 6.0
Now this is grouped and looks nice. Nothing to change then, right?
If so, Jens, please close this issue.
Updated by Jens Hoffmann 12 months ago
Can we make this as "Tree" ?
Updated by Jens Hoffmann 12 months ago
I mean, just like this example #10587 .