Help:Locating broken scripts

If you have problems with local gadgets or user scripts, these problems are often created by broken JavaScript code (the programming language that gadgets are written in) or undeclared dependencies on other code.

To track down the problematic code and place that needs fixing, you will have to use the developer tools of your web browser. This tool, combined with a special URL will help you to identify the broken scripts.

Test if you have script related problems
First, ensure your browser is up to date. MediaWiki features and some scripts are not supported by old browsers for safety reasons.

To test if your problem is linked to scripts, you can try to deactivate all scripts and gadgets at once.

To do so, add   to the web address (URL) of the page on which you see the problem. Example:  

If the URL already includes a  , append   instead. Example:  

If you still have problems on the page you are testing with the safe mode ad your browser is up to date, please contact a developer. If you don't have the problem anymore using the safe mode, it means you have a script issue. You have to identify the problem.

Identify the problems
The following links explain how to do this for the following browsers: [https://developer.chrome.com/devtools Chrome/Chromium], [https://developer.mozilla.org/en-US/docs/Tools/Web_Console Firefox], [http://msdn.microsoft.com/en-us/library/ie/dn255006 Internet Explorer], [<tvar|opera>http://help.opera.com/Linux/12.10/en/errorconsole.html</> Opera] and [<tvar|safari>https://developer.apple.com/library/mac/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html</> Safari].

After opening them, please append <tvar|debug> </> to the web address (URL) of the page on which you see the problem. Example: <tvar|example> </>

If the URL already includes a <tvar|?> </>, append <tvar|debug> </> instead. Example: <tvar|example> </>

For more technical information you can check toggle>ResourceLoader/Developing_with_ResourceLoader#Toggle_debug_mode</>|how to Toggle debug mode (but you do not have to read that to follow the next steps.)

If there is a problem with JavaScript, an error should be printed in the 'console' of the developer tools.

Make sure that "JavaScript" or "JS" is enabled here, and potentially disable other output so the output does not get too noisy:



Click on the file name on the right. This will open the "Debugger" view. The right pane will show the code which needs to be fixed. The left pane will show which file needs to be fixed (you might need to scroll through the list to find the one file that is highlighted). Right-click on the file, to open the file that needs fixing in a new tab:



Due to how files are "loaded", the exact URL of the file might not always be obvious. So you may have to scroll to the top of the file to see its name.

This name may just be a comment (something like <tvar|title> </>.

Problems that need fixing could be in the local <tvar|common>MediaWiki:Common.js</> file on that wiki, in your personal files such as <tvar|personal>User:MyUserName/common.js</> (or other .js files that you have under <tvar|subpages> </>), or in the code of one of the gadgets available on that wiki, or in the code dependency definitions of the gadget defined in MediaWiki:Gadgets-definition on that wiki.

Fix the problem
Problem on scripts can be due to multiple causes. We advice you to contact someone who knows JavaScript to help you.

In the meantime, you can disable the scripts.

If the broken script is identified as a gadget, disable the gadget in your preferences.

If the broken script is on a .js page or yours, disable the gadget by commenting it. Add <tvar|/*> </> at the beginning of the concerned code and <tvar|*/> </> at the end.

Others ways to identify broken scripts

 * 1) note the gadgets and scripts you are using on your account
 * 2) disable all scripts and gadgets on your account
 * 3) re-enable one gadget
 * 4) clear your cache
 * 5) test if you still have problems:
 * 6) * If not, go to step 3
 * 7) * If yes, fix the script and go back to step 3 for other potentially broken scripts