#111490Conditions with unresolved constants in TypoScript never match
Description
I guess this is a regression of #105864
We have TypoScript which tests if a constant is different from a certain value, e.g.
["{$plugin.tx_xxxxx.isLoaded}" != "1"]
# set code if constant is not "1"
[end]
The constant is set when a certain extension is installed and a specific static TypoScript template was loaded. Before TYPO3 14.3.12 this condition worked as expected: if the other extension was installed and the template included, it didn’t match. If it was not installed, the fallback code was loaded, because the constant was resolved to "{$plugin.tx_xxxxx.isLoaded}" which is obviously different from "1"
With TYPO3 14.3.12 this condition never matches. It would be great, if we could get back the old behaviour.
Reviews 1
Related issues 1
History 12
-
Georg Ringer changed Related to #105864 <span data-processor="relativetime" data-value="2026-11-18T21:09:31+00:00" > 11/18/26, 21:09 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 97808 status
NewUnder Review <span data-processor="relativetime" data-value="2026-11-18T21:15:31+00:00" > 11/18/26, 21:15 </span>