Project

General

Profile

Actions
Copy link

Bug #104544

closed

TypoScript cache of nested Site Sets are not unique in Frontend

Added by Benjamin Franzke 4 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Must have
Assignee:
Benjamin Franzke
Category:
TypoScript
Target version:
13.3
Start date:
2024-08-02
Due date:
% Done:

100%

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

Description

If a set extends another set by depending on it and changing some TypoScript:

typo3conf/ext/mysite/Configuration/Sets/ExtendingSite/config.yaml

name: my/extending-site
label: 'My Extending Site'
dependencies:
  - typo3/styleguide

typo3conf/ext/mysite/Configuration/Sets/ExtendingSite/setup.typoscript

page >
page = PAGE
page.1 = TEXT
page.1.value = FOOBAR

then the frontend will create a TypoScript cache and apply that to sites that either use the set my/extending-site or typo3/styleguide while the sets are actually different.

The backend TypoScript analyzer does not suffer from this.

Credits to @Tomek W for finding this bug.

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Task #103439: Site TypoScriptClosed2024-03-20

Actions
Actions
Copy link

Also available in: Atom PDF