Task #44340: Improve UI
Multiple selection for "Allowed CE"
|Priority:||Could have||Due date:|
|Assignee:||Tobi Ferger||% Done:||
|Category:||Layout and UI||Spent time:||-|
|TYPO3 Version:||6.0||PHP Version:|
In the extension "gridelements" and in the backend_layouts there is for each column you can edit a field named "Allowed CE".
If you don't know the CType possibilities it's hard to select the right one.
Maybe a selection of all possible CEs will be nice.
Updated by Jo Hasenau over 1 year ago
- Status changed from New to Needs Feedback
- Assignee set to Thomas Loeffler
Actually it would be nice to implement the feature "allowed CE" at all ;-)
Currently there's only a dummy field without any functionality, but it's still planned to implement it.
We are discussing if the exclusion should happen on backend or frontend level though.
Frontend level would have the advantage, that you could still insert elements in the backend, which would just not be rendered in the frontend.
Backend level would be more restrictive but much more complicated to implement as well, since we would have to care about allowed elements for each and every transaction between grids, including Drag & Drop actions.
Updated by Thomas Loeffler over 1 year ago
Hehe, I didn't know that it's only a dummy field. So long for testing. ;)
I would prefer the frontend level implementation.
Updated by Jo Hasenau over 1 year ago
- Assignee changed from Thomas Loeffler to Jo Hasenau
So do I ...
Maybe we can just implement it on frontend level and implement a backend level check later on.
Backend level could be activated by a TSconfig switch then.
The problem with backend level implementation would be:
What to do with elements that have been inserted to the wrong column already?
Should we remove them automatically?
Should we move them to the unused column instead?
If no one complains, I will start with frontend level implementation tomorrow.
Updated by Rocco Georgi about 1 year ago
I'd prefer the FE thing too.
Could we additionally render "wrongly placed items" (those that are not allowed in the FE at their current position) in the BE with an overlay or some other hint that shows that the item will not appear in FE? Otherwise this might cause a lot of confusion for users (why does my content not show up?).
Updated by Bernhard Eckl 11 months ago
I have one simple question, is the »allowed feature« only not implemented in ext gridelements or is it also not implemented in the normal backend layout (core feature)? I couldn’t find anything on what to type in there e.g. to jus allow a text element or custom content element (I use the wec_contentelements API). Thank you very much!
To your discussion, I would also like that an editor would not be able to place not allowed content elements in the backend column as well, this would be less confusing for editors.
Updated by Jo Hasenau 11 months ago
The "allowed CE" feature will only be available when you install grid elements.
The original wizard for backend layouts does not contain "allowed CE", so they are not available anyway.
When the feature will be provided by grid elements it will be available for both, backend layouts and grid elements though.
Updated by Steffen Müller 8 months ago
Although the FE solution seems to be easier from developers point if view, the BE solution is far more convenient for editors and would push the page module to a new level of usability.
Updated by Jo Hasenau 8 months ago
- TYPO3 Version set to 6.0
Currently the deal is: If someone buys the feature we presented as a reward at our startnext project page, we will definitely go for the convenient BE solution, otherwise we will do the FE solution only unless there will be time and/or money left before feature freeze.