Guild Wars Wiki:Reporting wiki bugs

From Guild Wars Wiki

---

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 support site.
• 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. Also be aware of some common things that will cause problems on the wiki.

Contents 1 Skin defaults 2 Protection 3 Google Chrome issues 4 WikEd still won't work

[edit] Skin defaults

I'm not sure exactly where to put this, so if it should be somewhere else, feel free to move it as is appropriate. It has recently been brought to my attention that users who choose to view GWW using different skins in their preferences are having difficulties seeing some content appropriately. The global monobook.css file sets table backgrounds to default as white, while others set it as transparent. Is it possible to get the css files attached to the various optional skins changed so that they have some of the same basic defaults? I know that the Modern skin specifically has this issue. -- Wyn 05:56, 12 June 2009 (UTC)

This may be possible, but I'm not sure how much of a time sink that would be. In order to make these changes effectively, it seems like we'd have to identify problem classes for all available skins and manually update the stylesheets of each one to include the fixes. We'd also have to make sure to do this each time we do upgrades, as I believe that they overwrite default files. It's not to say that it's impossible. I'm just wondering if it would be better to just strike all MediaWiki skins (except for Monobook), since the wiki looks completely broken in all non-Monobook styles. I have very limited resources at this point, so I'd rather allocate them in other directions rather than using them to band-aid skins that are probably not (and really shouldn't be) widely used.

Do you guys think it would be an awful thing to just make Monobook the defacto skin and remove the others? I don't think that beginner users should be able to view the site in a skin we know to be broken, and advanced users who really want to change their looks can always modify their own css (which many already so). -- Emily Diehl (talk) 01:51, 16 June 2009 (UTC)

Yeah I agree with that, I don't even get why there are actually other skins available, because they are a bit too simple (well, maybe for alternative web access; lynx/mobilephone anyone?). Monobook is the default skin, monobook is what all visitors will see, so we should focus only on that. I don't care about if we remove the others or keep them for whoever wants to use them (in which case those people should be aware that the view might be different), but we shouldn't "fix" them to display pages in the same way as monobook does (because that is obviously not the intention of those skins). And especially in this case, I don't think any additional work on "fixing" those skins is necessary for that problem of you - sorry, Wyn. poke | talk 07:11, 16 June 2009 (UTC)

I have no problem with making monobook the only available skin, I just brought this up because I just recently found out that the other skins do not have the same css, and I was concerned that anyone choosing a different skin may not be getting the most out of GWW. I do understand the work that would potentially go into adjusting all the css files, and I agree. -- Wyn 07:19, 16 June 2009 (UTC)

It's a little late, but what about MediaWiki:Common.css? Surely you could put changes to affect all skins in there? — Ebany 20:55, 18 June 2009 (UTC)

Hey all! I talked to the team about this, and they agree that it's not the best plan to modify default files on a case-by-case basis. They also think that removing optional skins is the way to go, but I'm not sure of the timeframe on this. I'll check and see if we're planning on doing it for the 1.15 upgrade or not. Sorry for the late response on this! -- Emily Diehl (talk) 22:32, 22 July 2009 (UTC)

[edit] Protection

Protection still grinds the wiki to a halt. This one made the wiki inaccessible, and when it returned it was very slow. GW2W seems to be affected by GWW protections, but GW2W protections don't come with any slowdown. Quite odd. -- Brains12 \ talk 22:57, 22 August 2009 (UTC)

That's really bizarre, Brains. I will pass this along again. I talked at length with the team about the report last time, but we weren't able to figure out what could have caused the issue. Maybe this recent bit of info will help. Thanks for the report! -- Emily Diehl (talk) 21:18, 1 September 2009 (UTC)

[edit] Google Chrome issues

I'm looking at the wiki with the default template of GWW, using Google Chrome. Now the menu to the left starts after the main content pane has ended, eventhough both are alligned at a different place of the page, i'm adding a screenshot. RedShadowHuntress 15:03, 14 September 2009 (UTC)

screenshot: File:Google chrome template issues.jpg RedShadowHuntress 15:05, 14 September 2009 (UTC)

I can confirm this happens on my machine as well Prattmic 20:36, 10 October 2009 (UTC)

Unless you are using the first version of chrome this issue is long gone fixed. Its not GWW related but rather how the browser handles web objects. --Dominator Matrix 20:38, 10 October 2009 (UTC)

I am using the most recent beta of Chrome (4.0.221.6), and I still have this issue. I understand that it has to do with how Chrome handles the HTML, but a problem on one site is not something Google is likely to fix, while the owners of the wiki could. It is interesting that it seems to only affect the GWW, not other MediaWiki wikis, as GWW uses the default theme. Prattmic 22:59, 10 October 2009 (UTC)

I found the problem, and created a user script that will apply the solution each time a page loads. If anyone is interested, it can be found here: http://pastebin.com/f2031c36a Prattmic 00:13, 11 October 2009 (UTC)

You could simply write <div style="position: absolute;"> instead of using an id and applying the style later with all those different cases. poke | talk 13:52, 11 October 2009 (UTC)

Good call. I'm so used to doing things the "correct" way, but it doesn't really matter for such a quick fix. Prattmic 19:51, 11 October 2009 (UTC)

→ moved from Help:Ask a wiki question#Chrome/Chromium based sidebar error.

Using chromium, the navigation sidebar keeps getting pushed down to the level of the current page. See these screenshot http://imgur.com/9MgVD&RcavN and http://imgur.com/9MgVD&RcavNl

This error does not happen on fx. Wikipedia. :S

Panthor 15:09, 3 November 2009 (UTC)

[edit] WikEd still won't work

This wiki is the only wiki where the javascript show-preview button of WikED doesn't work. It's really annoying having to do a real show preview, that takes ages to load. RandomTime 19:56, 30 September 2009 (UTC)

"If you are using wikEd on a non-Wikipedia installation check if $wgAllowUserJs is has been set to true in the MediaWiki initialization file LocalSettings.php by an administrator". Which is at false at the moment I am sure. --Dominator Matrix 20:46, 10 October 2009 (UTC)

Yeah, because we all don't use custom javascript and GWWT is a lie :P

RT, do you get any javascript errors when trying? poke | talk 13:44, 11 October 2009 (UTC)