Help:Locating broken scripts
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.
Be sure you have an up-to-date configurationEdit
First, ensure your browser is up to date. MediaWiki features and some scripts are not supported by old browsers for safety reasons.
Then, purge the cache for the page to force the page to be redisplayed from its source or scripts to restart.
Those two points solve most issues.
If you have a tool like "NoScript" or ad blockers installed on your web browser, then make certain that scripts are enabled for wikipedia.org, wikimedia.org, mediawiki.org, and wikidata.org.
To test if your problem is linked to user scripts or gadgets, you can try to temporarily deactivate all on-wiki scripts and stylesheets at once.
To do so, add the safemode parameter (
?safemode=1) to the web address (URL) of the page on which you see the problem. Example:
If the URL already includes a
&safemode=1 instead. Example:
If you still have problems on the page you are testing with the safe mode, and your browser is up to date, please contact a developer of MediaWiki (How to report a bug). If you don't have the problem anymore using the safe mode, it means you have an issue with a user script or gadget. You have to identify the problem.
Some issues may be a result of interaction between Wikipedia and some browser extension. The easiest way to test it, is to try the same action with all extensions disabled, and the easiest way to achieve this, at least with the google chrome and firefox browsers, is to repeat the operation using "anonymous browsing", where the browser disables all extensions by default. If the issue disappears with anonymous browsing, try to narrow it down by temporarily disabling extensions one by one, until the "culprit" extension is found.
If you find that the problem is indeed related to a browser extension, consider reporting it to the extension developers. If you decide to report it on Wikipedia, please mention this fact in the report.
Identify the problemsEdit
The following links explain how to do this for the following browsers:
After opening them, please append
?debug=true to the web address (URL) of the page on which you see the problem. Example:
If the URL already includes a
&debug=true instead. Example:
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
Problems that need fixing could be in the local MediaWiki:Common.js file on that wiki, in your personal files such as User:MyUserName/common.js (or other .js files that you have under
User:MyUserName/), 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.
For more technical information you can check how to Toggle debug mode.
Fix the problemEdit
You will find most of the scripts by looking in m:Special:MyPage/global.js on Meta, and locally
Special:MyPage/common.js, Special:MyPage/vector.js (or similarly named pages, if you are using a different skin, such as Special:MyPage/monobook.js if you are using the MonoBook skin), and anything that is selected locally in the
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 script by commenting it out. Add
/* at the beginning of the concerned code and
*/ at the end.
You can also disable the script by blanking all of the lines about it in your .js page or by commenting out by
// at the start of each line concerned.
Other ways to identify broken scriptsEdit
- note the gadgets and scripts you are using on your account
- disable all scripts and gadgets on your account
- re-enable one gadget
- clear your cache
- test if you still have problems:
- If not, go to step 3
- If yes, fix the script and go back to step 3 for other potentially broken scripts
Totally unrelated gadgets can break the strangest things. To narrow it down turn off all the gadgets in a particular section of the gadgets list in preferences, and see if that helps. Then if that doesn't work try turning off another section of gadgets. Eventually you will find the section of gadgets where the problem lies. Then turn off the gadgets in that section one by one. Before doing any of this take a screenshot of the whole gadget preferences page. This way you can get back to what you like. Firefox has a built-in screenshot tool that lets you get the whole page including the part of the page not showing on the screen.