Project

General

Profile

Actions

Bug #102357

open

PageTsConfig: site settings / constants are not substituted in FormEngine

Added by Moritz Ngo 6 months ago. Updated 4 months ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2023-11-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
8.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When using Site settings as constants in PageTsConfig conditions, the actual value is not being substituted.

How to reproduce:

  1. Add SiteSettings (config/sites/<siteidentifier>/settings.yaml:
    foo:
        bar: 1234
    
  2. Add PageTsConfig:
    TCEFORM.test = {$foo.bar}
    [{$foo.bar} == 1234]
        TCEFORM.test2 = 42
    [GLOBAL]
    
  3. Open any record (e.g. page properties via Page module)

Now you'll find the following error message in the TYPO3 Log:

Thu, 09 Nov 2023 11:59:07 +0100 [ERROR] request="af66caedbce8e" component="TYPO3.CMS.Core.TypoScript.IncludeTree.Visitor.IncludeTreeConditionMatcherVisitor": Expression could not be parsed. - {"expression":"{$foo.bar} == 1234"}

When Debugging PageTsConfig via the appropriate Module, the site settings / constants are getting substituted properly, thus suggesting it'll work


Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #92528: TypoScript site constants not always populatedClosed2020-10-09

Actions
Related to TYPO3 Core - Bug #102452: TypoScript constants from site settings are not substituted in Backend Extbase ModulesResolved2023-11-22

Actions
Related to TYPO3 Core - Feature #97816: New TypoScript parserClosed2022-06-27

Actions
Related to TYPO3 Core - Feature #91080: Populate site settings to TypoScript constantsClosedBenni Mack2020-04-17

Actions
Actions

Also available in: Atom PDF