Guild Wars Wiki:Reporting wiki bugs/archive 13

From Guild Wars Wiki
Jump to: navigation, search


Featured article star too low in Vector skin

Rather than being directly to the right of the page title, it strays below the line so that it overlaps with the body text (or, more commonly, with the screenshot/image that's at the top right of most articles). -- Hong 19:48, 25 June 2011 (UTC)

Can't export Guild:Its Mocha (historical)

As in subject. 93.32.128.32 07:28, 17 July 2011 (UTC)

The same with User:Dan_Mocha. 93.32.128.32 09:02, 18 July 2011 (UTC)
Just noticed that even http://wiki.guildwars.com/wiki/Guild:Its%20Mocha%20%28historical%29 doesn't work, but http://wiki.guildwars.com/wiki/Guild:Its_Mocha_%28historical%29 works. You seem to have some problems with spaces. I don't know how this can affect Special:Export. 93.32.128.32 11:04, 18 July 2011 (UTC)
That server issue is more or less known. Thank you for reporting this special case, I’ll try to get it fixed. As a workaround, you can access your export with this and this link. poke | talk 12:11, 18 July 2011 (UTC)
Thank you. It happens the same with User:BeXoR/* and User:Keirou/*, although they can be accessed normally. 93.32.128.32 14:26, 18 July 2011 (UTC)

Broken Game Updates box

Broken navbox
moved from Guild Wars Wiki talk:Community portal#Broken Game Updates box?

I'm not sure how long it will last, or if it's just me being affected, but currently, in the Feedback:Game updates navbox, where it lists the recent updates and has links to older archives, it's displayed as July, July, May instead of what I assume it's meant to be: July, June, May. I have no idea how to go about fixing it, just thought I'd mention it. ~FarloUser Farlo Triad.pngTalk 05:28, 31 July 2011 (UTC)

It seems to be the following line of code:
* [[Game updates:{{ #time: F Y {{!}} F }}]], [[Game updates:{{ #time: F Y {{!}} F | -1 months }}]], [[Game updates:{{ #time: F Y {{!}} F | -2 months }}]]
The -1 months bit should give us June from what I can tell as the -2 gives us May (and changing it to from -1 to -2 gives "July, May, May"). Not sure what the problem is as I just don't know the code well enough. --Rainith 06:01, 31 July 2011 (UTC)
That's as far as I got as well. Maybe it has something to do with it being the end of the month and July being weird and having a 31st day is confusing the code and/or something to do with using UTC like this? I have no clue what could be causing it, just trying to throw ideas at the board and see what sticks. Also, did I report this in the right area or is there a bug report place for the Wiki that I'm forgetting about? ~FarloUser Farlo Triad.pngTalk 06:14, 31 July 2011 (UTC)
On your left. | 72 User 72 Truly Random.jpg | 16:07, 31 July 2011 (UTC)
Eh? ~FarloUser Farlo Triad.pngTalk 17:02, 31 July 2011 (UTC)
72 is referring to the Report a wiki bug link in the Support section of the lefthand navigation bar. - Tanetris 17:37, 31 July 2011 (UTC)
*facepalm* ~FarloUser Farlo Triad.pngTalk 17:49, 31 July 2011 (UTC)
Doesn't appear like that any longer, so I can't comment on why it happened. If you see it again, please purge the cache first (click the UTC clock at the top). poke | talk 18:59, 1 August 2011 (UTC)
Yeah, I have no clue, but I did try clearing my cache when I saw it. I guess we'll see if it repeats in a month. ~FarloUser Farlo Triad.pngTalk 19:34, 1 August 2011 (UTC)

Bad Input collection

As this server problem is still around from time to time, and the server team is not really willing to disable the protection, but rather wants to whitelist all problems individually, I'm starting a collection of those errors now. This could lead to two possible outcomes; either we can completely whitelist all situations in which the Bad Input appears, or we collect that many cases that they accept that it's impossible to whitelist every MediaWiki operation for it.

The Bad Input error appears when you are sending a request, which gets blocked by the server. You can easily spot it, as it's basically a blank page with some text and the header “Bad Input | Problème de saisie | Problem bei der Eingabe”. If you notice such a case, please post below (in the “New reports” section with as detailed reproduction steps as possible. Please also keep the discussion in this topic to a minimum, as it's primarily there to collect the issues. Thank you. poke | talk 21:23, 4 August 2011 (UTC)

Simple links
More complex issues
Sysop-only
  • Special:AbuseFilter/new, enter substr() as the filter code, click "Check syntax". The AJAX request in the background then results in a Bad Input error.

New reports

Please post new issues in this section. poke | talk 21:23, 4 August 2011 (UTC)

http://wiki.guildwars.com/wiki/Special:AbuseFilter/examine/log/1 (and 2, and 3, and 4...). Same for the random handful I tried on GW2W. - Tanetris 19:40, 5 August 2011 (UTC)
Getting these on all of them as well. ~FarloUser Farlo Triad.pngTalk 05:36, 11 August 2011 (UTC)
These blocks should be fixed. Please let me know if you spot some more. Thanks. --Stephane Lo Presti talk 20:06, 11 August 2011 (UTC)
Entering "Shielding Urn (skill)" into the searchbox or export page will result in the Bad Input error. The substring "Urn (" is enough to trigger the error. The Shielding Urn (skill) article itself works fine. "Spirit Burn (Togo)" suffers from the same problems. Tub 14:26, 30 October 2011 (UTC)

Divs gone wild

Feedback:User/Falconeye/Avatar Unique Scythe Update Dont know if anyone can see what I see, but for the past 24+ hours, the main page has been disorganized: the navigation is two-pages worth bottem-left corner, the font sizes 50% smaller then average, and for a while i was getting duplicate entries (it has since stopped). It is -ONLY- this page and am currently stump as how to fixed it from my end. --Falconeye 02:55, 23 November 2011 (UTC)

That's not related to "Bad Input", you formatted the page incorrectly. You need to close every usage of <div> with a </div>. --Silver Edge 05:53, 23 November 2011 (UTC)
Thank you SE! ^_^ --Falconeye 06:22, 23 November 2011 (UTC)

user account creation is failing

Error is "Could not open socket" - confirmed on multiple machines and networks.

This error has been occuring since the 25th of October and is still in effect as of the 29th of November. (also reported here). --Chieftain Alex 17:35, 29 November 2012 (UTC)

(Reset indent) Hi everyone. First of all on the oversight on this bug. We think we've identified the culprit and we'll be applying a fix next week. I'll keep you updated about this as soon as I have more details. Thanks. --Stephane Lo Presti talk 20:06, 7 December 2012 (UTC)

Quick update about this issue: User:Stephane_Lo_Presti/News#Quick_maintenance_today_-_December_11.2C_2012 Thanks --Stephane Lo Presti talk 20:09, 11 December 2012 (UTC)
New spam accounts have started to be created, I'll take that as a sign that the fix worked. :P Chieftain Alex 08:56, 12 December 2012 (UTC)
Wait, spam accounts can be created despite the Captcha? --Stephane Lo Presti talk 23:02, 20 December 2012 (UTC)
About 20 spam accounts per day compared with 40 per day before installation of captcha isn't awful, but I'd love to know what other wikis use to deter the creation of spam accounts.. (fyi about 35 spam accounts created per day on gw2wiki.. perhaps to do with higher volume of users on gw2w.) Chieftain Alex 08:54, 21 December 2012 (UTC)

SVG images

SVG thumbnail images such as File:Exclamation Point - Red Emblem.svg are not processing at all. (when you click on the actual image location, i.e. here - you can see the file works.) --Chieftain Alex 17:35, 29 November 2012 (UTC)

Hi there, we solved this bug. We checked that it's working fine but let us know if you see something weird. Thanks. --Stephane Lo Presti talk 23:54, 20 December 2012 (UTC)