Project

General

Profile

Actions

Bug #97172

closed

TemplateAnalyzer does not show constants populated from site settings for nested sites

Added by Susanne Moog over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2022-03-11
Due date:
% Done:

100%

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

Description

Page tree:

- UID 1 - Root - Normal Page - No Site
-- UID 2 - Is_siteroot - Site Configured

Config.yaml

rootPageId: 2
settings:
foo: bar

Expectation:
Backend TS Object Browser shows constant `foo`.

Reality:
TS Object Browser only considers UID 1 for site finding and fails to find the config.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #91081: Populate site settings to TSconfigClosedBenni Mack2020-04-17

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

Actions
Actions #1

Updated by Gerrit Code Review over 2 years ago

  • Status changed from New to Under Review

Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/73902

Actions #2

Updated by Gerrit Code Review over 2 years ago

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/73956

Actions #3

Updated by Susanne Moog over 2 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #4

Updated by Christian Kuhn over 2 years ago

Actions #5

Updated by Christian Kuhn over 2 years ago

  • Related to Feature #91080: Populate site settings to TypoScript constants added
Actions #6

Updated by Benni Mack about 2 years ago

  • Status changed from Resolved to Closed
Actions #7

Updated by Philipp Kitzberger almost 2 years ago

Just as an info for anyone wondering: I can confirm that this bug exists in 10.4.34 as well and the above mentioned patch is working without any adjustments for that version as well.

Actions

Also available in: Atom PDF