redlinks appear and force edits

[jrbray1]

An incoming URL may be redirected, but if you quote the wrong case version in the page, it generates a redlink which points to an edit page http://localhost/wiki/johnbraywiki/index.php?title=A_city_night&action=edit&redlink=1

The extension would need to get rid of "&action=edit&redlink=1" to be useful. I had hoped the March 2020 update might have done this, but no luck so far

[ciencia]

That's not feasible. Otherwise, you won't be able to create pages with a different case than existing ones, and there may be reasons to create those.

If you want a case-insensitive MediaWiki you may want to try this (I don't know if that would work currently, though)

I'm not closing this, but I doubt it would be implemented in the near future, because that has several implications. When a page is created or renamed, the extension would need to check incoming links in any case, and that would probably be expensive

[jrbray1]

I think anyone using SaneCase would be using it to create a case-insensitive wiki. With only external incoming URLs being decased, I don't feel this extension is much use, sadly, as so many people have railed against the case sensitivity policy over the years. I have one special use case where it is still useful, when I ported from wikidot with fancyclopedia.org/john-bray becoming fancyclopedia.org/John Bray on mediawiki, and I wanted to stop breaking links to the former, but I had hoped for more. After the port we are cluttering our wiki with case changing redirects.

[ciencia]

Actually, I'm using it because the Bing crawler usually treats all URLs as case insensitive, and likes to crawl my wiki with all lowercase URLs, leading to lots of 404 errors on my logs. Also, some users like to type page names directly on the URL instead of using the search suggestions...

[aaronliu0130]

Our Miraheze wiki uses dialogs in the actions portlet to create new pages. It seems like automatically redirecting is easier than manipulating the database, especially on wikifarms that'd take bureaucracy to configure unexposed stuff, while many extensions can be selected. Maybe this could be a setting.