Forum:Common.js problem

I have an problem when I edite the common.js section on the legendary wiki:

Strangly every time I add something to it and save it; it works, however after an fell minutes it just stop working. With stop working: The collapse extension. The wiki currently use

Second question: I tried to update the version to 1.8 but I just can't figure it out how to update. —This unsigned comment is by Jens Ingels (talk • contribs) 15:59, 17 February 2012. Please sign your posts with !


 * First off, the software version is managed by Wikia, and they haven't decided to upgrade to 1.18 yet (version updates do happen, but Wikia tends to skip a few releases because they have to make sure a lot of the custom-written code on Wikia still works before upgrading. Can you provide a link to the wiki so we can have a look and see if there's a problem with the javascript code you put on it? It might help if you cleared your browser's cache and cookies, that can sometimes cause it to mess up. --  Random Time  16:04, February 17, 2012 (UTC)


 * Clean up the cache was one of the first thing I did. I don't think it's the code itself that cause the problem because I even tried some full codes on other wiki and they work but didn't work after an fell minutes like the others. For the moment the js of the metawiki is on it. Here is the link to the common.


 * I create the Legendary Wars Wiki an long time ago. I quit that project because of inactive editors. But now the monster wars wiki is created. I want to try again. Hope you can find what's wrong with it.
 * --Jens Ingels 17:34, February 17, 2012 (UTC)


 * The collapse code seems to be working fine here. Rappy 20:56, February 17, 2012 (UTC)


 * Strange, both on chrome and firefox there not working.--Jens Ingels 21:06, February 17, 2012 (UTC)


 * It works for me on Chrome/Chromium. 21:11, February 17, 2012 (UTC)

Try private browsing with Firefox or Chrome and see if it works then. If it does, it's your personal cache that's causing the issue. Rappy 21:15, February 17, 2012 (UTC)


 * Just so you know, it's 1.18 (and now 1.19), not 1.8. I got a support message that said they would update in early April. Iggyvolz 23:33, February 17, 2012 (UTC)

It's back working again. Not sure what the problem was. Thx for all answers--Jens Ingels 12:39, February 18, 2012 (UTC)