Yea, @Ora. But this really seems to have been resolved (partially because some pages still do this, I think the same thing happens (useformat=mobile). Does it still happen to you?

Even so, not planning to close as resolved because it's a problem in several wikis and have to do something manual to avoid it instead of reappearing by itself, and, this only happens with pages that redirect to User groups.

After manually creating the groups in MediaWiki:Grouppage, I "solved" the problem as the groups came back. https://gtavariants.miraheze.org/wiki/Special:Statistics @dross creating the pages "solved" the problem

Hello. It's been a few days and this is still active. Are in the service to discover something? Or do I have to do something?

In T8667#175791, @Ugochimobi wrote:

Maybe purge the wiki or something

How do you purge a wiki?

I'm not talking about the link that redirects to User groups, but the rights that disappeared. Is this on purpose? Because, it appears on some wikis and not others.

example: https://gtavariants.miraheze.org/w/index.php?title=special:statistics

True, I just saw it. So how so? Will the extension have the same functionality?

The PVW, unfortunately

This is specific for wikimedia

Users can create a namespace named "Special". So it replaces it, and when you visit a special page (after replace), it appears as if it doesn't exist, and we don't know where the page goes. It's complicated because all the pages listed are just on a special page.

It is asking you to disable and re-enable the VisualEditor in Special:ManageWiki/namespaces

This already happened to me on my wiki, I followed this example given by a user (void): Use Special:ManageWiki/namespaces cycling the option to enable VisualEditor in that namespace. Even If it is currently disabled, disable it, save, and renable

@Bukkit Also, it doesn't happen with WMF wikis and any other type of wiki that uses MediaWiki software. Only Miraheze.

@Bukkit this has probably already shown that it's not cookies error, it happens with clean browsers. And, @Universal_Omega this doesn't just happen with Minerva, it happens with Timeless, among other mobile themes. 2: Happens to logged in users as well 3: heavy pages usually take a while to load and in the end, "fall over" with it (desktop theme being shown). This is a readability issue.

This for me (imported along my passage in wikis) pages in masses imported mainly from Wikipedia, and in the end, this always happened. Anyway, pages appeared in special:log/import

So, if it's intentional, how do I make a request to remove them?

You need to find out more about it here (it doesn't just happen when you go researching something). If it is intentional, I object so, per my reasons cited here. This for me, hinders more than helps. First, the theme is no longer responsive.

@Universal_Omega , could you help this, to see the function causing this, because I think it's public utility, this can be good or bad (bad for me). Or elevate that to an RfC to see community votes?

If it's intentional, something probably causes it. To extend the above stub, this also happens when we go to very heavy pages, and especially when we are logged in, annoying.

@Agent_Isai

I don't believe this happens just for me. I invite the automatic subscribers of this task to do the same (On cell phone (or mobile) click on that gray magnifying glass, and do a search even without characters). Theme will stay desktop. I guarantee. I just need to make a video showing this, to prove it.

@Universal_Omega Please do it yourself. On mobile, when doing a search, the theme automatically switches to the desktop theme abruptly and unintentionally. This doesn't happen on small pages, it happens on large pages or in wiki search.

I assure you that it is not any browser error or cookies or anything related. The explanation for this is difficult because I've already tested it with other MediaWiki wikis, but this only happens on Miraheze-hosted wikis. You can analyze it yourself. It would be great if some system wizard here, look for something that causes this, or even solve it. I've already done a test in two browsers, and the same happens with other devices.