Perhaps ideally this should throw an exception (but where exactly? Setup.php? Seems weird to check for this super unususl case in setup.php).

Honestly though, I feel this is a case of do silly things get silly results.

In T245873#5909168, @Bawolff wrote:

Perhaps ideally this should throw an exception (but where exactly? Setup.php? Seems weird to check for this super unususl case in setup.php).

Based on my conversation with @Reedy, A patch to setup.php may be trivial as there is no current validation. Although, the issue of all the other languages was brought up.

Honestly though, I feel this is a case of do silly things get silly results.

We are the first to report in a long time. It’s an edge case.

The namespace will not be created (and probably error) to avoid breaking functionality

Of course the setup.php wouldnt solve that problem. It would just change from special being broken to the entire wiki being broken.

In T245873#5909216, @Bawolff wrote:

The namespace will not be created (and probably error) to avoid breaking functionality

Of course the setup.php wouldnt solve that problem. It would just change from special being broken to the entire wiki being broken.

That’s out then. I was looking for a way to prevent a namespace called “Special” or the localised version being created to avoid damage to core functionality.

While you are using some sort of custom interface to let users create namespaces, right? Personally, I think it makes more sense to verify the sanity of the configuration on that layer.

In T245873#5909282, @Bawolff wrote:

While you are using some sort of custom interface to let users create namespaces, right?

Extension:ManageWiki

Personally, I think it makes more sense to verify the sanity of the configuration on that layer.

We're looking at that but someone mentioned the possibility of having mediawiki core block it as well.