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 related to the server upgrade[edit]

No Incomplete page loads[edit]

So I've had this 3 times now, example: The page is no longer loading, nor does it 'give up after a long time'. It kind of just stops there after 3-4 seconds. I forgot to look at console when this happens if anything appeared, but will next time. I also got when reloading the shown page (this has only happened once so far). -Darqam 20:31, 8 November 2017 (UTC)

I'm not sure about this one, as I don't understand that error message. Can anyone else provide some further insight about this? Justin Lloyd (talk) 21:22, 8 November 2017 (UTC)
I believe it's a 416 error (, which could make it a one time 'my problem' issue. Until I get it once more or someone else reports it. I'm going to assume (t least on my end) that the error was a one off thing. The incomplete page load seems to also be gone, so this might have all been some browser screwery on my end. -Darqam 13:13, 9 November 2017 (UTC) -Chieftain AlexUser Chieftain Alex sig.png 18:10, 9 November 2017 (UTC)
Also everything is horribly slow. -Chieftain AlexUser Chieftain Alex sig.png 01:15, 11 November 2017 (UTC)
That isn't just me? Thank god. I thought I was going crazy. I was all set to start deep cleaning files.--Rain Spell (talk) 02:24, 11 November 2017 (UTC)

I know these reports are almost 3-weeks old but I wanted to know if this still happening? --Stephane Lo Presti talk 00:16, 1 December 2017 (UTC)

Pressing edit on some pages right now is taking over a minute to load the editing window:
Also receiving 503 Gateway timed out, and 503 Backend fetch failed errors too, in addition to not loading some of the CSS files, making it look ugly as hell like the sections below. --Chieftain AlexUser Chieftain Alex sig.png 11:46, 28 January 2018 (UTC)
Alex, the 503s/Varnish errors from yesterday morning were an issue with one specific server and that issue has been resolved. Justin Lloyd (talk) 13:13, 29 January 2018 (UTC)

No Odd page loading/messed up UI[edit]

Idk if this is just a normal bug or one from the move. Was loading a page and it took 5s instead of 2. Looked like this and the lower half looked like this. I'm using Firefox. I could click on some links, but others (the bug notice) wasn't working/where it said it was. Refreshing fixed the problem, and I have no idea how it would be replicated, but it happened. --Rain Spell (talk) 20:05, 9 November 2017 (UTC)

Occasionally getting this issue along with slow page loads. I get the feeling that they're both somehow correlated due to high traffic, but that's just my opinion and I have no way of confirming my theory. Seeing as everyone here is having issue in Firefox (including myself) is it possible it could be browser-specific? Sythe 16:34, 13 November 2017 (UTC)

Are you two still experiencing slowness on the wiki after the past few weeks? --Stephane Lo Presti talk 00:16, 1 December 2017 (UTC)

I'm still experiencing slowness (especially when editing. Example: I added one link on the Fractal Console page (+18 characters) and it took a good 7 seconds to finish loading. Loading the edit page is usually fast.) I haven't had any more odd page loads though. Oh, and I updated to the new Firefox a few days ago as well, so it should be up to date. --Rain Spell (talk) 20:14, 1 December 2017 (UTC)
Sorry to hear that Rainspell! Is this slowness consistent, meaning that you experience it every day or every week, or something that occur occasionally? If you could provide us with more data (article you were editing, with corresponding date and time), it may help us with troubleshooting this. And if anybody else experiences this slowness, more data would be helpful. --Stephane Lo Presti talk 22:13, 12 December 2017 (UTC)
Earlier today was particularly slow - about 2 hours previous to this message. -Chieftain AlexUser Chieftain Alex sig.png 22:32, 12 December 2017 (UTC)
I've been experiencing it consistently with pretty much every single article I edit or create. Creating a page is slightly faster, but moving/changing names on things take 2-3s longer than normal. It's only since the move, as far as I know. Were the servers moved really far from where they were before? It used to be it'd only take 5s to load a page if it had a lot of calls, but editing any page from Lesser Call of the Wild to Jingo to Black Lion Weapon Arsenal takes 5-7s. Maybe I was just spoiled before, but having a consistent load time of 5-7s for editing pages drives me batty. My loading times for navigating to pages is within a second, however. As for date/time. Since it's every edit: here ya go:(--Rain Spell (talk) 03:38, 13 December 2017 (UTC)

This comment seems to have moved a bit to loading times but I'd like to add that my UI is doing the same thing as pictured above, a lot of information is being pushed to the bottom of the page in a single column. I'm using Google Chrome and it started when the PoF graphics were put in. It's been getting progressively over time as well it used to have the search bar up top where it normally should be but now even that is being pushed down to the bottom as well. Some of the pages are loading better than others but I'm not sure why this is happening at all, I have the latest version of Chrome and it used to work fine, on top of that my dad uses Internet Explorer and none of these UI problems are happening for him. This is what my pages usually look like but unfortunately no amount of refreshing has fixed this so I've solved the replication issues because it's always happening for me and it's reaching the point of becoming unusable. SherlyDame (talk) 17:30, 21 January 2018 (UTC)

Hum. Having logged into the wiki on Chrome (v63, 64 bit, Windows 10) I'm not finding any immediate issues with the appearance. I know with firefox it sometimes drops the connection when downloading the stylesheet and that renders like Rainspell's first image above - maybe Chrome does something worse.
Can you please confirm that (i) you've cleared your local browser cache to make sure you're fetching the most recent revision of the stylesheets (CTRL + F5), (ii) cleared your cookies (Chrome ... > Settings > Advanced > Clear browsing data), (iii) which wiki skin are you using (Special:Preferences > Appearances > Skin), (iv) does the clock show up at the top of the page? (if not, indicates javascript bug) --Chieftain AlexUser Chieftain Alex sig.png 18:09, 21 January 2018 (UTC)
Oh wow! I feel dumb, I just did the first thing and cleared the cache, it's totally fine now! I rarely do any clearing but it's never presented a problem like that before so I never think about it. Thanks for the help! SherlyDame (talk) 15:27, 25 January 2018 (UTC)
Lol don't worry about it. I would hope that we have enough users using a variety of browsers to be able to detect bugs quickly enough to at least identify them, if not sort them out. --Chieftain AlexUser Chieftain Alex sig.png 18:07, 25 January 2018 (UTC)

(Reset indent) To revisit the original bug reports here, I occasionally get the page looking like Rainspell's link ( The apparent cause on this occasion, reading the developer console in firefox, is that failed to load. -Chieftain AlexUser Chieftain Alex sig.png 18:03, 26 January 2018 (UTC)

Yes Increased ping time with bots[edit]

I used to run a deletion script which would just burn through a complete list in a few seconds flat, it seems to have a minimum delay of 5 seconds now. Is that intended? -Chieftain AlexUser Chieftain Alex sig.png 13:09, 18 November 2017 (UTC)

Hey Alex, it's not something we specifically set. Is this still happening? --Stephane Lo Presti talk 00:16, 1 December 2017 (UTC)
Yes, it happens with regular editing accounts too - there is a five second delay before any edit is submitted. (e.g. if i press submit now at 17:27:22, the edit only appears to process at 17:27:27). This doesn't seem like a lot but we used to be able to push through 100 bot edits per minute no problem (same routine would take 8 minutes now). -Chieftain AlexUser Chieftain Alex sig.png 17:28, 4 December 2017 (UTC)
Sounds like the same issue reported above. Do you have more data about the bots so we can look into logs? --Stephane Lo Presti talk 22:13, 12 December 2017 (UTC)
The circa five second delay between submitting edits and the corresponding page appearing is pretty consistent.
(i - now) I raised this issue above when deleting Erasculio's userpages - see these log entries. If you look you can see I've deleted roughly 12 pages per minute - this was using a deletion API script.
(ii - previously) Compare with these log entries earlier in October when I was running the same script to delete orphaned files, and was getting >150 pages per minute.
The script is the same so I'm guessing rate-limit or throttling somewhere else. -Chieftain AlexUser Chieftain Alex sig.png 22:43, 12 December 2017 (UTC)
Going to add on to this a bit. It would appear the edit/saving the edit is still very fast: I just did some testing while fixing some item stub tags and hit "save" with my bot, then opened the page right away and it was already updated, which would be about the same speed it would have shown me as being "saved" before the move. However, on the bot's end it was still showing as "saving". It's the same for regular editing as well, I just edited the sandbox, and had that page open on a separate tab. As soon as I hit save, I refreshed the other page, and it showed me my edit on the page, however the original page was still showing as "saving". So the edits are going through at the same speed, but the pages are just slow to show it after editing I guess? - Doodleplex 22:54, 27 December 2017 (UTC)
(Reset indent) When reading pages that I have not just edited, they load acceptably fast. The bit which is slow is (i) press edit until the source comes up, (ii) submitting edits until the new page comes up. I have renamed the topic title since it is not just limited to bots. -Chieftain AlexUser Chieftain Alex sig.png 22:36, 15 January 2018 (UTC)
This seems to have been fixed at some point. Getting good ping-times with AWB. -Chieftain AlexUser Chieftain Alex sig.png 21:05, 12 February 2018 (UTC)

No PoF interactive maps broken[edit]

The interactive maps for all 5 PoF map pages aren't working. It just shows a ~1/2 inch height black bar instead of the map. Domain of Istan is full size and shows the icons but the terrain map doesn't reach it so it's surrounded by black. I sampled some other maps from Core, HoT, and LWS3 and all the ones I checked are working fine --Gimmethegepgun (talk) 19:16, 2 December 2017 (UTC)

It's the API that is broken. For some reason when LWS4 E1 hit, the other maps got removed from the API. -Chieftain AlexUser Chieftain Alex sig.png 20:52, 2 December 2017 (UTC)

No Error 503 Backend fetch failed[edit]

Was editing a line of text on the Of Wiki of Gold page. Went to hit "Show Preview" and got the following page (text only):

Error 503 Backend fetch failed

Backend fetch failed
Guru Meditation:

XID: 73074799

Varnish cache server

I went back and tried hitting preview again and it worked fine. Just a cache issue?-

Oh, Browser is Firefox, newest version afaik.-Rain Spell (talk) 03:03, 9 December 2017 (UTC)

I'm getting this occasionally. -Chieftain AlexUser Chieftain Alex sig.png 13:30, 9 December 2017 (UTC)
Getting it again. Refreshing or pressing back and clicking the same link works, but it takes a good 10-15s. I think it's happening more on pages I've left open for an hour and come back to. Also, apparently others are experiencing similar. :
Error 503 Backend fetch failed

Backend fetch failed
Guru Meditation:

XID: 784826374

Varnish cache server

--Rain Spell (talk) 23:43, 12 January 2018 (UTC)

Yes Problems with random images on the Wiki?[edit]

moved from Talk:Main Page

I've been having problems seeing random images on this Wiki and I believe it's somehow related to how thumbnails are generated/cached in Google Chrome (like if you have a 100x100 pixel image and resize it to 50x50 pixels on a page).

  • Exhibit 1 - The images for Euryale and Street Rat don't appear for me on the Biography page
  • Exhibit 2 - If I click on the link for Street Rat, the link works just fine and I can clearly see the image
  • Exhibit 3 - If I then click on the BACK button in my browser, I can now see the Street Rat image

However, if I then click on the Euryale link to see the image, then go back - I can see the Euryale image but not the Street Rat image. And the images that don't work appear to be random per computer. For example, my work PC (Windows 7 Pro 64-bit, Google Chrome browser) doesn't show Euryale & Street Rat while my home PC (Windows 10 Home 64-bit, Google Chrome browser) does, but with other images not being displayed.

If I use Firefox to view the Biography page, I don't seem to have this problem... but I'd like to stick with Google Chrome if possible. Any idea how to fix this? The preceding unsigned comment was added by Kencussion (talkcontribs) at 22:28, 8 January 2018‎ (UTC).

Hi Kencussion, did this problem happen to you before, or is this something you noticed recently? Does a page reload fix the issue? Thanks --Stephane Lo Presti talk 16:49, 9 January 2018 (UTC)
I'm not sure, but I just started noticing this problem a couple weeks ago. I've tried reloading the page, clearing the browser's cache - still having the same problem though. It doesn't seem to happen on my iPhone (even when using Chrome Browser), but I noticed it DOES happen on my Ubuntu box (Ubuntu 16.04 64-bit) when I use the Google Chrome browser - again it works fine in Ubuntu when I use Firefox. So it may just be an issue with Google Chrome on desktop PCs? Kencussion (talk) 19:49, 9 January 2018 (UTC)
At this point, we've been able to reproduce the issue and it looks like it's a Chrome-specific issue related to caching. It's a complicated problem to troubleshoot given its nature and it may take a while to investigate. Because this seems to be a fairly controlled issue (a workaround is to use Firefox and we haven't heard tons of report about it) and we want to push a few updates to the MediaWiki software, we'd like to first focus on these updates, and only after that go back to this investigation. It may take a while, so feel free to keep us updated to let us know if the issue is affecting a lot of people or being more widespread. Thanks --Stephane Lo Presti talk 21:00, 9 January 2018 (UTC)
Keep pushing until you reach MW 1.29! -Chieftain AlexUser Chieftain Alex sig.png 22:06, 9 January 2018 (UTC)
We've got 1.27.4 in test right now and hope to get it live very soon. We're then moving to 1.30 because it will take some time to iron out the new update procedure (this could also come with an upgrade of Semantic MediaWiki to 2.5 or 3.0). That being said, given the specificity of this issue, we're not sure that software updates are going to help here --Stephane Lo Presti talk 22:34, 9 January 2018 (UTC)
That's good to hear - there are so many annoying bugs that get fixed by the time MW reaches 1.30 (e.g. currently it downloads the CSS files twice, and sometimes javascript errors prevent scripts working) -Chieftain AlexUser Chieftain Alex sig.png 23:10, 9 January 2018 (UTC)
Sorry for the lack of updates on this front. We've focused most of 2017 on the move to the different platform and knew that we'd have to skip version updates, which could unfortunately impact editors the way you describe. Once we're past the upgrade to MediaWiki to 1.30, we should go back to a more regular pace of updates --Stephane Lo Presti talk 23:25, 9 January 2018 (UTC)

(Reset indent) We deployed a fix and this seems to have fixed the issue. Let us know if you still see it, or any other related problem. Thanks! --Stephane Lo Presti talk 20:06, 15 January 2018 (UTC)

It seems to have fixed the issue for me - thanks! Kencussion (talk) 20:10, 15 January 2018 (UTC)

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

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)