#90163Site config still being used even if page is no longer site root
Description
If the “Use as Root Page” flag is removed from the properties of a page with its own site config, that site config is still being used in the FE, if the config.yaml file is still present.
This can be highly misleading as the page is no longer visually recognizable as a site root in BE. Additionally, it shows up under “Unassigned site configurations” in sites management, with the explanation:
“The following sites don’t belong to any page anymore and can be removed.”
This also suggests that the site config is no longer in use, while it actually still is.
IMHO, this is actually a missing feature: an easy way to disable/enable a site configuration without having to rename/delete the respective config.yaml. I had hoped that this could be achieved by temporarily removing the “Use page as Root Page” flag.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[BUGFIX] Site config still being used even if page is no longer site root Resolves: #90163 Releases: main