Bug #90436
Updated by Christian Eßl about 4 years ago
*Preset:* We already have an existing page root "Root A". *Step 1* Now create a new Page root "Root B". TYPO3 will now automatically generate new site config in the format "autogenerated-96-26657d5ff9". The page has the checkbox "is_siteroot" NOT checked. *Step 2* Move the page "Root B" somewhere inside "Root A" to make it a part of its page tree. If you now visit the Site config module, the autogenerated site config will be now marked as *unassigned*. But if you open the page in the pages module, it will still have its site config for "autogenerated-96-26657d5ff9" assigned, which can lead to many bugs. *Examples:* Examples: - My site config for "Root A" allows for translations, but I can't translate the page "Root B", as the autogenerated site config has no other languages than "Default". - If I open the page with the "view" button, the url will look something like "https://typo3.ddev.site/autogenerated-96/en/root-b" *My conclusions:* My conclusions: - Autogenerated site configs should only be created, if you create a page set with "is_siteroot" to true. - If I delete a root page, its autogenerated (!) site config should be deleted as well. - It's weird, that the Site config module shows the site config as "unassigned", but it is actually loaded in several places, as can be seen from the behaviour. My understanding was, that a page would need to have "is_siteroot" set, but that is apparently not the case?