Bug #80386
closed
INCLUDE_TYPOSCRIPT condition option with custom defined condition requires double "\" in class name
0%
Description
Normally, when using custom conditions, the condition will be like this:
[TYPO3\CMS\Test\TestCondition = xx]
[global]
However, when using INCLUDE_TYPOSCRIPT like:
<INCLUDE_TYPOSCRIPT: source="DIR:EXT:test/test.ts" extensions="ts" condition="TYPO3\\CMS\\Test\\TestCondition = xxx">
it requires the double "\" (like in the above example).
Doesn't matter if the condition is in "[" and "]" either.
Updated by Benni Mack almost 7 years ago
- Target version changed from 8 LTS to next-patchlevel
Updated by Łukasz Uznański over 6 years ago
- Sprint Focus set to On Location Sprint
Updated by Mathias Brodala about 6 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Benni Mack about 5 years ago
- Target version changed from next-patchlevel to Candidate for patchlevel
Updated by Riccardo De Contardi over 3 years ago
I think that it requires the double "\\" because the "\" is a character that needs escaping
should we mention it on the documentation? https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/TypoScriptSyntax/Syntax/Includes.html?highlight=include_typoscript#conditions
Updated by Riccardo De Contardi 11 months ago
I have to note that this issue could be obsolete, as since TYPO3 12 the includes work inside a condition e.g.
<INCLUDE_TYPOSCRIPT: source="DIR:EXT:test/test.ts" extensions="ts" condition="TYPO3\\CMS\\Test\\TestCondition = xxx">
can be written as [TYPO3\CMS\Test\TestCondition = xx] <INCLUDE_TYPOSCRIPT: source="DIR:EXT:test/test.ts" extensions="ts"> [global]
Updated by Christian Kuhn 8 months ago
- Related to Feature #97816: New TypoScript parser added