#106064deflateKeys error in using a link via Plugin Enhancer
Description
I get the following error message when using a link via Plugin Enhancer:
TYPO3\CMS\Core\Routing\Enhancer\VariableProcessor::deflateKeys(): Argument #1 ($items) must be of type array, string given, called in /var/www/html/public/typo3/sysext/extbase/Classes/Routing/ExtbasePluginEnhancer.php on line 95
I checked that and indeed is the argument a string. I get an ‘__UNSET’ in the array key $this->configuration[‘defaults’], so the condition $this->configuration[‘defaults’] ?? [] doesn’t work, because the value isn’t empty.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 3
-
Oliver Hader commented and changed status
NewNeeds Feedback 02/04/25, 09:20 -
Oliver Hader commented 02/04/25, 09:56
Besides that, could you please provide the exact TYPO3 version that is being used, as well as the YAML site configuration in question? Thanks in advance!
-
Georg Ringer commented and changed status
Needs FeedbackClosed 11/11/26, 21:56Thank you for the report.
There was no answer to the request for the exact TYPO3 version and the YAML site configuration, so there is nothing to reproduce this with. As analyzed above, the error happens when a literal
__UNSETvalue is stored in the YAML file fordefaultsof the enhancer, so thatdeflateKeys()receives a string instead of an array. Removing the__UNSETfrom the site configuration resolves it. It is unclear how the value ended up in the file, and the report is for TYPO3 v12.I am closing this issue due to missing feedback. If you can still reproduce it with a current version, please open a new issue and provide the exact TYPO3 version, the YAML site configuration and the steps that led to the
__UNSETvalue in the file.If this is still valid for you in v14, please open a new issue and provide information how to reproduce it. Thanks!
Reference: https://github.com/TYPO3/typo3/blob/v12.4.26/typo3/sysext/extbase/Classes/Routing/ExtbasePluginEnhancer.php#L99
It seems, that
__UNSETis persisted in your YAML site configuration as well. When modifying the site configuration via the site module in the TYPO3 backend, a corresponding check flags to-be-removed sections with__UNSETand finally cleans them by invokingArrayUtility:: mergeRecursiveWithOverrule, see https://github.com/TYPO3/typo3/blob/v12.4.26/typo3/sysext/core/Classes/Configuration/SiteConfiguration.php#L327-L335In case my assumption is correct – that there’s a
__UNSETin your YAML site configuration – then, the issue can be resolved by manually removing the__UNSETfrom the configuration file. However, it’s unclear, how it ended up there…