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

Bugs / requests related to MediaWiki 1.30 upgrade[edit]

Please add new bug reports in this section with === heading level three titles ===. --Chieftain AlexUser Chieftain Alex sig.png 18:21, 20 March 2018 (UTC)

Yes Extension:NewUserMessage[edit]

We didn't ask for this, and when poorly configured it starts by pasting a user's real name into a broken template generating two redlinks. Can this be disabled? (I've blocked the account it supposedly edits from but I doubt that will do anything) -Chieftain AlexUser Chieftain Alex sig.png 18:30, 20 March 2018 (UTC)

Justin is in the process of disabling this. It seems like a good idea but we don't want to force anything onto the community. If you or someone else thinks it's worth properly configuring it, let us know --Stephane Lo Presti talk 18:57, 20 March 2018 (UTC)

Yes Extension:DismissableSiteNotice[edit]

Could the dismissable function be enable for anonymous users? mw:Extension:DismissableSiteNotice#Configuration (this should be a one-liner with $wgDismissableSiteNoticeForAnons) -Chieftain AlexUser Chieftain Alex sig.png 18:35, 20 March 2018 (UTC)

Justin just made this change, let us know if this works. --Stephane Lo Presti talk 19:18, 20 March 2018 (UTC)

No JQMIGRATE console message[edit]

I get the following message whenever I visit any page in the console:

JQMIGRATE: Migrate is installed with logging active, version 3.0.1-pre

It sounds like we have some kind of optional logging switched on. Can this be switched off? -Chieftain AlexUser Chieftain Alex sig.png 18:36, 20 March 2018 (UTC)

Alex, it looks like this is coming from https://github.com/wikimedia/mediawiki/blob/master/resources/lib/jquery/jquery.migrate.js#L53. I'm not seeing any obvious way to disable that particular message, but I'm not a JavaScript expert. Any suggestions? Justin Lloyd (talk) 19:28, 20 March 2018 (UTC)
Drat, I thought it might have had some obvious source or on/off switch. I guess we can live with it. -Chieftain AlexUser Chieftain Alex sig.png 19:32, 20 March 2018 (UTC)

Yes Gallery images are being pulled from Wikipedia[edit]

In certain cases where the article (only examples I have at the moment are for trinkets) shares the same name as a Wikipedia article (and perhaps doesn't already have gallery images), it seems like Wikipedia images are being shown in the gallery of the infobox, e.g., Charisma, Jade Pendant. --Floodbars (talk) 00:57, 21 March 2018 (UTC)

Not sure what the cause of this is yet, but a brief check suggests its not SMW related for once. (can replicate issue with [[File:Charisma.jpg]] on an otherwise empty page. -Chieftain AlexUser Chieftain Alex sig.png 07:50, 21 March 2018 (UTC)
Could this be InstantCommons? G R E E N E R 09:17, 21 March 2018 (UTC)
Yes, this is InstantCommons. I enabled it when installing the WikiLove extension to enable the built-in awards. I've gone ahead and disabled InstantCommons. Let me know if there are any further issues regarding this. Justin Lloyd (talk) 11:43, 21 March 2018 (UTC)

Yes User common.js not loading correctly[edit]

In the German wiki, I have an own common.js that loads three extra buttons into the toolbar of the editor. For some reason, those buttons are not loaded anymore automatically. To load them, I have to manually purge cache (shift + strg + r) within the opened/edited page, then the page reloads and they appear just as they should. Does anyone have this problem too? Any ideas? Vaetir (talk) 12:25, 21 March 2018 (UTC)

Heya. I expect it's a race condition where you're asking for a module when the wiki hasn't finished loading the "mediawiki toolbar" javascript module yet. Sometimes the User JS is slow and so it will load slowly enough for it to already have finished loading the "mediawiki toolbar" module. Try using RLQ.push at the front of it, i.e.
RLQ.push(function () {
    if ( mw.toolbar ) {
        var button1 = {
            'id': "button-gw2wiki-uebersetzung",
            'imageFile': "/images/f/f0/Bug_Icon.png",
            'speedTip': "Vorlage Übersetzung",
            'tagOpen': "{"+"{Übersetzungsfehler|",
            'tagClose': "|{"+"{subst:#timel:d.m.Y}}|}}",
            'sampleText': "Beschreibung"
        };
        var button2 = {
            'id': "button-gw2wiki-loeschantrag",
            'imageFile': "/images/f/f3/Müllhaufen_Icon.png",
            'speedTip': "Löschantrag",
            'tagOpen': "{"+"{Löschantrag|",
            'tagClose': "}}",
            'sampleText': "Umbenannt"
        };
        var button3 = {
            'id': "button-gw2wiki-fehlendeinfos",
            'imageFile': "/images/b/b2/Datei_verbessern_Icon.png",
            'speedTip': "Fehlende Informationen",
            'tagOpen': "{"+"{Fehlende Informationen|",
            'tagClose': "}}",
            'sampleText': "Beschreibung"
        };
        mw.toolbar.addButtons([button1, button2, button3]);
    }
});
-Chieftain AlexUser Chieftain Alex sig.png 19:59, 21 March 2018 (UTC)
Hi Alex, thank you very much for your help. To give an update: Unfortunately, your solution didn't work for me. I also forgot that the German wiki has some buttons for the toolbar in its global common.js, so I wasn't the only user affected. As seen in the link, our administrator Think was able to fix this problem with some Java magic, so I guess this counts as solved. – Vaetir (talk) 21:56, 24 March 2018 (UTC)

Yes Broken Ingredient Links[edit]

I am unsure if this relates to the upgrade, or is more likely a result of authorship errors; however, on Bag, two of the 32-slot bags have all of their ingredient links broken, not rendering, and showing two separate errors. If this is due to a deeper issue, then there may be more broken links yet discovered. --Bandlero (talk) 11:24, 23 March 2018 (UTC)

Also seen on Gift of Dragon Magic --Eggbutt (talk) 17:42, 24 March 2018 (UTC)
Blanked/restored the pages with the recipes. I suspect this is mostly unrelated SMW bugs that usually occur when the wiki is being editing whilst its busy behind the scenes. -Chieftain AlexUser Chieftain Alex sig.png 18:29, 24 March 2018 (UTC)

Yes Semantic galleries providing image sizes in caption text[edit]

We knew about this prior to the MW upgrade, just documenting here that I've added a few lines to the Common.js to remove them. -Chieftain AlexUser Chieftain Alex sig.png 18:24, 24 March 2018 (UTC)

No Form:Parameter check[edit]

I'm not sure why, but I'm getting the following message when trying to visit the Form:Parameter check page.

MediaWiki internal error.

Original exception: [553e94dad7ff1bc74c3d2349] 2018-04-01 17:35:28: Fatal exception of type "MWException"

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.

--Chieftain AlexUser Chieftain Alex sig.png 17:35, 1 April 2018 (UTC)

apparently we can't use {{Special:RunQuery/Parameter check}} anymore, but we can still use https://wiki.guildwars2.com/wiki/Special:RunQuery/Parameter_check . Wierd. -Chieftain AlexUser Chieftain Alex sig.png 17:38, 1 April 2018 (UTC)
Pretty sure the documentation suggests it should still be possible too. -Chieftain AlexUser Chieftain Alex sig.png 17:41, 1 April 2018 (UTC)

Yes Page: Faction Provisioner[edit]

When loading this page in Chrome, not all of the Buy/Sell Prices load. Refreshing will some times result in a different number of prices being shown but it only ever seems to be the first 1-18 items. Loading the page in Firefox works perfectly and displays all the buy/sell prices for every item. The preceding unsigned comment was added by Dravis (talk) at 13:53, 4 April 2018‎ (UTC).

This is to do with Chrome processing javascript faster than Firefox does. Essentially Chrome has run the widget script (added by every Template:Tp occurence) prior to finishing rendering the HTML added by the widget. I think this is called a "Race" condition. When I tested it, I found that Chrome fires the script after 30 out of 67 elements had loaded. Firefox is slow enough on this page to run the script when 67/67 have loaded. Firefox does however routinely fail to render the TP prices on other pages too though. I'll have a think about how to fix this. -Chieftain AlexUser Chieftain Alex sig.png 17:20, 4 April 2018 (UTC)
Should be fixed, albeit I'll have to go looking for old direct usage of Widget:TP prices. -Chieftain AlexUser Chieftain Alex sig.png 18:39, 4 April 2018 (UTC)

No Oddity from Gw1w[edit]

A <s> had been placed in a subsection's title. With the update, the TOC applied the strike to the entire page. Given that the strike and TOC had been there with no ill effect for quite some time, I'm going to guess that the new TOC system does not sanitize the code.

I'm quite sure that the source is the TOC, as it was applying the strike to everything after the TOC, rather than everything after the actual subsection where the strike existed. G R E E N E R 18:50, 20 March 2018 (UTC)

It's odd this hasn't appeared struck-through before to be honest, as I would have expected the broken <s> to have caused the rest of the page to be struck through. Maybe we just need to keep an eye out for other sleeping broken formatting. -Chieftain AlexUser Chieftain Alex sig.png 19:11, 20 March 2018 (UTC)

Some Used In MF recipe bugs[edit]

Spark of Sentience and Mystic Tribute both have broken recipe entries for Aurora (but the other 2 ingredients for Aurora are working correctly, and everything else on Mystic Tribute is working fine). I've purged the pages, removed and replaced the recipe list template from one of them (and blanked the page afterwards too), and have tried inputting their name into recipe list on different pages (with the same broken result) --Gimmethegepgun (talk) 21:36, 29 March 2018 (UTC)

Fixed this immediatly for a legendary item. Your steps where correct, but instead of applying these delete/purge procedure to the broken recipe pages, you should have done this on Aurora.
Alex describes the procedure as follows: "Generally blank+save the page, purge the page, add the top infobox only+save, purge, add the recipe, purge. It sucks but it usually works. -Chieftain AlexUser Chieftain Alex sig.png".
For anyone else interested, there's a discussion about this topic at User talk:Chieftain Alex#SMW bug. --Tolkyria (talk) 12:01, 31 March 2018 (UTC)

Yes SMW bug[edit]

moved from User talk:Chieftain Alex#SMW bug

What's the trick to get bugged recipes like Mystic Caller working? I managed to fix Corsair Sharpening Stone at Kralkatite Ore and 28-Slot Cowrie League Saddlebag at Tailor but broke with my edit 32-Slot Cowrie League Saddlebag at Tailor. There are some more ? [[|link=?|20x20px]] ? at Artificer, Jeweler, Leatherworker, Weaponsmith --Tolkyria (talk) 11:39, 30 March 2018 (UTC)

Generally blank+save the page, purge the page, add the top infobox only+save, purge, add the recipe, purge. It sucks but it usually works. -Chieftain AlexUser Chieftain Alex sig.png 11:41, 30 March 2018 (UTC)
Ok, thanks, so thats what I already basically did. I just got worried since I broke the 32-slot box. Another question which might be related: Lesser Elixir C was created some weeks ago and first labeled as Utility and later correctly labeled as Trait. Now #ask-ing for Utility and Elixir still gives it as a result.
See {{#ask: [[Has skill context:: Utility]][[Has skill type::Elixir]]| format = list }} has the following output
Elixir B, Elixir C, Elixir R, Elixir S, Elixir U
So does the same procedure solve this case too? --Tolkyria (talk) 11:50, 30 March 2018 (UTC)
Apparently it didn't work that time. I deleted the page, purged it and pasted the old content in. Sorry I've lost the page history but at least it works. -Chieftain AlexUser Chieftain Alex sig.png 12:21, 30 March 2018 (UTC)
Thanks again. Some similar bug may appear with Guardian's third cast Final Charge of Mantras, some of them were labeled as Mantras upon creation but so far I haven't tested these. I also found some more pages not displaying recipe components, generally the new >20 slots bags seems to be affected very often, see Spool of Deldrimor Thread or Supreme Rune of Holding. But as you said, this "sucks", it might need some free time to fix this. --Tolkyria (talk) 08:39, 31 March 2018 (UTC)
Most of these pages were modified around Path of Fire release - this was not a good period for the wiki + lots of saved pages didn't get fully submitted it seems. --Chieftain AlexUser Chieftain Alex sig.png 09:16, 31 March 2018 (UTC)
I've had another go at deleting/restoring the contents of the pannier bags. Keep telling me if you're finding more bugs and i'll go nuke them. -Chieftain AlexUser Chieftain Alex sig.png 09:28, 31 March 2018 (UTC)
Just browsing through the PoF matrials, I found:
Edit: Thats it for all pages which Refinement links to. --Tolkyria (talk) 09:51, 31 March 2018 (UTC)
Well, it's getting too much now, just giving the pages where the bugged recipe is:
Wanderer's Intricate Gossamer Insignia, Viper's Intricate Gossamer Insignia, Vigilant Intricate Gossamer Insignia, Minstrel's Intricate Gossamer Insignia, Commander's Intricate Gossamer Insignia, Oiled Gossamer Helm Padding, Oiled Gossamer Helm Strap, Oiled Hardened Boot Upper, Oiled Hardened Boot Sole, Oiled Hardened Glove Lining, Oiled Hardened Glove Panel, Oiled Hardened Shoulderguard Padding, Oiled Hardened Shoulderguard Panel, Oiled Hardened Trouser Padding, Oiled Hardened Trouser Panel. Mostly this are related to HoT stats armors, commanders, vipers, wanderers, etc.. --Tolkyria (talk) 10:04, 31 March 2018 (UTC)
As I brought up in the wiki bug page, Spark of Sentience and Mystic Tribute are broken for Aurora as well --Gimmethegepgun (talk) 10:59, 31 March 2018 (UTC)
Alright that's half an hour of my life I won't get back. -Chieftain AlexUser Chieftain Alex sig.png 14:15, 31 March 2018 (UTC)

(Reset indent) Looked through half of the wiki, crafting materials, insignia, inscriptions, etc... corrected ~10 bugged recipes. I think we catched most of the bugged recipe lists. --Tolkyria (talk) 19:49, 31 March 2018 (UTC)

Database error when trying to merge accounts[edit]

I just attempted to merge two accounts via Special:UserMerge, and received this error: [a4a1f7d9443bf69e223961ff] 2018-05-10 20:44:33: Fatal exception of type "Wikimedia\Rdbms\DBQueryError". G R E E N E R 20:47, 10 May 2018 (UTC)

Special:Contributions/Mistress Elemental vs Special:Contributions/Mistesrian.
I'm wondering if Special:RenameUser (built into mediawiki core) is the more recent version of Special:UserMerge (provided by a mediawiki extension)? See if RenameUser works -- if it does, then I think we can get Justin to remove mw:Extension:UserMerge. -Chieftain AlexUser Chieftain Alex sig.png 22:06, 10 May 2018 (UTC)
Also a quick check of mediawiki talkpages suggests the user might have Watched the same pages? (getting the user to blank their watchlists might work) -Chieftain AlexUser Chieftain Alex sig.png 22:08, 10 May 2018 (UTC)
FWIW, I checked the error logs and the message about the error was from line 342 in MergeUser.php, which is in the function deduplicateWatchlistEntries(), so I think you're on the right track, Alex, with the watchlist cleanup. Justin Lloyd (talk) 16:27, 11 May 2018 (UTC)

Cookie notification can't be permanently dismissed[edit]

I'm being prompted by the new cookie notification every time I open the edit box, compare revisions, or look at a page history. (Using Internet Explorer) --Idris (talk) 18:52, 25 May 2018 (UTC)

Same happens with Google Chrome. Sime (talk) 19:13, 25 May 2018 (UTC)
Compare and contrast the following two cookies: CookieNotification (broken) versus dismissableSitenotice (working).
I suspect that the root cause of this is that the "path" parameter of the cookie is set as "/wiki/". It needs to be set as "/".
Any page visited for edit/history/actions uses the url format wiki.guildwars2.com/index.php? and therefore does not contain "/wiki/", hence the cookie notice shows up. -Chieftain AlexUser Chieftain Alex sig.png 20:00, 25 May 2018 (UTC)
Also in case anyone else hasn't realised, the cookie notice is blocked with uBlockOrigin by default. -Chieftain AlexUser Chieftain Alex sig.png 20:02, 25 May 2018 (UTC)

(Reset indent) We're sorry about this, one of our web programmer has been working on trying to fix the situation before the 3-day weekend. --Stephane Lo Presti talk 22:47, 25 May 2018 (UTC)

Update: yay! Our web programmer found the fix, it should be working now but let us know if you still see some weirdness --Stephane Lo Presti talk 22:52, 25 May 2018 (UTC)
While it works fine on my phone/Google Chrome, my ipad(which I believe uses Safari) is still having the issue. =( - Doodleplex 00:28, 26 May 2018 (UTC)
I can confirm that this is still an issue with Safari. --Cali (talk) 00:58, 26 May 2018 (UTC)
It may be a mobile thing, my work computer(a Mac) has no issues that I can tell, but it is being a bit weird on my phone now at random intervals. - Doodleplex 01:10, 26 May 2018 (UTC)
I'm actually using a desktop. Perhaps it's which version of Safari is being used? Mine is version 11.0.2. --Cali (talk) 01:44, 26 May 2018 (UTC)
Hm, the notification is now no longer showing up. Perhaps it just took a little longer for the fix to activate. --Cali (talk) 03:26, 26 May 2018 (UTC)
I spoke too soon; it's still happening. Think I'll hold off on commenting further until more time has passed. --Cali (talk) 03:44, 26 May 2018 (UTC)
Yeah, I'm also still getting it, but it's happening less often than it was before. --Idris (talk) 04:01, 26 May 2018 (UTC)
I guessed wrong on the cookie thing then :( -Chieftain AlexUser Chieftain Alex sig.png 08:45, 26 May 2018 (UTC)
To be able to investigate this bug, we need complete details from someone who's currently experiencing it, meaning: hardware platform, OS versions, browser version, exact steps to reproduce the bug. Thanks! --Stephane Lo Presti talk 15:27, 29 May 2018 (UTC)
I'm using an iMac with High Sierra 10.13.2 and Safari 11.0.2. I generally skim Recent Changes by clicking on "diff" and opening a new window. Of the last 11 pages I checked, the cookie notification showed up 2 times on the new page. It's definitely showing up less often than it used to, but it's not consistent, so I can't provide exact steps to reproduce it. --Cali (talk) 22:54, 29 May 2018 (UTC)
We've updated our code on the backend. Could you check if the problem still occurs? --Stephane Lo Presti talk 17:28, 1 June 2018 (UTC)
I think you guys have solved it. After looking at 20 pages, the notification didn't show up once. Thanks to everyone who worked on fixing it! --Cali (talk) 23:23, 1 June 2018 (UTC)
(Reset indent) I've rewritten the cookie JS code with my suggested changes: User:Chieftain Alex/sandbox5. Among the issues (1) there was .toGMTString() which isn't widely supported and (2) the regular expression for the cookie didn't look to be functioning properly. -Chieftain AlexUser Chieftain Alex sig.png 13:17, 26 May 2018 (UTC)
Not sure if anything is needed from us based on what you did? --Stephane Lo Presti talk 15:27, 29 May 2018 (UTC)
Well the cookie code is set serverside by you guys, none of us on the wiki can change it, we can however view it since it downloads it every time we visit a page. -Chieftain AlexUser Chieftain Alex sig.png 17:04, 29 May 2018 (UTC)