Issue Bug Closed

#105760Cached Settings in site configuration (multi domain setup)

David Hoeckele 12/04/24, 11:02 updated 12/02/25, 14:31

Description

Hey, i have a multidomain setup (v12 => v13 upgrade) with a settings.yaml for each site which contains some pids like

publication:
  detailPid: 123
  listPid: 456
  storagePid: 789

These settings are used in typoscript plugin config (and later in php/fluid):

plugin.tx_customer_publication {
    settings {
        listPid = {$publication.listPid}
        detailPid = {$publication.detailPid}
        storagePid = {$publication.storagePid}
    }
}

the first site get’s the correct site settings as expected, calling the second site afterwards it gets the same settings as the first site instead of it’s own custom settings, they seem to be cached.
I also made a testcase with a plain TYPO3 instance:
Created 2 site configs and add settings to site config (separated settings.yaml made no difference):

base: 'https://plain-typo3-13.ddev.site/autogenerated-1'
errorHandling: {  }
languages:
  -
    title: English
    enabled: true
    languageId: 0
    base: /
    locale: en_US.UTF-8
    navigationTitle: English
    flag: us
rootPageId: 1
routes: {  }
settings:
  testParam: 111

and

base: 'https://plain-typo3-13.ddev.site/autogenerated-2'
errorHandling: {  }
languages:
  -
    title: English
    enabled: true
    languageId: 0
    base: /
    locale: en_US.UTF-8
    navigationTitle: English
    flag: us
rootPageId: 2
routes: {  }
settings:
  testParam: 222

Created a typoscript template in backend on each root page to output the setting:

page = PAGE
page {
  typeNum = 0

  10 = TEXT
  10.value = {$testParam}
  10.insertData = 1
}

Calling first page returns 111, calling second page afterwards also returns 111 instead of 222.
I also have checked the cache/code/core/SiteSettings_* files, they look fine.

Reviews 4