Registry: Global disallow setting #507
Comments
saitho
added a commit
to dkd/container
that referenced
this issue
Jun 11, 2024
A new method "Registry::addDisallowedCType" is added that allows excluding content elements from all containers per default (if Ext:content_defender is installed). However, content elements excluded in such a way can still be explicitly allowed via "allowed" setting in column configuration. Resolves: b13#507
saitho
added a commit
to dkd/container
that referenced
this issue
Jun 11, 2024
A new method "Registry::addDisallowedCType" is added that allows excluding content elements from all containers per default (if Ext:content_defender is installed). However, content elements excluded in such a way can still be explicitly allowed via "allowed" setting in column configuration. Note: In order to take effect on the whole TYPO3 system, the method needs to be called in ext_localconf.php. Resolves: b13#507
saitho
added a commit
to dkd/container
that referenced
this issue
Jun 11, 2024
A new method "Registry::addDisallowedCType" is added that allows excluding content elements from all containers per default (if Ext:content_defender is installed). However, content elements excluded in such a way can still be explicitly allowed via "allowed" setting in column configuration. Note: In order to take effect on the whole TYPO3 system, the method needs to be called in ext_localconf.php. Resolves: b13#507
saitho
added a commit
to dkd/container
that referenced
this issue
Jun 11, 2024
A new method "Registry::addDisallowedCType" is added that allows excluding content elements from all containers per default (if Ext:content_defender is installed). However, content elements excluded in such a way can still be explicitly allowed via "allowed" setting in column configuration. Note: In order to take effect on the whole TYPO3 system, the method needs to be called in ext_localconf.php. Resolves: b13#507
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a few containers defined across multiple extensions and we have many content elements.
Some content elements are not suited to be nested in containers, therefore we want to exclude those from all containers.
Right now there is no way to exclude a content element from all grids. I'd like to suggest a new method for the container Registry that allows defining a global disallow setting, that is merged with the disallow list already returned by
Registry::getContentDefenderConfiguration.Maybe a content element globally disallowed via this method, should only be allowed when it is explicitly listed in "allowed".
The text was updated successfully, but these errors were encountered: