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]

Yes Favicon[edit]

It looks like the favicon is missing when the wiki is viewed from "https://wiki.guildwars2.com/". -Chieftain AlexUser Chieftain Alex sig.png 20:12, 8 November 2017 (UTC)

Could this be a local caching issue? I can't repro the issue. Justin Lloyd (talk) 21:22, 8 November 2017 (UTC)
It seemed to fix itself shortly after the URL problem was addressed. I reckon this can be considered resolved. -Chieftain AlexUser Chieftain Alex sig.png 07:29, 9 November 2017 (UTC)

Yes ".wiki.guildwars2.com" to ".wiki-en.guildwars2.com"[edit]

Apparently making any edit whilst logged in to .wiki. redirects you to .wiki-en. afterwards. Do we have to edit the wiki from the -en address now? -Chieftain AlexUser Chieftain Alex sig.png 20:14, 8 November 2017 (UTC)

This has been fixed. Please confirm whether you're still seeing the issue. Justin Lloyd (talk) 21:22, 8 November 2017 (UTC)
Possibly related, but https://www.guildwars2.com/ is now sending me to https://wiki-de.guildwars2.com/wiki/Hauptseite . G R E E N E R 21:46, 8 November 2017 (UTC)
I am currently unable to reproduce that redirect error. Have you purged your DNS and browser caches and perhaps trying to reproduce the error with another browser? Also, did you mean wiki.guildwars2.com and not www.guildwars2.com? Justin Lloyd (talk) 22:33, 8 November 2017 (UTC)
Just got back home. Problem seems to have been fixed. The problem had been with www.guildwars2.com, not the wiki. G R E E N E R 05:03, 9 November 2017 (UTC)

Yes Logged in[edit]

I seem to being having issues not being logged in on random pages, and after I edit things I seem to get logged out again. Using Firefox currently. - Doodleplex 20:16, 8 November 2017 (UTC)

I had the same issue. I think it has to do with the url force change in the subject above. Had to log-in to the 'new' url to get things working. -Darqam 20:17, 8 November 2017 (UTC)
Hopefully this is fixed with the correction to the wiki/wiki-en redirect issue. Let us know if it persists. Justin Lloyd (talk) 21:22, 8 November 2017 (UTC)
Seems to be fixed, thanks! - Doodleplex 22:35, 8 November 2017 (UTC)

No Incomplete page loads[edit]

So I've had this 3 times now, example: http://prntscr.com/h7yg08. 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 http://prntscr.com/h7yg6f 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 (https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/416), 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)
https://http.cat/416 -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)

No HTTP to HTTPS redirect missing[edit]

A while ago, I set up a custom search within my browser to search on the GW2Wiki from the address bar via gw2w <my search term>. When I created that custom search, I set the query URL (for unknown reasons) to use http as the protocol instead of https. When I tried to edit a page some minutes ago, I was not logged in due to not using the https protocol. I don't recall ever running into this problem before the server upgrade, so I assume this appeared with the upgrade. Example link for a quick test.Nefastu 23:47, 11 November 2017 (UTC)

Our engineer identified the issue and thinks he has a fix that he may be able to deploy next week. I'll keep you posted --Stephane Lo Presti talk 00:16, 1 December 2017 (UTC)
I forgot to update this thread when we posted the fix last week. Let us know if this is still happening! --Stephane Lo Presti talk 22:13, 12 December 2017 (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)

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

No Pearl Conch recipes appear on the wrong Inscription pages[edit]

