Guild Wars 2 Wiki:Reporting wiki bugs

From Guild Wars 2 Wiki
Jump to: navigation, search

Please report all bugs found on Guild Wars 2 Wiki here.

This page is NOT for reporting game bugs, those should be reported at the official forums.

This page is for reporting bugs that you may encounter in the wiki. This does not cover in-game issues that you may encounter, nor does it cover page contents within individual articles.

  • If you are experiencing an in-game bug or issue that requires technical support, check the Guild Wars 2 support forums.
  • If you are experiencing difficulties getting past a specific part of the game, use the "Search" box on the left to find the specific quest, mission, or region that you are finding difficult. You can review any tips on that page, and discuss it on that page's talk page if more help is needed.
  • If you have a problem with contents of a page, use the associated talk page.

Please review existing bug reports before creating a new one. If you add a bug not related to the wiki (such as a bug in the game itself), the report may be removed with no action taken.

When reporting a new bug, be sure to provide a description of the problem, your wiki username, the information from any error message received, and any additional comments that may help someone reproduce and troubleshoot the suspected bug.

Key: Yes = Solved, No = Unsolved, No = Not a bug

Yes Pages with apostrophe in title cause "too many redirects" error in Chrome[edit]

After trying to search for "Hero's Canton", I discovered that any page with an apostrophe in the title/URL causes Chrome to fail to load, citing a "too many redirects" error. I'm not a wiki or Chrome expert so I don't know why, but given that similar pages on Wikipedia load correctly, I'm inclined to suspect it's a problem with something this wiki is doing. NikkoJT (talk) 19:30, 16 March 2016 (UTC)

