Eastham Sewers

Awesome find on the eastham sewers quest. That shield looks great (well, for a noob). I wonder how many other quests they updated but that didn't make it into the hub? So far we have Eastham Sewers and Sylsfear Dungeon. I checked out Swamp Temple (created a guide for it too) and didn't see any updates there.

anyway, good catch ;)

--An Adventurer 00:21, February 18, 2010 (UTC)

Django's post said they changed many key-dropping creatures that had generic names. I can't think of many beyond the quests already part of the hub and the ones we have checked, but one quest that does immediately stand out in my mind is the SoLL. I'm pretty sure the 6 first keys are dropped by generic named drudges and such. If you need a place to check, that'd be a good start. --An Adventurer 00:33, February 18, 2010 (UTC)

Yes, I've already requested it be fixed. It took several weeks to fix the revision histories for articles in the main name space so it may take a while for them to fix the File namespace also, but it should get fixed sometime in the near future. Also you may already know this, but if you want to link to an image's file page you can do so by putting a colon before File, for example [[:File:Image.jpg]].

Hi, just wanted to update you on this, it appears that all the File histories are now correct (for example if you click on the history for your example image you are correctly listed as the contributor). However the attribution in the image info table still displays the wrong user. This is a text field that is stored in the revision table in the database and so I will be submitting a new ticket to see if they can fix it. I'm not sure how straightforward it will be to apply a fix across 25,000+ images so it may take them a while. So for the time being we'll continue to have dopplegangers for old images (mine is Someguy hehe). --Tlosk  talk  contr 14:35, December 1, 2009 (UTC)

It's a quirk of the software that the order you do the edits can cause that behavior. It's also true of the image page at the bottom where it displayes links to pages where the image is used. This also happens when the image is used via a template sometimes. It's not permanent though, the updates get put into a job cue and they are updated when the server isn't busy doing something else. (The basic gist of the issue is that for it to be completely up to date for any given moment would use too many server resources so they don't). I don't know enough about their particular image cache/server architecture to make a guess about what a "reasonable" time frame for them to start showing up (and stop showing up in the unused page) is but since we don't use it to purge images as some wikis do it doesn't really matter, just more of an inconvenience. I'm getting ready to make an up to date list as well that is A-Z and that will update itself as images are added (using parser functions), I'll give you a link when I'm done. --Tlosk  talk  contr 22:54, November 19, 2009 (UTC)

Actually doing some more digging it looks like I didn't understand it as I thought I did (I looked into it a while back when I first noticed it). I'll do some more investigating and see if I can see what the problem is and how it can be fixed. --Tlosk  talk  contr 22:59, November 19, 2009 (UTC)
It seems that doing a null edit on a page where the image is used fixes it for that page (though not for other pages where it is used). A null edit is where you just open it for editing, don't change anything, and click save changes. It doesn't show up as an edit in the history but if you then go to the image's file page it will show it's used on the other page in the bottom section. The image should also be removed from the unused listing the next time it is cached (looking into it it seems it might only be once or twice a day).--Tlosk  talk  contr 23:07, November 19, 2009 (UTC)