Forum:GED not updating 2

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > GED not updating 2
Archive
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 20 October 2013 by Cqm.

Per RS:EXCHANGE, this forum has been created due to the Grand Exchange Database (GED) not updating as of October 8, 2013 (verified by RuneScript). Jagex have been contacted via bug report detailing the issue and Wikia have been contacted to allow all users to update exchange pages. The update scripts have been altered to allow custom price updates and the bug has been announced on {{Wiki News}}. cqm 09:17, 11 Oct 2013 (UTC) (UTC)

It would appear that User:TyBot has resumed functioning. ⁓ Hello71 14:29, October 14, 2013 (UTC)
s/functioning/editing/

10:31:12 < Hello71> ty: TyBot seems to be running off of old data, see http://runescape.wikia.com/wiki/Exchange:Bond?action=history
10:31:31 < Hello71> dunno if this is the bot's fault or api providing old data
10:53:42 <@ty> ~add_items
10:54:44 <@ty> Hello71: I'd like to think it is the api's fault, since there hasn't been any changes to the bot's code
11:10:40 < tybot> GE updates complete!

Hello71 15:55, October 14, 2013 (UTC)

Notice of intent - TyBot's list is up to date and most items appear to be updating correctly. However, the newer items don't appear to be updating and as such I'm awaiting Ty's confirmation of everything working correctly before closing this.

Given that this is the third time I've contacted Wikia mere days after requesting they unprotected the namespace to reprotect it, I question whether it is really a good idea to have it protected in this manner as opposed to using our own abusefilter. We can manage it ourselves which seems far more flexible and easier to alter when bugs like this occur.

I will remove the notice in the sitenotice and revert the js changes. I will also contact Wikia to re-protect the namespace. cqm 20:46, 15 Oct 2013 (UTC) (UTC)

AFAIK, abuse filters can only take action once the edit is submitted, not before. ⁓ Hello71 21:27, October 15, 2013 (UTC)
That doesn't mean the end result will be any different. An abuse filter to prevent edits to a namespace will accomplish the goal as protected the namespace. Furthermore, the edit button can be removed with css, so the fact that the abuse filter doesn't actually do anything until an attempt to edit is made should be considered irrelevant. Suppa chuppa Talk 21:31, October 15, 2013 (UTC)
We can also add a edit notice explaining the situation like we do for Update namespace pages (I think Exchnage pages have this already). cqm 21:41, 18 Oct 2013 (UTC) (UTC)
It looks like things will work nicely, but I'm waiting for the next GE Update to say anything definite. svco4bY.png3Gf5N2F.png 14:10, October 16, 2013 (UTC)
Things look good. I'd close this, but there seems to be some discussion about whether or not protecting the namespace is a good idea or if abuseFilter would be better. svco4bY.png3Gf5N2F.png 14:24, October 20, 2013 (UTC)
I was going to take that to another thread as there may be issues that I haven't thought of brought up that are a bit outside the scope of this. Withh that in mind, this is now closed and I'll make the other thread sometime soon. cqm 16:39, 20 Oct 2013 (UTC) (UTC)