This doesn't appear to be just Chrome, as IE and Safari also exhibit the issue. I'm investigating. Justin Lloyd (talk) 19:48, 16 March 2016 (UTC)
And Firefox too, just to cover all bases. Also the bottom part of the page seems to be buggy too, I have to tab through the page and hit enter on the upload button to be able to upload images now because the button itself doesn't work. =( - Doodleplex 20:23, 16 March 2016 (UTC)
The upload button works in our test environment so at least it wouldn't appear to be a MediaWiki-specific bug. I'll investigate that as well. Thank you for pointing it out. Justin Lloyd (talk) 20:32, 16 March 2016 (UTC)
I would guess that its probably related to the "fix" implemented to work around "+" signs? (+10 Agony Infusion doesn't work either). -Chieftain AlexUser Chieftain Alex sig.png 20:46, 16 March 2016 (UTC)
I found a related issue in Phabricator ( so I applied a two-line fix to GlobalFunctions.php (lines 433 and 444 in the code at that link) and the affected pages appear to work now. Let me know if you see any further issues regarding this. Justin Lloyd (talk) 20:52, 16 March 2016 (UTC)
Just noticed your comment about plus signs as well. I'll see if a similar fix helps in our test environment. Justin Lloyd (talk) 20:57, 16 March 2016 (UTC)
Actually plus signs seem dangerous, though I have another place I can look regarding that. Justin Lloyd (talk) 21:00, 16 March 2016 (UTC)
Might also be related to why the link option in #ask (Example), which generates a link to Special:Ask, doesn't work at all now.--Relyk ~ talk < 21:17, 16 March 2016 (UTC)
For reference sake, Justin says via email that he has fixed the plus sign bug on all language wikis. -Chieftain AlexUser Chieftain Alex sig.png 17:25, 18 March 2016 (UTC)
Is the problem with #ask something related to a server software (e.g. Semantic MediaWiki) or content (i.e. that you guys can change)? -Stephane Lo Presti talk 22:06, 18 March 2016 (UTC)
The issue seems more like MediaWiki not liking the special characters in the URL generated by SMW. It's not a significant concern. The only thing I've used it for is links to query examples. Special:Ask itself uses an alternative way of forming the URL that works perfectly fine. The other site I checked had no problem handling the URL link generated by SMW.--Relyk ~ talk < 01:30, 19 March 2016 (UTC)

No Ampersands[edit]

(Reset indent) Hello, pages with ampersand also have this issue (fr:Chercheuse senior de PR&T Takka), thanks --IruleManik (talk) 08:38, 29 March 2016 (UTC)

I've fixed the ampersand issue. Justin Lloyd (talk) 21:45, 29 March 2016 (UTC)
Apparently pressing "edit" or "history" on these pages takes you to half the page title. e.g. go to Assist PR&T Esoterics with ooze research + press "edit" at the top :( -Chieftain AlexUser Chieftain Alex sig.png 19:07, 3 August 2016 (UTC)
I reported the issue in the wrong place ([1]). All pages with ampersand:
  titlematch = %&%
  columns = 3
  format = ,\n* [[%PAGE%]],,
The preceding unsigned comment was added by BryghtShadow (talkcontribs) at 03:47, 20 August 2016‎ (UTC). Edit: Forgot to sign. --BryghtShadow (talk) 03:49, 20 August 2016 (UTC)
Apparently it worked at one time because Talk:PR&T Esoterics exists but I can't comment on that or edit PR&T Esoterics to kill some extra space at the top of the page. Perhaps pages with it should be moved, replacing the ampersand with "and" and putting a note on the top of the page about technical difficulties instead? - Doodleplex 22:52, 30 September 2016 (UTC)
Ok, so workaround for that, if you click edit you go to a new page, fine. Now go into the URL and change it like so: "" to "". Notice the manual change of "&" to "%26". Note this is by no means a fix to the problem, but simple a way to work around the issue until it is solved. -Darqam (talk) 23:04, 30 September 2016 (UTC)
NOOOOOPE, don't do that. You'll create a new page. -Darqam (talk) 23:06, 30 September 2016 (UTC)
Yeah I tried that. =< (edit) I see Alex is having fun with the PR page, good thing we don't need that as an acronym for anything lol. (edit #2) Apparently leaving feedback works cleanly. 0.o - Doodleplex 23:08, 30 September 2016 (UTC)
Doodle, it used to work. Every other wiki on the face of the planet apart from GW1W manages to have ampersands correctly encoded. Example: w:A&W Root Beer. Afaik from a quick google search the issue is probably related to our URL shortener rules. -Chieftain AlexUser Chieftain Alex sig.png 23:14, 30 September 2016 (UTC)
Seems like the problem must exist elsewhere. This entry here posted just about 2 months ago apparently offers a solution. -Darqam (talk) 23:15, 30 September 2016 (UTC)
This problem is actually a result of our wikis running behind Microsoft IIS/ARR load balancers (along with other critical stuff so we can't make global configuration changes), and IIS/ARR likes to handle with URL-encoding in a way interferes with URLs with special characters that MediaWiki permits. We do have a long-term plan for dealing with this, but that's a little ways off. Justin Lloyd (talk) 18:36, 5 October 2016 (UTC)

No File Upload Bug[edit]

Went to upload a better version of File:Euryale.jpg and got:

  • Could not read or write file "mwstore://local-backend/local-public/c/c3/Euryale.jpg" due to insufficient permissions or missing directories/containers.
  • Could not store file "/tmp/php2rXVH2" at "mwstore://local-backend/local-public/c/c3/Euryale.jpg".

Uploaded a picture of another NPC before and after that one, so it seems to just be this file. - Doodleplex 05:55, 17 August 2016 (UTC)

Should be fine now. I deleted it, and then pulled it back from the dead, and it seemed to work. However, the image is not appearing on the article, which I'm hoping is just a cache bug for now. —Ventriloquist 10:28, 17 August 2016 (UTC)

No 502 and 503 errors[edit]

Please report any 502 or 503 errors encountered whilst editing or using pages here, and include the date+time of the page attempted too.

Pages with percent in title for SMW special pages[edit]

Using 30% Magic Find Bonus as example.

I believe that's all the percent related issues with SMW's special pages. --BryghtShadow (talk) 05:08, 20 August 2016 (UTC)

No Protection reason not given[edit]

Pages which have been protected no longer show the reason for the protection when you view the source code. You're told "You do not have permission to edit this page, for the following reason:" but nothing else follows. Granted I may be crazy and the wiki never did provide the reason; it's been ages since I would have checked. This issue is also true on the GW1W. G R E E N E R 17:35, 28 September 2016 (UTC)

Can you provide some examples, please? —Ventriloquist 20:31, 28 September 2016 (UTC)
example (obviously you need to view the source whilst logged out or using a private browsing instance. - 21:19, 28 September 2016 (UTC)
Hot Pink Dye doesn't have one. The page history makes it self-explanatory though. The other pages on [2] show the reason as expected.--Relyk ~ talk < 01:12, 29 September 2016 (UTC)
Uh after removing the protection and then readding it, I'm still not seeing a reason given. Caveat: only when logged out. -Chieftain AlexUser Chieftain Alex sig.png 06:47, 29 September 2016 (UTC)
"06:46, 29 September 2016 Chieftain Alex (Talk | contribs) protected "Hot Pink Dye"‎ ‎[edit=autoconfirmed] (indefinite)‎[move=autoconfirmed] (indefinite) (Excessive spamming: Apologies for the lack of reason last time being confusing.) (hist) View full log" Is what I see on the hot pink dye page when editing now. Seems good? -Darqam (talk) 14:02, 29 September 2016 (UTC)
I'm still only seeing "You do not have permission to edit this page, for the following reason:" sans reason, even on those other pages. Using Firefox and Chrome, and via Monobook. I am viewing that while logged out. G R E E N E R 16:11, 29 September 2016 (UTC)
Yup. --Chieftain AlexUser Chieftain Alex sig.png 18:19, 29 September 2016 (UTC)
Would the problem be from the "view source" portion of it then? Since it seems like the "edit" page shows it fine. -Darqam (talk) 18:24, 29 September 2016 (UTC) - basically it omits the useful information as to precisely why the page was protected (which is stupid). I suppose we could write some javascript to insert it. -Chieftain AlexUser Chieftain Alex sig.png 19:07, 29 September 2016 (UTC)
Yeah. It was brought to my attention after I protected a page for the third time in a rather snide way. A contributor pointed out that I couldn't get frustrated with people for not understanding a message they weren't receiving. G R E E N E R 20:04, 29 September 2016 (UTC)
It's the same behavior as Wikipedia, so looks designed that way. That's very unhelpful behavior by Mediawiki...--Relyk ~ talk < 20:18, 29 September 2016 (UTC)
// Display protection log information for users who cannot edit protected pages
function anonymousQueryProtectionLog () {
    if ( mw.config.get('wgAction') === 'edit' && document.getElementsByClassName('permissions-errors')[0] != null ) {
        // Helper function to display times and dates correctly
        function padzero (s) {  return (s < 10 ? '0' : '') + s; }

        // Query the wiki API to fetch the protection log details
        var qstr = '/api.php?action=query&format=json&list=logevents&letype=protect&letitle='+encodeURIComponent(mw.config.get('wgPageName'))+'&lelimit=1i&leprop=title|user|timestamp|parsedcomment|details';
            var data = querydata.query.logevents[0];

            // Pages protected prior to 2015 don't return a timestamp or user.
            // Give up because there isn't any useful data available.
            if (!('timestamp' in data)) {
                console.log('Page was protected prior to 2015.');
            var comment = ''; if (data.parsedcomment !== '') { comment = '<span class="comment">('+data.parsedcomment+')</span>'; }
            var details = data.params[0], ptype = 'semi-protected', pexplain = 'registered users';
            if (details.match(/^[edit=sysop]/i)) { ptype = 'protected';  pexplain = 'users with administrator privileges'; }

            // Convert the given mediawiki timestamp string 'YYYY-MM-DDThh-mm-ssZ' into something we can use
            var timestamp = data.timestamp;
            var date = new Date(timestamp.substr(0,4), timestamp.substr(5,2), timestamp.substr(8,2), timestamp.substr(11,2), timestamp.substr(14,2), timestamp.substr(17,2));
            var datestring = padzero(date.getUTCHours()) + ":" + padzero(date.getUTCMinutes()) + ", " + padzero(date.getUTCDate()) + " " + mw.config.get('wgMonthNames')[date.getUTCMonth()] + " " + date.getUTCFullYear();

            // Generate a box identical the default mediawiki protection log message for logged in users
            var boxString = '<div class="mw-warning-with-logexcerpt mw-content-ltr" dir="ltr" lang="en">'
                             +'<b>Warning:</b> This page has been <b><a href="/wiki/Special:ProtectedPages" title="Special:ProtectedPages">'+ptype+'</a></b>, so that only '+pexplain+' can edit it.\n'
                             +'<li class="mw-logline-protect">'+datestring+' <a href="/wiki/User:'+encodeURIComponent(data.user)+'" title="User:'+data.user+'" class="mw-userlink">'+data.user+'</a> <span class="mw-usertoollinks">(<a href="/wiki/User_talk:'+encodeURIComponent(data.user)+'" title="User talk:'+data.user+'">Talk</a> | <a href="/wiki/Special:Contributions/'+encodeURIComponent(data.user)+'" title="Special:Contributions/'+data.user+'">contribs</a>)</span> protected "<a href="/wiki/'+encodeURIComponent(data.title)+'" title="'+data.title+'">'+data.title+'</a>" '+details+' '+comment+' <span class="mw-logevent-actionlink">(<a href="/index.php?title='+encodeURIComponent(data.title)+'&action=history" title="'+data.title+'">hist</a>)</span> </li>\n'
                            +'<a href="/index.php?title=Special:Log&page='+encodeURIComponent(data.title)+'&type=protect" title="Special:Log">View full log</a>'
^That's my proposal. It'd probably go in the bottom of the common.js. --Chieftain AlexUser Chieftain Alex sig.png 21:44, 29 September 2016 (UTC)
Out of curiosity, is 2015 a hard cut-off for a reason? Or will it be a cut-off which slowly moves forward as the wiki forgets things? (I noticed such an oddity with the abuselog API). G R E E N E R 16:30, 30 September 2016 (UTC)
I figure the internal table that stores the list of all protected pages used on Special:ProtectedPages was introduced circa 2015, you can see the timestamp/user are blank for the earlier ones. Abuselog used to be limited to a few months of data before that was changed. -Chieftain AlexUser Chieftain Alex sig.png 21:55, 30 September 2016 (UTC)

Is there any way I can convince you to do a trial run of that code on the gw1w at some point? I'll pay you in ToT bags ; ) G R E E N E R 19:07, 22 October 2016 (UTC)

Paste it straight on to gw1:MediaWiki:Common.js. -Chieftain AlexUser Chieftain Alex sig.png 19:39, 22 October 2016 (UTC)
Looks great, thanks Alex! Farming ToT bags for you now. G R E E N E R 20:05, 22 October 2016 (UTC)