Page MenuHomePhabricator

Allow providing a (manual) list of titles to delete on [[Special:Nuke]]
Open, LowPublic


Currently, the only options are for deletion of pages matching a pattern or by the same user. Sometimes we already have a list of pages (which does not match any of the previous conditions), and we could provide it to the extension in a text field, one title per line.

Shell scripts are used by sysadmins in many wikis to do this, showing there is interest for the feature.

[1] E.g.:

Version: unspecified
Severity: enhancement



Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:16 AM
bzimport set Reference to bz66447.
bzimport added a subscriber: Unknown Object (MLST).

This is a common operation on the Wikisources: what on a Wikipedia would be "a page" is on Wikisource "this collection of pages in multiple namespaces". Thus having a list of pages, possibly into the thousands (one per page of a book, for example), is a very common scenario. Based on recent experience on enWS it is even more common than mass deleting all contribs from a particular user (most of our recent spammers have constrained themselves to a single page).

A typical case will start with a list of subpages garnered from Special:PrefixIndex. The ProofreadPage extension that powers the Wikisource workflow puts each individual page in a scanned book into Page:filename.pdf/1, Page:filename.pdf/2. And when a work (book) is exposed to readers it will often be structured as Title of Work, Title of Work/Preface, Title of Work/Chapter 1 and so forth.

In other words, what on Wikipedia would be a simple delete on a single page (the article), on Wikisource is a batch delete of a page and anything from a handful to a thousand+ pages with a common prefix.

@brion @JeroenDeDauw Isn't it about time Extension:Nuke got a little TLC? Last release was in 2017, and this phab would also fit nicely with this year's Community Wishlist focus. Just sayin'… 😎

PS. We're currently making do with a local gadget, but it's old and clunky and enWS doesn't have any local Interface Administrators so it's a pain to maintain and in practice impossible to improve.

PPS. Fixing this phab would also obviate the need for the tasks blocked on T145966. I think we can safely conclude that Extension:DeleteBatch will never be adapted to get by @Bawolff's watchful eye; but maybe there is some synergy in making Extension:DynamicPageList and Extension:Nuke talk to each other?

PPS. Fixing this phab would also obviate the need for the tasks blocked on T145966. I think we can safely conclude that Extension:DeleteBatch will never be adapted to get by @Bawolff's watchful eye; but maybe there is some synergy in making Extension:DynamicPageList and Extension:Nuke talk to each other?

Fyi, im not currently assigned to sec reviews, so its not me you have to convince anymore! But for reference, the extension very mildly failed, it could probably be reconsidered if there was sufficient desire behind it (especially if spoof user option is off). The bigger concern (which wasnt mentioned on the original review) is that is probably a lot of page deleting in one POST request.