Extension talk:Nuke

Jump to: navigation, search

About this board

previous talk on this page

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL
Reception123 (talkcontribs)


My project was recently vandalized by someone using nuke. Is it possible to set a limitation in LocalSettings.php to limit how many pages can be nuked?

Kghbln (talkcontribs)

Oh, that's pretty bad. Limiting the number of pages that may be nuked by one user is currently not possible. It is however possible to decouple the required user right from being in the sysop user group. I have added instructions on how to do this to the extension's page.

Reception123 (talkcontribs)

Okay. Thank you very much for your help.

Reply to "Limit nuke"
Naught101 (talkcontribs)

I changed the first part of the listForm method to allow multiple users, as a comma separated values list. Works pretty well. I don't know if commas can be part of a username, if they can, I guess you'll just have to manually delete those pages, or change the "explode()" separator (the first argument):

function listForm( $usernames, $reason ) {
  global $wgUser, $wgOut, $wgLang;

  $users = explode(",", $usernames);
  $pages = array();
  foreach ($users as $user) {
    $pages += $this->getNewPages( $users );

  if( count( $pages ) == 0 ) {
    $wgOut->addWikiMsg( 'nuke-nopages', $usernames);
    return $this->promptForm();
  $wgOut->addWikiMsg( 'nuke-list', $usernames );
Gettodachopper (talkcontribs)

Hi, thanks for that, I've updated the SpecialNuke_body.php with the above but when I try it out it seems to bunch all of the usernames as one. I've tried separating with commas, semi colons, with and without spaces but with no luck. Is there anything else I need to do other than changing SpecialNuke_body.php? Is there any other way I should be entering the usernames into the mass delete box?

This comment was hidden by Kghbln (history)
Reply to "Mass delete from multiple users"

version (Version 1.1.7) not working with wediawiki 1.16.5

Raako71 (talkcontribs)


This post was posted by Raako71, but signed as

Raako71 (talkcontribs)

I have tried to install a newer version of nuke, either 1.1.7 or 1.1.6 from tags and it comes up with server error on my browser. Nuke comes up in the verson page as 1.1.7 or 1.1.6, and also appears in special pages, but dosent work from there.

I can get an old version to work, but I cant select a bunch of users easily, and there seem to be hundreds of spam users...

anyway here's the current *working* version of Special:Nuke

Reply to "version (Version 1.1.7) not working with wediawiki 1.16.5"

What if 'mass delete' does not show on Special:Special pages?

Astraeasweb (talkcontribs)

I finally had to ask for the entire wiki I was working on to be deleted and re-created. I went in and installed ConfirmEdit, and found also that Nuke was still present from the old install so I put a link to that in LocalSettings.php also; It says that after it is installed and the link put in, you should see "Mass delete" in Special Pages. I don't see it. I have reloaded the page and I am logged in. What should I do?

This post was posted by Astraeasweb, but signed as Astraea.

Jeroen De Dauw (talkcontribs)

It shows for me as "Mass delete" under "Page tools". If it does not show for you, you probably do not have the rights to use the page. Just got to Special:Nuke to confirm if this is the case.

Reply to "What if 'mass delete' does not show on Special:Special pages?"
Chiefgeek157 (talkcontribs)

Not a question so much as a note. Searching by wildcard uses the encoded title name. In particular, spaces must be replaced with underscores: "My long article name" is matched by "%long_article%". (talkcontribs)

Same problem here. I unintentionally allowed anonymous edits, and now the wiki contains hundreds of spam pages created from the same ip, but nuke claim that this ip made no changes..

Reply to "Using wildcard search"
Wikihy com (talkcontribs)

Hi, I am using MW 1.21. Some spammers created lots of spam pages (I allow anonymous user to create pages but disallow creation registering new users). I wanted to use Nuke to mass delete those pages. However, when I put in the spammer's IP (everything else is default) in Special:Nuke, I see the message saying no recent contributions were found for this IP. If I use Special:RecentChanges, I can surely see those spam pages. Am I doing something wrong?


Reply to "Search by IP does not work?"
Juandev (talkcontribs)

Is there a max line limit? I got just 141 pages deleted (some of them were nonexistent), but I wanted more.

Reply to "Limit"

Nuke revisions, not whole pages - how? NukeRevision?

8 (talkcontribs)

There's already a RevisionDelete and some scary instructions on how to make deletion permanent, i.e. like nuking, from 2008 and involving SQL manipulations that may or may not work with your mediawiki as installed and extended. There's DeletePagePermanently which seems to be functionality equivalent to nuke, on a tab. There's DeleteBatch, etc. which doesn't "really" delete pages.

Given all that, why is there no way to nuke specific revisions through the mediawiki shell tools or tabs? That's what we need to remove spam, SQL manipulations are very likely to leave things in an inconsistent state.

For wikis that are hit with bots that spam pages with legitimate edits, which cannot simply be restored with the correct timestamps after a "nuke", there's presently no solution at all. This can multiply smaller SQL DBs' size by hundreds of times and sure makes wiki farms very difficult to run.

Larger wiki farms like Wikimedia, Wikia, etc., probably have legal reasons to never truly remove anything and can pay to keep expanding disk space.

However if there's a frequent backup regime, or if you're hosting on a proper web host or in the cloud, you are paying for every gigabyte you move... we really need a NukeRevision.php shell tool and extension that lets someone tag spam in the history for permanent irrevocable removal, and purging to get the actual saved size down.

Jasper Deng (talkcontribs)

Extension:Oversight, but most pages look strange without revisions. Selective deletion (deletion of page followed by restoring only a few select "good" revisions) has been used to good effect, but it still isn't hidden from admins. (talkcontribs)

"Most pages look strange" just because some purely spam "versions" were removed with just a marker left?

The "oversight" extension seems only to "delete" or "archive" (very dangerous abusive overload of terms in shell commands) without permanently nuking it. Perhaps "nuke" isn't permanently deleting it either? After hundreds of nuked pages this DB is the same size.

Jasper Deng (talkcontribs)

Yeah, nuking does not remove them either. It just is equivalent to pressing the ordinary delete button repeatedly. (talkcontribs)

So, the insanely named script deleteArchivedVersions must be invoked? It should be called eradicateDeletedVersions or something that keeps the terms clear. And this script only gets rid of "deleted" and "nuked" stuff? No other purges or rebuild scripts required?

If so then the question is answered: DeleteRevision moves the stuff to "Archived" status, from which point it can be "deleted" (truly insane term clash here, that script must be renamed).

Jasper Deng (talkcontribs)

I can tell you that yes, "deletion" is not permanent in MediaWiki.

Bawolff (talkcontribs)

>(truly insane term clash here, that script must be renamed).

Perhaps, but that train left the sation at least 5 years ago. Very very few mediawiki things do permenant deletion.

Harry Wood (talkcontribs)

I've added a bit to Manual:deleteArchivedRevisions.php docs and linked it from this Extension:Nuke page down in the 'See also' section. For me this seemed like a good despamming combo: Use Extension:Nuke to perform a controlled (and reversible) mass deletion, and then later on use deleteArchivedRevisions to reduce the size of the database which was bloated with (deleted) spam.

Reply to "Nuke revisions, not whole pages - how? NukeRevision?" (talkcontribs)

I'am using mediawiki ver 1.16.4, I just downloaded Nuke and put it into my extensions/ folder but when I go to the special page "Special:Nuke" get the following error:

Fatal error: Call to undefined method SpecialNuke::getUser() in $IP/extensions/Nuke/Nuke_body.php on line 10 (talkcontribs)

me too (talkcontribs)

Make sure you download the localization for your version of MediaWiki from the "download a snapshot" link on the Nuke page http://www.mediawiki.org/wiki/Extension:Nuke. (talkcontribs)

Dowmloaded latest snapshot and Localization, and error is still the same. Running on a Windows implementation. Call to undefined method SpecialNuke::getUser()

Bawolff (talkcontribs)

Sounds like you have too old a version of MediaWiki. Try using either a newer version of MediaWiki (Specificly, the getUser method was introduced in MediaWiki 1.18) or using an older version of the nuke extension.

Jeroen De Dauw (talkcontribs)

Yes, that indeed is the issue - if you're using MW 1.16.x and cannot upgrade, use Nuke 1.1.1. Compatibility between Nuke releases and versions of MediaWiki can be seen in the factbox of the Nuke extension page.

2001:D30:101:1:0:0:0:5 (talkcontribs)

How can we download the old Nuke 1.1.1 ? Sorry for the newbiness, but I'm confused with the git repository.

Reply to "fatal error undefined getUsers()"
Guiwald (talkcontribs)

Hello, I would like to use Nuke to delete old pages. How can I modify it to be able to delete older pages?

G.Hagedorn (talkcontribs)

If you have access to LocalSettings, you can change the duration in which recentchanges are recorded to an arbitrary timespan. We repeatedly set it to over a year, the run the rebuildrecentchanges php script, and the desired articles were available to Nuke.

Diomidis Spinellis (talkcontribs)

Specifically in LocalSettings.php set

// Two years
$wgRCMaxAge = 2 * 365 * 24 * 60 * 60;

and run

php maintenance/rebuildrecentchanges.php

Then reset wgRCMaxAge and rerun rebuildrecentchanges.php.

To avoid having a list of thousands of deleted pages you might want to set wgRCMaxAge to 0, run maintenance/rebuildrecentchanges.php and then remove the setting. The list of recent pages will then start from empty.

Reply to "Allow nuke to delete older pages"