Issue Bug New Orphaned

#107028Invalid site sets are hard to debug and show missleading information

Benjamin Kott 07/03/25, 13:28 updated 07/03/25, 13:28

Description

When having misconfigured Site Sets it´s hard to find where the problem is.

In the settings interface i can see that this site has an invalid set.
And it´s telling me that it’s missing a dependency. But the set is available and included in the same package.
I have no way to access the current settings anymore nor i get presented any relevant information in this view,
that would explain the error.

clipboard-202507031513-hzete.png

The situation is the same for the sites module.

clipboard-202507031523-agqtr.png

I need to scroll down to find a new section that displays invalid sets, but not all of them

clipboard-202507031524-04o2w.png

I can now see some messages but without context to the site.
I can see that an invalid page type is provided by “blog/static“
I can see that “blog/standalone” is disabled due to a missing dependency, but blog/static is available – but it´s broken / has errors

My expectation would have been that i was getting the message that the blog/static has a problem in the first place.
So i would have expected to see the root cause of the problem and not the end of the chain.

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] Invalid site sets are hard to debug and show missleading information Resolves: #107028 Releases: main