RuneScape:Administrative requests

Note: Please only make requests on this page that specifically require sysop tools to fulfill.

Long text issues
Might I suggest implementation of w:c:dev:BackToTopButton because of some of the really long walls of text some pages of this wiki poses?. Brizingr5 (talk) 22:37, September 25, 2014 (UTC)
 * It's certainly something I can look into, but I'm more interested in what you're looking for that's at the top of the page. Your userpage/talkpage? The wiki navigation? Search?
 * You might have seen the redesigned global navigation currently being tested on around Wikia on wikis such as Avatar Wiki, would something like that possibly solve the need for a back to top button?
 * As you mentioned, the wiki search bar and navigation, but also the ToC and infobox. I pretty much use the wiki instead of Swiftkit nowadays, so quickly going across a ton of (often extremely large) pages for small amounts of information can become cumbersome scrolling up so much getting back to a search bar without wasting load time on a new page to just jump to the top.  Brizingr5 (talk) 03:48, September 26, 2014 (UTC)
 * Interestingly there are plans to address almost all of these issues without a back to top button, hopefully coming in the near future. However, the infobox isn't included in those plans. I'll review the script you proposed as soon as I can and propose it's usage on the Yew Grove soon after to see how other people feel about it's installation. Thanks for the suggestion :)
 * Following a talk with staff about this, apparently it's been considered to add a button for this either in the TOC (currently this would just be the wikiamobile TOC) or as a separate button. However, it was also brought up that for desktop/laptop users, the "Home" button does this natively.

Table sorting
The parser seems to sort only descending, not ascending. -- 20:03, November 21, 2014 (UTC)
 * It's a known bug, caused by backporting something from mw1.23 without proper testing. Essentially, $.fn.tablesorter is called twice which attaches events twice and one click becomes two clicks.
 * Bummer. Just wait for a fix, I guess. -- 01:32, November 22, 2014 (UTC)
 * This bug should apparently be fixed in the new year (the next code release). In the meantime, I added a quick hack to workaround the bug a few days back.
 * I noticed the edit to site js, but tables still only sort descending for me. I can wait. I won't die. -- 23:51, December 17, 2014 (UTC)
 * I've just checked in both skins and they appear to be sorting correctly for me, e.g. [ oasis], [ monobook]. It doesn't look like the up/down arrows appear for monobook, but as I don't use the skin very often I don't know if that's normal or not. Could you link to a page where it's not working for you?
 * I tested the ones you linked. Those worked, but it was odd. Oasis worked, but Monobook didn't work until I viewed in Oasis first. Upon visiting another page and going back, Nex#Armour was broken again in Monobook. All pages I try seem to work fine in Oasis. There are no errors in my js console. I'm not sure what's going on. -- 11:17, December 18, 2014 (UTC)
 * Sent in a bug report about the missing chevrons, it looks like a wikia modification that didn't account for monobook. I'm not sure what's causing the odd results your seeing, hopefully wikia's fix will somehow fix that too.
 * @Saftzie do you know how long the chevrons have been missing? Knowing how long they've been gone for might make it easier to track down what css should be in effect.
 * They've been gone a year or so. Personally, I don't miss them. -- 16:43, December 18, 2014 (UTC)