Feature #80544
closed
INCLUDE_TYPOSCRIPT resolve constants for condition argument
0%
Description
I know about the bug here: https://forge.typo3.org/issues/56304
and here: https://forge.typo3.org/issues/47985
which describes why one cannot use constants inside the path.
However, it would be really nice to support constants in the condition parameter, e.g. I want to define a page ID constant
and then include additional TypoScript if one is on that page like
[page|uid = {$pageuid}]
or similar.
This will work inside a file itself but not when using it in INCLUDE_TYPOSCRIPT.
However, it would be really nice if it would work in both scenarios. Maybe one could check if one is parsing setup TypoScript and if so resolve the constants?
In any case it will probably not be that easy to solve.
Updated by
Updated by Christian Kuhn over 2 years ago
- Related to Feature #97816: New TypoScript parser added
Updated by Christian Kuhn over 2 years ago
- Status changed from New to Rejected
@import can be nested within conditions in new ts parser. And standard conditions do support constants. This adds the last feature to @import where INCLUDE_TYPOSCRIPT has been used before. We will probably phase out INCLUDE_TYPOSCRIPT and will not implement this feature to it anymore.