FANDOM


FastDelete adds buttons to any page that can be deleted which deletes the page with a single click.


Installation

To install the script add the following to your global.js. If you have an importArticles statement already, this should be added to the articles array.

importArticles( {
    type: 'script',
    articles: [
        // ...
        'u:dev:FastDelete/code.js',
        // ...
    ]
} );

The script also requires you to configure the buttons you'd like to use. Some example of buttons you might like to use can be seen below, where label is the text that appears on the button, and summary is the reason for deletion.

window.fdButtons = [];
 
window.fdButtons.push(
    {
        summary: 'Housekeeping',
        label: 'HK'
    },
    {
        summary: 'Vandalism',
        label: 'V'
    },
    {
        summary: 'Spam',
        label: 'S'
    }
);

It is recommended to use short button labels or they will rapidly take up lots of space.

The buttons need to be defined before the script import. All together it will look something like this:

window.fdButtons = [];
 
window.fdButtons.push(
    {
        summary: 'Housekeeping',
        label: 'HK'
    },
    {
        summary: 'Vandalism',
        label: 'V'
    },
    {
        summary: 'Spam',
        label: 'S'
    }
);
 
 
importArticles( {
    type: 'script',
    articles: [
        // ...
        'u:dev:FastDelete/code.js',
        // ...
    ]
} );
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.


Wikitext in summaries

You can use some limited wikitext in the summary:

  • [[link]]
  • [[link|text]]

Other wikitext will not work:

  • [http://c.wikia.com/wiki/Link]
  • [http://c.wikia.com/wiki/Link Text]
  • {{template}}

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.