Issue Bug Under Review Quiet

#110527Site settings do not reach TypoScript constants until caches are flushed

Benjamin Kott 08/24/26, 13:27 updated 10/08/26, 12:58

Description

Values saved in the site settings editor do not reach the frontend. The
rendered page keeps the previous value until the “pages” cache group is
flushed by hand. The TypoScript module shows the new value right away,
because it builds the tree without a cache.

Steps to reproduce

1. Set up a site with a set that defines a setting and uses it as a
constant.
2. Flush all caches and call the frontend once, so the TypoScript cache
is warm.
3. Change the setting in the site settings editor and save.
4. Call the frontend again — the constant still carries the old value.

Cause

SysTemplateTreeBuilder::getTreeBySysTemplateRowsAndSite() caches the
include tree node built for a site under

site-template-<type>-<siteIdentifier>;

That identifier does not depend on the site settings, while the node
contains the constants generated from them, attached by
addDefaultTypoScriptConstantsFromSite(). The inner node it attaches is
cached under site-constants-<hash of the settings> and is hashed over
the settings correctly, but is never reached because the outer entry is
returned as a whole.

SiteSettingsService::writeSettings() only flushes the code cache. The
typoscript cache lives in the “pages” group and is left untouched, as is
the page cache holding the already rendered pages.

Reviews 1

History 15