Extension talk:Nuke

From MediaWiki.org
Jump to: navigation, search
Start a new discussion


Thread titleRepliesLast modified
Using wildcard search109:29, 4 February 2015
Search by IP does not work?012:39, 1 September 2014
Limit020:36, 28 July 2013
version (Version 1.1.7) not working with wediawiki 1.16.5118:24, 12 April 2013
What if 'mass delete' does not show on Special:Special pages?113:19, 21 November 2012
Nuke revisions, not whole pages - how? NukeRevision?714:17, 14 November 2012
fatal error undefined getUsers()715:22, 13 October 2012
Allow nuke to delete older pages220:58, 31 August 2012
Nuke log in "recent changes"315:07, 6 July 2012
White Page119:00, 2 July 2012
Mass delete from multiple users116:06, 10 May 2012
Problem With Git HEAD and Current Snapshot version019:00, 17 April 2012

Using wildcard search

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%".

Chiefgeek157 (talk)14:02, 15 January 2015

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.., 4 February 2015

Search by IP does not work?

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?


Wikihy com (talk)12:39, 1 September 2014

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

Juandev (talk)20:36, 28 July 2013

version (Version 1.1.7) not working with wediawiki 1.16.5

deleted, 12 April 2013

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

Raako71 (talk)18:24, 12 April 2013

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

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?

Astraea (talk)05:13, 21 November 2012

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.

Jeroen De Dauw (talk)13:19, 21 November 2012

Nuke revisions, not whole pages - how? NukeRevision?

There's already a RevisionDelete [1] 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., 11 April 2012

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.

Jasper Deng (talk)03:08, 11 April 2012

"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., 11 April 2012

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

Jasper Deng (talk)05:34, 11 April 2012

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)., 11 April 2012

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

Jasper Deng (talk)15:15, 11 April 2012

fatal error undefined getUsers()

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, 8 May 2012

me too, 12 July 2012

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., 24 July 2012

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

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.

Bawolff (talk)18:22, 10 August 2012

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.

Jeroen De Dauw (talk)15:07, 17 August 2012

Allow nuke to delete older pages

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

Guiwald (talk)09:17, 14 June 2012

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.

G.Hagedorn (talk)13:17, 22 June 2012

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.

Diomidis Spinellis (talk)20:58, 31 August 2012

Nuke log in "recent changes"

Why does Nuke leave a very verbose log of what it deleted in the "recent changes" page? I've now got lots of "penis" this and "cialis" that in the recent changes page. Google doesn't like that. I don't think that people would mind if Nuke lost its ISO 9000 certification (due to lack of paper trail)..., 5 July 2012
  1. How else to present the deletion?
  2. You can temporarily assign the bot flag to someone who needs to nuke, perhaps the "flood" flag used on some Wikimedia wikis. That way it won't usually appear in recent changes.
  3. You can hide those log entries.
Jasper Deng (talk)02:37, 5 July 2012

It's not really feasible to use RevisionDelete, because it seems to only allow deleting log entries of one page at a time. However I'm using Nuke to delete several spam pages at a time. You can see my site here: http://dancecal.info/wiki/Special:RecentChanges .

I think it would be better if Nuke would be able to delete 100s of spam pages at once and put in the log "Mass deleted 100 pages by so-and-so". The details could be buried in a special "mass delete log" page. I feel that this change would be really helpful to mediawiki users..

My dance calendar website used to be on the first page of google results for "dance calendar" but now I don't even know which page it's on.. My guess is that google saw all these porn keywards and it thinks my website is a spam site or something. I could lock down my site, but I want it to be open so that people can add their own dance calendars by themselves without my intervention.

I will try your suggestion to use the "bot" permission., 6 July 2012

Hey Jasper, thanks very much, your suggestion to use the bot permission works fine. :), 6 July 2012

White Page

Ive installed Nuke and added entry into LocalSettings, its showing up as installed in SpecialPages:Version however when I try to go to Nuke I just get a white page?

Any ideas anyone?, 2 July 2012

There was a problem with 1.18+ which was rectified on 2012-06-15. You will have to download a current development snapshot. Hopefully this solves your problem.

[[kgh]] (talk)15:40, 2 July 2012

Mass delete from multiple users

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 );
Naught101 (talk)00:39, 29 February 2012

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?

Gettodachopper (talk)16:06, 10 May 2012

Problem With Git HEAD and Current Snapshot version

When attempting to use Mass Delete functionality of extension "Nuke", I get <databaseerror> page (no other message is given). This happens every time.

Version / system configuration: MediaWiki: 1.18.1 PHP: 5.3.8 PostgreSQL: 9.0.5

Nuke: 1.1 (Later tried 1.1.4, what ultimately worked was 1.1.5 (which came before 1.1.4)

So after trying to debug this for a while I started looking for past commits on the Git Source Page:


What I found was that the most recent commit (and the version you get when you download the Snapshot on the main Mediawiki page) have serious bugs.

The commit that worked best was: c56370bf33a4f5a1c5ca0b3338177234761bbb34


I suggest the HEAD be rolled back.


SasQuach (talk)19:00, 17 April 2012