Forum:JavaScript not loading in Oasis

Twenty-four hours ago this issue seemed resolved. I reported as such here. Unfortunately, it has reared its ugly head again. For some reason JavaScript contained in MediaWiki:Common.js  and/or  Wikia.js  is not loading in Oasis. They are loading completely in Monobook; there are no problems.

Today, at around 13:00UTC, it just stopped. At the very same time, I noticed that every single thread’s heading in the Community Central Forum (at least on the first listing page) went back to indicating that I had not read any of them, when I had read all of them.

When I script debug on any wiki, the error breakpoint is in a file called oasis_user_js  with the following details:" "The error description reads as follows:" "I ran the script debugger on my home wiki — where neither of these files have been altered since 16:00UTC yesterday and loaded perfectly with no breakpoints evident in the script debugger right up until around 13:00UTC today — and received the error indicated above. I then ran the script debugger here on Community Central — where MediaWiki:Common.js  (there is no  Wikia.js  at ) has not been altered since 17:41UTC yesterday and loaded perfectly with no breakpoints evident in the script debugger right up until around 13:00UTC today — and the script debugger reported the exact same error.

I have no personal JS being loaded from my userspace. My global.js  is empty. I am using Microsoft Internet Explorer 8 (version 8.0.6001.18702) with all updates installed. Here is a screen capture of the script debugger at the breakpoint, and a screen capture of the system info:



Thanks! — Spike  Toronto  14:19, June 29, 2011 (UTC)


 * Try it in another browser, I'm not getting any errors at all. It's likely just an IE compatibility issue, which are a dime a dozen.


 * You’re right about it being browser specific. We’ve already established by multiple testing of different browsers that it only seems to happen to those of us using IE. But, while its marketshare has fallen from a high of 94% in 2003, IE is still used by 60% of Internet surfers. So, the solution is never telling someone to use a different browser. (Not that you said that!) My hope is that whatever the techies did yesterday around midday UTC that got it working again, they’ll repeat the fix.

In the meantime, since the error is always with oasis_user_js, what is that file? Where is it located? When does it load? Is it upstream of MediaWiki:Common.js  and/or  Wikia.js</tt>, and the JS in one’s userspace and  global.js</tt> ? Can we edit it? Thanks! — Spike  Toronto  14:49, June 29, 2011 (UTC)


 * It's the default JS for Oasis. Among other things, it's got the jQuery library in it. It can't be edited, as it's a global file, and it's far upstream from editable files. It loads second, after . There's not much you can do about it except Special:Contact, but considering that Uberfuzzy commented on the other thread and that he's the person you're likely to get with a Special:Contact message, you might be out of luck on this one.


 * I filed a bug ticket about this. It's about middle priority on the priority scale, so I can't promise a very quick timetable, but it will be getting looking at soon for sure. --daNASCAT http://images2.wikia.nocookie.net/__cb32675/wikia/images/e/e9/WikiaStaff.png (help forum | blog) 15:09, June 30, 2011 (UTC)


 * Thanks DaNASCAT! I very much appreciate it. And, I think that Uberfuzzy was trying his best to help, I just think that perhaps I didn’t lay out the explanation of the problem very well. Thanks to all! — Spike  Toronto  07:08, July 2, 2011 (UTC)


 *  Question : Is the lower priority given this by the Wikia techies an indication that Microsoft Internet Explorer is going the way of Monobook with regard to support? Is there another browser that Wikia supports more, that it recommends over others? Should we be indicating such on our wikis’ main pages? Thanks! — Spike  Toronto  01:10, July 4, 2011 (UTC)


 * Sparing you the "IE sucks and web developers hate it" speech, a compatibility issue with one browser is likely to be low priority because fixing it so that it doesn't break other browsers can be a hassle, and it's not a widely reported issue. The techies probably have a bunch of better things to do right now, but they'll get around to it eventually.