ContentDefender configuration in PageTSConfig

[599media]

Hi and thanks for the great work!

We're migrating some projects from ext:gridelements. As you might know gridelements has an integrated content_defender. The configuration there can be done via PageTSConfig and is therefor page-based (which is great for multi-site instances). In ext:container the content defender configuration can only be done via TCA and is therfor global if we're not mistaken.

Are there any plans on changing or extending this?

We did have a look at the getContentDefenderConfiguration-function in the Registry.php. It seems like the actual content_defender stuff is done on-the-fly. So you actually can access the PageTSConfig of the current page and are potentially able to override the global TCA-based content_defender configuration. Since we need this pretty badly, we are extending the class and try to implement this feature. Are you interested in pull request when we're done or is this something you don't see in ext:container?

[599media]

Here is the extending class we use in our project to enable the mentioned behaviour... it basically checks if there's a PageTSConfig configuration for the content defender settings.

<?php

declare(strict_types=1);

namespace Fnn\FnnContainerExtended\Tca;

use TYPO3\CMS\Backend\Utility\BackendUtility;


class Registry extends \B13\Container\Tca\Registry
{
    public function getContentDefenderConfiguration(string $cType, int $colPos): array
    {
        $currentPageId = (int)$_GET['id'];
        $ctypeConfig = BackendUtility::getPagesTSconfig($currentPageId)['lib.']['fnnContainerExtended.'][$cType.'.'] ?? [];

        $contentDefenderConfiguration = [];
        $rows = $this->getGrid($cType);

        foreach ($rows as $columns) {
            foreach ($columns as $column) {
                if ((int)$column['colPos'] === $colPos) {
                    if (isset($column['allowed']) && !empty($column['allowed'])) {
                        $contentDefenderConfiguration['allowed.'] = $column['allowed'];
                    } else {
                        $contentDefenderConfiguration['allowed.'] = $ctypeConfig[$colPos.'.']['allowed.'] ?? [];
                    }

                    if (isset($column['disallowed']) && !empty($column['disallowed'])) {
                        $contentDefenderConfiguration['disallowed.'] = $column['disallowed'];
                    } else {
                        $contentDefenderConfiguration['disallowed.'] = $ctypeConfig[$colPos.'.']['disallowed.'] ?? [];
                    }

                    if (isset($column['maxitems']) && !is_null($column['maxitems'])) {
                        $contentDefenderConfiguration['maxitems'] = $column['maxitems'];
                    } else {
                        $contentDefenderConfiguration['maxitems'] = $ctypeConfig[$colPos.'.']['maxitems'] ?? 0;
                    }
                }
            }
        }

        return $contentDefenderConfiguration;
    }
}

[achimfritz]

Hi @599media , you can do so, but this will not goes into the EXT:container Code, because it depends on the Request (s. $currentPageId = (int)$_GET['id']; ) (e.g. will not work in CLI, or for POST Requests) (i think, the change can even have more Site-Effects in special cases).
The container-configuration ist static and complety cache. We prefere to use an other CType for an other configuration.

[599media]

@achimfritz Thanks for your feedback. Can I ask, what kind of CLI actions or POST requests you have in mind? And maybe you could also give us a hint about the possible additional side effects? Maybe we can come up with a more robust solution. An answer would be very much appreciated!