Issue Bug Closed

#91995It's not possible to handle the case "no site config yaml found" for a domain like an error (e.g. 404 or 503)

S P 08/13/20, 11:11 updated 12/17/24, 10:12

Description

We have a big TYPO3 setup with hundreds of domains, all configured via site config yaml files.

If – by whatever accidental reason – a domain is pointing to the TYPO3 system that was NOT configured as a site yaml, then the first “pseduo site” is used instead (which usually is the first is_siteroot = 1 found in the page tree). Then this domain displays totally unrelated and random content.

It’s OK to show the first site from the page tree if NO yaml exists at all (to make life easier for beginners or small setups). But as soon as site config yamls exist, a domain that was not configured should not start displaying some random content from a totally arbitrary place in the page tree (which can even change if moving nodes around).

In our case we’d like to show the action configured in [FE][pageNotFound_handling].

It must be posible to handle unconfigured domains somehow.

I flagged this as regression because with ext:realurl this was possible. Realurl then exited at least with a 500 error because the resolution of the rootpage id was ambigious.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.