NullEditButton adds a "Null Edit" option to page controls. A "Null Edit" is in a way similar to purging, but better. It forces the server to rebuild the page using new data.


  • All other purge methods do not apply to categorization and what links here changes from template edits, but a null edit does.
  • It's extremely useful for wikis using Semantic Mediawiki
    • The properties, filterable lists, etc generally require a null edit to get the data updated.
    • A normal ?action=purge doesn't usually work.
  • Very useful for DPL forums where a purge wouldn't work.
  • Works on Monobook

The Button


The button is added to the drop-down besides the Edit Button. In case the arrow doesn't exist like while viewing diffs, the null edit is added below Back to page link instead.


The button is added to the Monobook top bar, on the right side, along with the actions like "Edit", "History", and "Rename".

The button has an access key 0 (zero).


See also: Help:Including additional CSS and JS, Help:Advanced CSS and JS
  • For site-wide use, an administrator can add the line below to the wiki's MediaWiki:ImportJS page. Note that JavaScript must be enabled on the wiki.
  • For personal use, add the code snippet below to your global.js page (for use on all wikis) or your common.js page on your wiki (for use on a single wiki). Note that personal JS must be enabled for your account.
    type: 'script',
    articles: [
importArticles — Best Practices for installing JavaScript on FANDOM
The importArticles statement is designed to combine multiple HTTP requests into a single data transfer, allowing multiple scripts to load and execute faster. If you've been installing several different scripts, your JavaScript file has probably accumulated unnecessary import statements. Click "Expand" to learn how to efficiently batch import scripts to speed up performance and make your code look cleaner. One other approach is by using the MediaWiki:ImportJS.
If your JavaScript file has several lines of code that say importScript, importScriptPage, or importArticles, you may be able to combine them! By batch importing a collection of scripts with a single import, your JavaScript code will load faster and look cleaner. Consider the example below. On the left is an example of what your JavaScript file might currently look like. On the right is how you could improve that code.
Multiple imports — messy and slow One import — clean and efficient
  type: 'script',
  article: 'u:dev:FloatingToc/code.js'
importScriptPage('page1.js', 'wikiname');
importScriptPage('page2.js', 'wikiname');
    type: 'script',
    articles: [
Note: In this example, pay close attention to the placement of commas and other punctuation. For people who aren't familiar with programming (and even those who are!), a common mistake when writing code is to accidentally delete, forget, or misplace critical symbols like commas or quotation marks. This can cause a syntax error that breaks the code. Carefully follow the convention shown here when using importArticles.
But there's much more to importArticles than just this! For more examples and advanced usage, see the help page at Help:Including additional JavaScript and CSS.


To translate this script, you can use the translations editor.