GuildWiki:Bug reports

__NEWSECTIONLINK__ This page is for users to report any bugs that they may find in the wiki software. Administrators and other knowledgeable users will review the reports to determine whether the incident is an actual bug or not. Confirmed bugs will then be reported to Curse staff.

DPL Error in Forum Highlands page
'Extension DPL (warning): current configuration allows execution of DPL code from protected pages only.' Appears by the top of the Nick section. Yamagawa 02:50, 14 February 2011 (UTC)


 * Not exactly a bug, but Curse imposed a limitation that we can only use DPL if we enable the restriction that it only runs on protected pages. In order for that template to work, we would have to protect the pages of all 137 "Nick-worthy" explorable areas.  Since I had only piloted it on 8 pages, we haven't taken the time to do anything with it yet.  I'll try to come up with an alternative to DPL, but for the meantime I'll just remove it from those 8 pages.  &mdash;Dr Ishmael Diablo_the_chicken.gif 04:28, 14 February 2011 (UTC)

server performance unacceptable
Doing tasks any more complex than adding a note to a page invariably leads to minutes of waiting. I want to move a page, then adjust the redirects to it, and run into a minute long unavailability after the move. Adding categories to pages or similar activities that require database changes often have the same result. I had hoped that curse would have gotten these problems in hand after the WoWwiki move (because the same thing happened to it), but I aseem to have been mistaken. As it stands, any but the most simple editing tasks can only be undertaken by very loyal editors, because the lags will turn anyone else away. --◄mendel► 11:44, 19 February 2011 (UTC)
 * Is WoWwiki still having the same issues, or have they been fixed? Jink  13:31, 19 February 2011 (UTC)
 * Well, they're wowpedia now, and back in November I had the impression that it was fixed. Maybe they just have a better server than we do.
 * Note that the unavailability likely affects all wiki users, with possibly the exception of anons looking at cached content. --◄mendel► 16:19, 19 February 2011 (UTC)


 * WoWpedia was moved to their own dedicated servers, yes. We don't qualify for that because we don't have enough traffic.  (I think Brian said we'd get moved if we had 100k+ daily page-views or something like that; according to Quantcast, the closest we've been is a blip of 76k on Jan 3.)  &mdash;Dr Ishmael Diablo_the_chicken.gif 16:50, 19 February 2011 (UTC)


 * They seem to forget that the constant server overload turns away people. Perhaps not as much, because it's only with edits, but gwiki has been quite slow overall as well.--[[Image:El Nazgir sig.png|Talkpage]]El_Nazgir 17:08, 19 February 2011 (UTC)
 * Someone please put together a technically valid complaint and I will communicate it with Donovan. [[Image:Felix_Omni_Signature.png|link=User:Felix Omni]] 19:30, 21 February 2011 (UTC)


 * I don't know how much more technical we can make it, because there doesn't seem to be anything specific that is triggering this. It seems like any edit to any page (as well as file uploads) can cause the servers to become unresponsive for up to 5 minutes, returning either the Curse system error "Servers temporarily at capacity" or the HTTP errors "502 Bad gateway" and "504 Gateway timeout".  Sometimes, I can get through 10 edits in a row without any trouble, then the 11th edit triggers the problem; other times, it's every single edit.
 * The one thing I know for sure is that this is not due to either DPL or SMW; rather, it seems that pages that use DPL/SMW actually save faster than other pages and trigger the gateway errors less often. &mdash;Dr Ishmael Diablo_the_chicken.gif 23:08, 21 February 2011 (UTC)


 * Felix must be joking. It's not even close to my job as a user to figure out how to make a technical complaint. I often cannot view a page because it times out. And the issue is worse when attempting to edit or preview. This has been going on since we moved, got better briefly, and is getting worse again.


 * By the way, while we discuss this, most of the people I know who used to visit GWiki before GWW have stopped visiting. I was able to stem some of the hemorrhaging after Oasis, but folks have mostly said, why should I suffer attempting to connect to the other site, when I can just use the official wiki. (Obviously, my sample size is anecdotal, but it's the only sampling I have the resources to do.) — Tennessee Ernie Ford ( TEF ) 01:34, 22 February 2011 (UTC)
 * Thank you ish, I've sent an e-mail to Donovan demanding that action be taken. TEF, D: [[Image:Felix_Omni_Signature.png|link=User:Felix Omni]] 03:29, 22 February 2011 (UTC)

Getting worse? (Curse servers)
Curse servers seem to be getting worse. The time between failure seems to be about the same, but the downtime for delays seems to be growing. Also, today, when attempting to compared GWiki's IotW guide with PvX's, I had zero trouble getting to PvX, but had to wait 10-15 minutes before being able to display GWiki's.

I'm posting here not so much to gripe as to provide data points for future conversations with the Cursed Brigands. — Tennessee Ernie Ford ( TEF ) 18:20, 21 February 2011 (UTC)


 * I personally just have problems with submitting content. The rest goes slower than "normal", but I occasionally just have 5-10 minutes where I submit something, and then I can't open anything on gwiki (keeps loading, gives bad gateway errors). My submission still gets through, but it's annoying as hell when making small edits to multiple pages. (it's annoying in any case, but well...) And yeah, it's been happening a lot more than at the start of the move. --[[Image:El Nazgir sig.png|Talkpage]]El_Nazgir 18:29, 21 February 2011 (UTC)


 * Please join this discussion already in progress. &mdash;Dr Ishmael Diablo_the_chicken.gif 19:27, 21 February 2011 (UTC)
 * My issues tend to only appear when I'm going through multiple pages (either at once or one at a time immediately after the last). Primarily submitting edits - which of course causes lag errors with categories at times it seems. >.< But the wait time for things to get back to functional seems longer. When I first noticed it, a simple one-time reload fixed the issue, now, I got to wait 1-5 minutes while waiting for the error notification to load up. -- Konig / talk 04:30, 22 February 2011 (UTC)