Guild Wars 2 Wiki:Reporting wiki bugs/archive 9

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

(Small bug that I can't fix) Semantic data for Two-Handed Training does not have Fury flagged

I was looking at Fury and noticed that the entry for Two-Handed Training does not have the word Fury bolded, as it is bolded in other entries. A quick check of the Semantic page showed that the keyword Fury is not flagged on that page. (To compare, No Quarter does have it flagged.) (And I don't have the power to edit Semantic pages, so I'm reporting it so someone who can can.) PaladinOne (talk) 21:01, 22 February 2018 (UTC)

It's not a semantic issue, the word just wasn't wiki-linked in the description (using [[]]). Linking it fixed the problem. —Ventriloquist 21:26, 22 February 2018 (UTC)

(Edit conflict) I was also to find Two-Handed Training querying fury just like how it's attached to No Quarter. Is this what you're referring to in terms of the semantic properties? Also, thanks for the linking, Vent. G R E E N E R 21:30, 22 February 2018 (UTC)

"Two-handed querying Fury" was exactly what I was talking about, and prior to Vent fixing it, it was not doing that. Good to know (for future reference) that this problem can be fixed by editing the normal page; I was under the incorrect assumption that Special:Browse was managed by something different in this context. PaladinOne (talk) 23:11, 22 February 2018 (UTC)

Bugs / requests related to MediaWiki 1.30 upgrade

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

Extension:NewUserMessage

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 Alex 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)

Extension:DismissableSiteNotice

Could the dismissable function be enable for anonymous users? mw:Extension:DismissableSiteNotice#Configuration (this should be a one-liner with $wgDismissableSiteNoticeForAnons) -Chieftain Alex 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)

JQMIGRATE console message

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 Alex 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 Alex 19:32, 20 March 2018 (UTC)

Gallery images are being pulled from Wikipedia

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 Alex 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)

User common.js not loading correctly

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 Alex 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)

Broken Ingredient Links

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 Alex 18:29, 24 March 2018 (UTC)

Semantic galleries providing image sizes in caption text

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 Alex 18:24, 24 March 2018 (UTC)

Form:Parameter check

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 Alex 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 Alex 17:38, 1 April 2018 (UTC)

Pretty sure the documentation suggests it should still be possible too. -Chieftain Alex 17:41, 1 April 2018 (UTC)

Page: Faction Provisioner

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 Alex 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 Alex 18:39, 4 April 2018 (UTC)

Oddity from Gw1w

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.

• Version with the strike
• Removing the strike from a title

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 Alex 19:11, 20 March 2018 (UTC)

Some Used In MF recipe bugs

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 Alex".

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)

SMW bug

→ 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 Alex 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 B#WvW,PvP, Elixir C, Elixir of Anguish, Elixir of Anguish#WvW,PvP, Elixir of Bliss, Elixir of Ignorance, Elixir of Risk, Elixir of Risk#WvW,PvP, Elixir R, Elixir S, Elixir U, Elixir U#PvP

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 Alex 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 Alex 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 Alex 09:28, 31 March 2018 (UTC)

Just browsing through the PoF matrials, I found:

• Mordant Inscription bugged at Pulsing Brandspark
• Insignia of the Harrier bugged at Pulsing Brandspark
• Pulsing Brandspark bugged at Eye of Kormir --Tolkyria (talk) 09:33, 31 March 2018 (UTC)
• 20 Slot Orichalcum Box bugged at Superior Rune of Holding
• Bringer's Orichalcum-Imbued Inscription bugged at Orichalcum Plated Dowel
• Giver's Iron-Plated Inscription bugged at Iron Plated Dowel
• Giver's Darksteel Imbued Inscription bugged at Darksteel Plated Dowel
• Giver's Steel-Plated Inscription bugged at Steel Plated Dowel
• Bringer's Orichalcum-Imbued Inscription bugged at Orichalcum Plated Dowel
• The Twins' Grieving Inscription bugged at Deldrimor Steel Plated Dowel
• Gold Bound Matrix bugged at Gold Ingot
• Tixx's Giver's Insignia bugged at Damask Patch
• Warbeast Hardened Helmet Strap bugged at Cured Hardened Leather Square
• Warbeast Orichalcum Gauntlet Lining bugged at Bolt of Gossamer

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 Alex 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)

