Project

General

Profile

Bug #12821

TypoScript condition syntax deprecated

Added by Marc Egger 2 months ago. Updated 2 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
Target version:
Start date:
19.07.2021
Due date:
% Done:

0%

Estimated time:
Discuss:

Description

Since T3 v9 the condition syntax has changed. Since we are using old condition syntax in UZH CD we get a lot of warnings.
If we change to the new condition syntax, UZH CD won't be compatible with T3 v8 anymore.

The warnings can be disabled by the following setting in Typo3 backend:

the feature flag [SYS][features][TypoScript.strictSyntax] can be disabled via Settings -> Configure Installation-Wide Options or directly in LocalConfiguration.php.

Warnings we get:

Mon, 19 Jul 2021 16:18:26 +0200 [WARNING] request="a8593a94bec76" component="TYPO3.CMS.Frontend.Configuration.TypoScript.ConditionMatching.ConditionMatcher": Expression could not be parsed, fallback kicks in. It looks like an old condition with only one equal sign. - {"expression":"PIDinRootline = "}
Mon, 19 Jul 2021 16:18:26 +0200 [WARNING] request="a8593a94bec76" component="TYPO3.CMS.Frontend.Configuration.TypoScript.ConditionMatching.ConditionMatcher": Expression could not be parsed, fallback kicks in. It looks like an old condition with only one equal sign. - {"expression":"globalVar = LIT:1 = 1"}
Mon, 19 Jul 2021 16:18:26 +0200 [WARNING] request="a8593a94bec76" component="TYPO3.CMS.Frontend.Configuration.TypoScript.ConditionMatching.ConditionMatcher": Expression could not be parsed, fallback kicks in. It looks like an old condition with only one equal sign. - {"expression":"PIDinRootline = 5,7,22,47,60,64,72,73,110,119,120"}

#1

Updated by Marc Egger 2 months ago

  • Description updated (diff)

Also available in: Atom PDF