I was looking at the page for Commander's Orichalcum Imbued Inscription and I noticed that the Used-In recipe lists at the end included the Minstrel's Pearl Conch (in addition to the correct Commander's Pearl Conch). I checked the Minstrel's Orichalcum Imbued Inscription page and found that its Used-In lists included the Seraph Pearl Conch. Checking the Seraph page , I found the Sinister Conch.

Upon examining the main Pearl Conch page, I noticed that the series of pages including the wrong additional recipe follows a pattern: In the current order of the page list, starting with Sinister and going down through Seraph, each Inscription page contains both the correct recipe, and the recipe of the next item in the list. The cycle ends at Seraph and resets back up to Sinister, so the top few and bottom few Conches aren't caught in the loop. PaladinOne (talk) 00:52, 18 November 2017 (UTC)

I gave the Pearl Conch page a bit of a kick by removing those items and subobjects. Looks like they're okay atm. G R E E N E R 01:05, 18 November 2017 (UTC)
It seems the issue has returned. Same set of erroneous items. (I checked it two weeks ago, after you fixed it, and at that time it was fixed. It appears to have un-fixed itself.) PaladinOne (talk) 07:08, 4 December 2017 (UTC)
I'm not seeing these problems. I recommend clearing out your browser cache of the affected pages and check again. SarielV 20 x 20px 07:18, 4 December 2017 (UTC)
Just tried looking at Trailblazer's Orichalcum Imbued Inscription in 3 different browsers, 2 of which have never been to the GW2 wiki, and also purged the wiki page cache. Issue still present. Were you maybe looking at one of the Conches that isn't affected? PaladinOne (talk) 08:03, 4 December 2017 (UTC)
I see this too. When I paste {{#ask:[[Has ingredient::{{{1|{{#titleparts:{{BASEPAGENAME}}}}}}}]]}} onto the page it's showing Pearl Conche#recipe15 (Trialblazer) and Pearl Conche#recipe16 (Valkyrie). I've checked the properties of recipe 16 and it is correct. Perhapse someone with more SMW knowledge can look into this? J.Tesla (talk) 23:24, 4 December 2017 (UTC)

No Session hijacking login[edit]

I got the following email from Innythia:

I seem to be having logging-in issues using Overwolf Browser (in-game browser) - Error message: There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again.

I told them to bring it up here, but they never did, so I figured the issue fixed itself. However I just had the same issue trying to login to the French wiki on Firefox. I tried logging in on Google Chrome and had no issue, so it might be browser specific or it might be the whole "links changed and now we have to hunt to find the secure login page". - Doodleplex 20:44, 29 November 2017 (UTC)

Same PC right? mw:Topic:Tvx6bgsxmwktdye9 - this suggests that it's related to https and http - possibly your cookie still has http instead of https. Did you clear your cookies after your last set of connection issues with the wiki? -Chieftain AlexUser Chieftain Alex sig.png 20:52, 29 November 2017 (UTC)
If this is related to the http/https issue reported above, we may have a fix coming next week. --Stephane Lo Presti talk 00:17, 1 December 2017 (UTC)
Yeah same PC Alex, but the ironic thing is several days ago, I was able to login just fine to the French wiki, and now I can't, so it was a bit strange. Also good to hear Stephane, can't wait. =) - Doodleplex 00:22, 1 December 2017 (UTC)
Alright so now I've got this issue. If I login over an HTTPS connection, and then visit any page on the wiki using HTTP - I won't be logged in. Trying to login under HTTP when I already have an HTTPS login active throws the error. I don't think this used to happen. -Chieftain AlexUser Chieftain Alex sig.png 10:37, 4 December 2017 (UTC)
Based on what Alex said, I clicked on the link to the French wiki from the recent changes page, put "https://" in front of the link, and bam, I was logged in. So it would appear our interwiki links only go to the HTTP pages, not the HTTPS. Can this be changed somehow, or will the above mentioned fix solve this as well? - Doodleplex 17:44, 4 December 2017 (UTC)
Currently all interwikis are sending people to the http location, as per Special:Interwiki. I recall coming across info stating that interwikis can have the http or https removed from the start of the link, which will then ape the users current setting when creating the link. Can't find that documentation atm, but it's one of the adjustments I made over at the gw1 equivalent.
Let me know if there are objections, and I can get around to it later tonight or tomorrow if need be. G R E E N E R 19:01, 4 December 2017 (UTC)
A day late, sorry. I've updated all of the interwikis to refer to the user's preference for http or https, rather than force them to go to the http version (as per this information).
I should also point out that the language wikis do not strictly enforce using https (i.e. you can access via http://wiki-fr.guildwars2.com/wiki/Accueil) while sites like wikipedia cannot be (i.e. http://www.wikipedia.org/ will always send you to https://www.wikipedia.org/). Possibly something to look into? G R E E N E R 07:01, 6 December 2017 (UTC)

Did this behavior change after the https fix we pushed last week? --Stephane Lo Presti talk 22:13, 12 December 2017 (UTC)

Well you've prevented reaching the wiki over http... so yes I think this message should largely be avoided since we'll never reach the http bit.
(new bug 1) Interestingly if you take an url to a usepage, e.g. "https://wiki.guildwars2.com/wiki/User:Chieftain_Alex", and then remove the "s" from https, http://wiki.guildwars2.com/wiki/User:Chieftain_Alex the wiki redirects to the same page with a slash on the end of it - a title that doesn't exist.
(new bug 2) Similarly, if you take a title with an apostrophe in it, e.g. "Talk:Repair the fort's walls by bringing rubble to the supply officer", https://wiki.guildwars2.com/index.php?title=Talk:Repair_the_fort's_walls_by_bringing_rubble_to_the_supply_officer and remove the "s" from https, it generates a bad title error (it tries encoding the pagename bit of the url again). This appears to be the same bug which also breaks the "/wiki" search functionality from ingame. I've added a workaround but it would be good to fix it on your end instead. -Chieftain AlexUser Chieftain Alex sig.png 22:50, 12 December 2017 (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. https://github.com/arenanet/api-cdi/issues/586 -Chieftain AlexUser Chieftain Alex sig.png 20:52, 2 December 2017 (UTC)

Yes AWB connection issue[edit]

As of today I can't connect to the wiki with AWB. I got the same message from what happened last year at this time, except this time, it's not giving me a reason in the error description. =< Doesn't look like there's been anything on AWB's end, no changes recently or complaints. - Doodleplex 18:38, 6 December 2017 (UTC)

Seems to be fixed now. Not sure if it was the below or not, but all is well. - Doodleplex 23:23, 8 December 2017 (UTC)

No /wiki (command line arguments) not parsing HTML codes[edit]

Using the in-game /wiki command will launch a browser window, but HTML characters are not parsed correctly (for example, %5B%26AgE%2BTgAA%5D instead of [&AgE+TgAA] for Hall of Monuments Portal Stone), therefore, no matches are found by the search engine. --NIN37 05:44, 7 December 2017 (UTC)

I haven't been had a need to do /wiki recently but I think this may have been caused by the same patch as when ANet are trying to fix the https/http bug. -Chieftain AlexUser Chieftain Alex sig.png 07:39, 7 December 2017 (UTC)
I cannot confirm this NIN37, searching chat links still works as expected. The game properly URL-encodes the chat link to %5B%26AgE%2BTgAA%5D which is absolutely the correct behavior when sending it as a query argument to the wiki. And going to the search url with that query argument will then also work properly. poke | talk 08:03, 7 December 2017 (UTC)
There was a similar report from another user, and these correlate with my edits to the Special:Interwiki where I removed the hardcoding of http on redirects (as per this response to a different problem).
I do not know if the /wiki function uses the en:, de:, fr:, or es: codes, but if it does, that may be the source. Also, given that I haven't heard if my edits solved Doodle's problem, we could err on the side of caution and revert my interwiki edits. G R E E N E R 12:56, 7 December 2017 (UTC)
I haven't had any issues since the change, other than my above bot issue of my bot not being able to connect to the wiki now. =x - Doodleplex 17:22, 7 December 2017 (UTC)
I returned the three language interwikis back to hardcoding http in response to the /wiki function (again, I have no idea if they are related). As for the AWB issue, is there any usage of the remaining sites when working with your bot? If so, we can return those interwikis back to http as well. G R E E N E R 19:19, 7 December 2017 (UTC)
I don't know what you changed, but I just changed AWB's default settings to connect to the https variant of this wiki and it does seem to be working now. Not sure if whatever you just changed back was the problem or if it's the http problem, I don't know, I'm just happy to have my bot back. Additionally, the interwiki links still do seem to work correctly btw and go to the https variant of the other wikis, so perhaps all is well? *goes off to hug J.A.R.V.I.S.* - Doodleplex 19:32, 7 December 2017 (UTC)
"the interwiki links still do seem to work correctly btw and go to the https variant of the other wikis" That would not have been me, as I returned them to the previous http. I'm sure there are tech savvy people out there saying, "Please stop changing things," so I'm going to leave things as they are (i.e. http for the interwikis, user preference for the other links). G R E E N E R 20:05, 7 December 2017 (UTC)
moved from Talk:Ascended Salvage Tool#[&AgEUJgEA]

I'm using Chrome. I'm brought to this page (https://wiki.guildwars2.com/wiki/?search=%255B%2526AvpvSQEA%255D) and it just stays there without re-directing. It looks like this: https://cdn.discordapp.com/attachments/295628621631062016/388693549106987008/unknown.png
--175.156.243.239 14:10, 8 December 2017 (UTC)

Yep it's broken for every chatlink returned from ingame. -Chieftain AlexUser Chieftain Alex sig.png 23:21, 8 December 2017 (UTC)

Is there anything else I can do to solve the problem or do we have to wait for ANet to fix it? --175.156.243.239 03:47, 9 December 2017 (UTC)

Symbol Encoded
[  %5B
&  %26
+  %2B
=  %3D
]  %5D
The characters are already converted by the time they reach the search box from which the chatlink script operates. We could apply a patch to the script locally to replace sequences of text but I would really really like ANet to fix it properly and our patching it might hamper their debugging. -Chieftain AlexUser Chieftain Alex sig.png 13:27, 9 December 2017 (UTC)
Actually ANet can use their stage-test-wiki to debug the issue. I've applied a temporary fix. here. --Chieftain AlexUser Chieftain Alex sig.png 17:32, 9 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)