Last modified: 2011-10-21 15:44:43 UTC
It would be of great help to us commons admins if we could mass delete images.
There are a number of people who upload mass amount of copyrighted material such
as anime to commons and it is very hard to deal with it with the existing one by
one deletion tool.
The ability to delete 20 or 50 uploads of a user at a time would be most helpful.
Isn't this what you're looking for? I know it's not enabled by default on WM wikis, but I know it exists and
Would it be possible to enable it if it works. I'd like some verification that this is the tool I am looking for before putting forward a request to get it enabled.
See [[mw:Extension:Nuke]]. It is currently installed on Meta, but I'm not sure if you're a sysop there.
I am an admin in commons. This tool would be more useful in commons than on meta.
(In reply to comment #4)
> I am an admin in commons. This tool would be more useful in commons than on
I am very familiar with that fact. But you said that you had no clue what he meant by Nuke. I was giving you examples of Nuke being used because that is what you asked for in comment 2.
Nuke has been installed on Commons some time ago.
Nuke does not nuke images - it will only nuke /page creations/. Refer to bug 13601 which is a tad overambitious (requests reverting all changes by a user which are in recentchanges) but would include nuking images.
Fixed in r35793.
This appears not to be fixed. I see no images in the list of things to possibly delete for users who have recently uploaded images. Page creations are still listed, but there are no images listed in cases where there should be (if this were fixed).
That is because it is not synched yet with the Wikimedia servers: Nuke (Version r34529)
Now also adds uploads that have not been editted in r36035.
Re-opening per http://commons.wikimedia.org/w/index.php?title=User_talk:Giggy&oldid=12619430#Special:nuke -- this seems not to catch all uploads that should be caught.
Bryan - was this updated since comment 12?
Works for me in HEAD. May have been fixed in r40895