Issue Bug Resolved

#108920Active TypoScript view in backend is broken if an unknown TypoScript modifier is used

Karsten Nowak (undkonsorten) 02/09/26, 16:24 updated 11/17/26, 20:20

Description

If I use my own modifier in TypoScript

plugin.tx_myplugin.settings.foo := mySampleModifier(bar)

the key foo is visible in active TypoScript view without a value and equal sign. That’s ok.

But if I use a setting/constant as value for the modifier

plugin.tx_myplugin.settings.foo := myUnknowModifier({$my.foo.bar})

and “Substitute constants in setup” is active, then the backend view for active TypoScript crashes with an type error:

TYPO3\CMS\Core\Utility\DiffUtility::diff(): Argument #2 ($to) must be of type string, null given, called in /var/www/html/vendor/typo3/cms-backend/Classes/ViewHelpers/TypoScript/FineDiffViewHelper.php on line 46

Reviews 2

History 48

  1. Maike Kiebele commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-17T16:55:10+00:00" > 11/17/26, 16:55 </span>

    Applied in changeset commit:bac214c33c0cc7ea6d7e9350113df6a0307ffcbf.

  2. Gerrit Code Review pushed patch set 2 for 14.3 to change 97759 status Resolved Under Review <span data-processor="relativetime" data-value="2026-11-17T19:35:44+00:00" > 11/17/26, 19:35 </span>

  3. Maike Kiebele commented and changed status Under Review Resolved <span data-processor="relativetime" data-value="2026-11-17T20:20:13+00:00" > 11/17/26, 20:20 </span>

    Applied in changeset commit:7384b571ecd1dc7295fa1bd50e39c037359fdba9.