Forum:Wikia.js page forbidden

This might have something to do with the new MediaWiki update, but how come my wikia.js page is apparently forbidden? 21:17, July 5, 2012 (UTC)
 * http://runescape.wikia.com/index.php?title=User:Bluefire2/wikia.js&amp;action=raw&amp;ctype=text/javascript
 * Is it what you wanted to have?
 * Yes, but Wikia imports http://runescape.wikia.com/wiki/User:Bluefire2/wikia.js?action=raw on pages for some reason, so nothing works! 05:59, July 6, 2012 (UTC)


 * This appears to be an issue with the MediaWiki upgrade. For instance, you can see it happening on the Pokemon wiki and Harry Potter wiki here and here, respectively. I also checked and it seems non-1.19 wikis don't have this problem. I'd report this as a bug to Special:Contact if you haven't already done so.


 * That's a problem with the fancy, unneeded and bad so-called "pretty urls" that Wikia uses, using Title?action=raw instead of index.php?title=Title&action=raw --Category:Ciencia Al Poder (talk) -WikiDex 11:37, July 7, 2012 (UTC)


 * I just linked to this thread for the third and possibly not the last time. Apparently some/several/many/all wikis have the exact same problem after the update. An official statement would be welcome! Tagging

Apart from User:Xxx/wikia.js this problem also affects MediaWiki:Monobook.css. Maybe all CSS and JS files are affected... --

Somewhere between MW 1.16 and 1.19, support was dropped for accessing the source of JS and CSS files on the wiki through the  url scheme. In 1.19, the only way you can do it is through index.php, eg. . However, Wikia have not updated Oasis to load wikia.js and wikia.css through index.php and they still load through /wiki/, which is why they return a forbidden error and as a result, don't load. This bug is also breaking the Mediawiki:Gadget pages. The bug might exist in Monobook on some wikis, but it definitely is not a sitewide issue like Oasis is. Here's a simple fix which you can put in your Mediawiki:Wikia.js until it gets patched: If you want to use it for Monobook, put it in Mediawiki:Monobook.js and replace all mentions of "wikia" with "monobook".

So long story short, Wikia have just derped. 01:04, July 13, 2012 (UTC)

No, pretty URLs are not completely broken

 * "That's a problem with the fancy, unneeded and bad so-called "pretty urls" that Wikia uses, using Title?action=raw instead of index.php?title=Title&action=raw"
 * "In 1.19, the only way you can do it is through index.php, eg. "

Not true. http://terraria.wikia.com/wiki/User:Mathmagician/wikia.js?useskin=oasis&amp;action=raw <-- working just fine for me (w:c:terraria:Special:Version).
 * Looks like they finally got around to patching it, then. 01:25, July 13, 2012 (UTC)

That's a lot of bull
It would take me all of two minutes two minutes to program a RewriteRule that "decodes" pretty URLs. Yes, I suppose doing this Wikia-wide would take quite a bit longer, but please don't assume that this a big deal. :P
 * It was a big deal because it was a breaking bug that existed sitewide. 01:31, July 13, 2012 (UTC)
 * It's a show-stopping bug and most definitely a very big deal. But you made it sound like this is some supercomplicated feature that will never come back. And that's kinda bull :P --
 * The cause behind why wikia.js/css wasn't working was somewhat complicated, but I did say that Wikia just haven't updated it and I did say that the bug is only temporary. Seems like they took the other route and made /wiki/ work again instead of just using index.php. It's nice that they took into consideration that /wiki/ not working might break things other than just wikia.js/css and Mediawiki:Gadget. (if you know what I mean) 01:40, July 13, 2012 (UTC)
 * Sorry about the harsh language yesterday! I get a bit irritable when I'm tired. And I get even more irritable when I have to waste so much time with bugs I could fix myself if only they'd let me. That's not your fault of course. So calling your statements "bull" was uncalled for. --

Resolution
The issue was actually with the URL paramater action=raw, simply we had some sort of disconnect there when we started adding that URL parameter. This was indeed fixed late last week. Please let us know if you are still having forbidden/404 errors with a JS/CSS page. --daNASCAT 14:44, July 16, 2012 (UTC)