FANDOM


MassRenameRevert adds buttons and a checkbox to each entry on the move log to open revert links quickly. Due to MediaWiki limitations, it is not possible to revert them conventionally with API like a normal page move by the user, so this is the closest you can get to accomplishing that. The purpose of this script is to mass revert renaming (usually by a particular user) in cases of extreme move vandalism.

Note: The script will not auto-detect if a page exists or not in languages other than English.

Note: If this script is installed wiki-wide, it is strongly recommended to enclose the import statement in an if statement which will only let certain usergroups load the script. An example for the sysop (administrator) usergroup is shown below:

if (mw.config.get("wgUserGroups").indexOf('sysop') > -1)
  importScriptPage('MediaWiki:MassRenameRevert/code.js', 'dev');

Usage

By default, all entries are checked. To check specific ones, either press the "Uncheck All" button and select the ones you want to open or uncheck manually. Pressing the "Unchecked All" button will also cause it to change to a "Check All" button, and will revert if pressed again etc.

When the "Open Moves" button is pressed, all lines with the checkboxes checked will open the "revert" links in new separate tabs ready to revert them to their old page names.

It is possible your browser will not open them, in which case you will need to enable popups on that wiki in your browser settings.

Installation

Installation

Add this JavaScript on your wiki:

Global Personal
w:Special:Mypage/global.js Special:Mypage/common.js
importScriptPage('MediaWiki:MassRenameRevert/code.js', 'dev');
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
importScriptPage('AjaxRC/code.js','dev');
 
importScript('MediaWiki:localScript.js');
 
importArticle({
  type: 'script',
  article: 'u:dev:FloatingToc/code.js'
});
 
importScriptPage('page1.js', 'wikiname');
 
importScriptPage('page2.js', 'wikiname');
importArticles({
    type: 'script',
    articles: [
        'u:dev:AjaxRC/code.js',
        'MediaWiki:localScript.js',
        'u:dev:FloatingToc/code.js',
        'u:wikiname:page1.js',
        'u:wikiname:page2.js'
    ]
});
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.


If you're already using importArticles(), you can import the script by adding the below to the article list.

"u:dev:MassRenameRevert/code.js",

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.