Cookie notification can't be permanently dismissed

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 Alex 20:00, 25 May 2018 (UTC)

Also in case anyone else hasn't realised, the cookie notice is blocked with uBlockOrigin by default. -Chieftain Alex 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. =( - Do_odleplex 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. - Do_odleplex 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 Alex 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 Alex 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 Alex 17:04, 29 May 2018 (UTC)

Show base ingredients no longer works unless a crafting discipline is selected manually

The Show base ingredients query seems to have broken recently, for a large number of recipes. Example: Xunlai Electrum Ingot: none of the ingots are broken down into their base ingredients, and neither is the Lump of Mithrillium. You only get the break down into the base ingredients after selecting the correct crafting discipline. This did not use to be necessary and makes no sense in this case, because Xunlai Electrum Ingots can only be crafted by Jewellers, so there should be no ambiguity about which recipe to use. But apparently the query has problems finding the recipe unless the crafting discipline is given. Gudy (talk) 05:30, 24 September 2018 (UTC)

Weird, i was trying to fix something else but i've reverted my changes which are no doubt the cause. -Chieftain Alex 06:09, 24 September 2018 (UTC)

Database error when trying to merge accounts

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 Alex 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 Alex 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)

Microsoft Edge does not load pages properly when previewing edits

Steps to reproduce

1. Open Microsoft Edge and navigate to the wiki.
2. Press edit on any page, type your edits then press preview
3. Instead of loading a preview, it loads no html content and displays the page as simply #.

Screenshot

bug screenshot

issue reported by User:Mervil. --Chieftain Alex 21:51, 9 August 2018 (UTC)

I ended up implementing a script to disable the Show preview and Show changes buttons for Edge. -Chieftain Alex 17:33, 25 September 2018 (UTC)

Update: This seems to have been resolved by Microsoft at some point, so I've removed the bandaid script from common.js. Initial tests on MS Edge appear okay. -Chieftain Alex 06:32, 11 July 2019 (UTC)

Coordinate Map Bug?

Either I'm bugged or the interactive map is, but it doesn't seem to let me see any of the maps from lws4. For example, I input the correct coords for General Almorra Soulkeeper and while it does show the wp nearby, it doesn't show any of the Jahai Bluffs, much less the section she's in. It just shows a yellow circle around the undetailed "undiscovered" version of the map ~ Trevor95251 16:08, 25 September 2018 (UTC)

That is an issue with the official API; they haven't updated it since Path of Fire release due to ArenaNet recruitment inadequacies. Because of this underlying issue I've added some tiles to the wiki as a temporary measure. Set | localtiles = true in any infobox for LWS4 maps. -Chieftain Alex 17:14, 25 September 2018 (UTC)

Example fix -Chieftain Alex 17:16, 25 September 2018 (UTC)

Semantic item search (special:ask) pages do not work due to missing Template:Item icon with tp

It just shows the list of redlinks to that template. 62.249.146.146 05:20, 11 July 2019 (UTC)

Hi. Good spot - I eventually worked out that you'd followed a link from Template:Contains upgrade component (with format=link set). The cause of the "bug" was that I had deleted the apparently unused template. As this is only used on five pages across the entire wiki I'm not too surprised that nobody had noticed it was missing... I've restored the deleted template and will add links between the two templates so that I don't make the same mistake again in the future. Thanks. -Chieftain Alex 06:25, 11 July 2019 (UTC)

The trait-list of the Mesmer's Illusion traitline shows an old version of a trait

List of mesmer traits shows "Phantasmal Force -> Phantasms' damage permanently increases whenever they attack or gain might."

This is an old version of the trait. I don't know how to update this. —The preceding unsigned comment was added by Lexxa (talk) at 22:54, 9 October 2019‎ (UTC).

Fixed by deleting and restoring the page (history lost) to clean the SMW cache. -Chieftain Alex 23:21, 9 October 2019 (UTC)