Last modified: 2014-08-14 18:12:32 UTC
There seems to be a problem with following wikilinks with certain punctuation (such as the ? character) when on the mobile site. For example, when I try to follow the wikilink [[R U Mine?]] from both my Kindle Fire and my phone, it takes me to https://en.m.wikipedia.org/wiki/R_U_Mine%253F instead of https://en.m.wikipedia.org/wiki/R_U_Mine%3F and I get a 'bad title' error. It seems to be a problem with percent encoding... %25 is the percent code for %, so by sending me to https://en.m.wikipedia.org/wiki/R_U_Mine%253F the site seems to be trying to double percent-encode or something. Any help would be appreciated!
Prioritization and scheduling of this bug is tracked on Trello card https://trello.com/c/fxZgRAAr
Hi! Can you say, what browser you use? I have tested the linking from this page [1] to "R U Mine?" on chrome for android in stable, beta ad alpha mode of MobileFrontend and had no problems :/ Any special steps and information to reproduce this would be helpful :) [1] https://en.wikipedia.org/wiki/Come_Together
(In reply to Florian from comment #2) > Hi! Can you say, what browser you use? I have tested the linking from this > page [1] to "R U Mine?" on chrome for android in stable, beta ad alpha mode > of MobileFrontend and had no problems :/ > > Any special steps and information to reproduce this would be helpful :) > > [1] https://en.wikipedia.org/wiki/Come_Together Okay, this is so weird. The issue's gone. I've been having the issue consistently for the last several months on both my Kindle browser (the default one, I think it's called Silk?) AND my Android (using Chrome and stock browser). Always happened only on the mobile site and not desktop version, and it happened with every single wikilink that had a "?" in the title. This was happening up til yesterday. I just tried it again, and this time it works! No bad title error. Problem solved, I guess? (I'm not crazy, I swear! Well, maybe I am a little.)
> I'm not crazy I think too you're not :) If we can't reproduce it, we can (unhappily) nothing do :( I will close this, but if you (or some other) see this problem again, feel free to reopen :)
Please reopen if the bug comes back and you can find a reliable way to reproduce! :)
