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
Not sure if this is the right place or if that should be a TYPO3 core feature.
We're using mutliple extensions providing content elements that should only be used in specific backend layouts.
I'd like to define a default setting for disallowed content elements that is applied to all backend layouts.
Current approach
The current approach would be defining a default value and copying that into the columns in PageTS via copy operator <.
The problem with that is that extensions defining own CEs can not exclude them from all other backend layouts they obviously don't know about.
Due to the limitations of PageTS in regards of using reference (=<) the suggested approach is supplying a default object for Ext:content_defender which is considered at runtime during evaluation of the settings. This effectively serves as default value for column settings which is extended by the regular settings on the backend layout.
Thank you for your feature proposal. Currently I don't see any way to include a default allowed/disallowed property in content_defender. If I understand you correctly, you do have a sitepackage providing the backendlayout and its configuration. The sitepackage "knows" about its dependencies (and therefore for loaded extensions and available content element types) and should be able to define allowed/disallowed element types per column.
Not sure if this is the right place or if that should be a TYPO3 core feature.
We're using mutliple extensions providing content elements that should only be used in specific backend layouts.
I'd like to define a default setting for disallowed content elements that is applied to all backend layouts.
Current approach
The current approach would be defining a default value and copying that into the columns in PageTS via copy operator
<
.The problem with that is that extensions defining own CEs can not exclude them from all other backend layouts they obviously don't know about.
Suggested approach
Due to the limitations of PageTS in regards of using reference (
=<
) the suggested approach is supplying a default object for Ext:content_defender which is considered at runtime during evaluation of the settings. This effectively serves as default value for column settings which is extended by the regular settings on the backend layout.Ext:content_defender
Ext:my_ext
The text was updated successfully, but these errors were encountered: