Issue Bug Closed

#106666Site Sets and TypoScript Conditions

Achim Fritz 05/07/25, 15:05 updated 12/02/25, 14:21

Description

having a Installation with two sites, and :

clipboard-202505071649-peiwp.png

having two Site-Sets, where Set2 depends on Set1

cat Sets/Site1/config.yaml 
name: local/site1
label: local/site1
cat Sets/Site2/config.yaml 
name: local/site2
label: local/site2
dependencies:
  - local/site1

use local/site1 as dependency in site config of site1
use local/site2 as dependency in site config of site2

base: 'https://core13.ddev.site/'
dependencies:
  - local/site1
rootPageId: 1
base: 'https://core13-2.ddev.site/'
dependencies:
  - local/site2
rootPageId: 2

now add some fancy TS

cat Sets/Site1/setup.typoscript 
config.disableAllHeaderCode = 1
page = PAGE
page.10 = COA_INT
page.10.10 = TEXT
page.10.10.value = default

[traverse(page, "uid") == 3]
  page.10.10.value = we are on page 3
[end]
cat Sets/Site2/setup.typoscript 
[traverse(page, "uid") == 4]
  page.10.10.value = we are on page 4
[end]

now call pages in this order

curl https://core13.ddev.site/page-3
echo ""
curl https://core13.ddev.site/
echo ""
curl https://core13-2.ddev.site/page-4
echo ""
curl https://core13-2.ddev.site
echo ""

we get

we are on page 3
default
we are on page 4
we are on page 4

so on root page of site 2 we get “we are on page 4” instead of “default“
(flushing cache and call root page of site 2 gives expected “default”)

(the bug occures not, if we have no site-sets, but use TS-Imports)
(only testet with TYPO3 13)

Reviews 2