Page MenuHomePhabricator

New extension to one-click revert all of a user's actions in recentchanges
Open, LowPublicFeature

Description

Author: mike.lifeguard+bugs

Description:
This is a request to expand the power of Special:Nuke significantly.

Currently, it allows one to mass-delete recent page creations of some user. I would like to expand that to revert all actions (or a subset, as determined by the user) which appear in the recentchanges table -- at a minimum, that will include:
*rollback of all edits;
*deletion of pages where no previous editor exists;
*deletion of uploads (or revert when they had uploaded a new version);
*reverting of page moves.

Note that permitting deletion of uploads is also requested in bug 8527, but this request is significantly more expansive.

This might be best left to a new extension NukeAll or something; I don't know whether the wikis which currently use Nuke would want such changes made.


Version: unspecified
Severity: enhancement

Details

Reference
bz13601

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 10:03 PM
bzimport set Reference to bz13601.
bzimport added a subscriber: Unknown Object (MLST).

That can work, or you can click on a button in the log that will revert a nuke. Such as a administrator clicking on the "rollback" like any rollbacker can do to the page, only admins will be able to do the same on nuke. Also since Nuke is now in the core of 1.14, it should be in there built in the software too.

mike.lifeguard+bugs wrote:

(In reply to comment #1)

That can work, or you can click on a button in the log that will revert a nuke.
Such as a administrator clicking on the "rollback" like any rollbacker can do
to the page, only admins will be able to do the same on nuke. Also since Nuke
is now in the core of 1.14, it should be in there built in the software too.

Erm, there's no log of "nukes" - it's not a single action, so reverting it would be rather difficult. Once the actions are performed, the software has no way to know what which actions were done as part of this, and which ones were done individually.

However this is probably best done as a new extension, not as an expansion of Nuke.

(In reply to comment #2)

(In reply to comment #1)

That can work, or you can click on a button in the log that will revert a nuke.
Such as a administrator clicking on the "rollback" like any rollbacker can do
to the page, only admins will be able to do the same on nuke. Also since Nuke
is now in the core of 1.14, it should be in there built in the software too.

Erm, there's no log of "nukes" - it's not a single action, so reverting it
would be rather difficult. Once the actions are performed, the software has no
way to know what which actions were done as part of this, and which ones were
done individually.

However this is probably best done as a new extension, not as an expansion of
Nuke.

However, nuke has been moved into the core in 1.14 alpha, so how do we make the changes there? Yes, you could make a extension for the older versions of Mediawiki from 1.13 and back, but if this happens, the new revert extension changes should be incorporated into the core of 1.14.

mike.lifeguard+bugs wrote:

(In reply to comment #3)

(In reply to comment #2)

(In reply to comment #1)

[...]

However this is probably best done as a new extension, not as an expansion of
Nuke.

However, nuke has been moved into the core in 1.14 alpha, so how do we make the
changes there? Yes, you could make a extension for the older versions of
Mediawiki from 1.13 and back, but if this happens, the new revert extension
changes should be incorporated into the core of 1.14.

No, you seriously misunderstand what this request is - it's almost totally different from your request to have an undo-nuke feature (bug 15942).

/This request/ is for one-click revert of everything a user has done which is still in the recentchanges table - ie to revert a vandal quickly and painlessly. Changing summary & blocks to reflect that.

helios89 wrote:

How is the development of this thing? I think it can be very useful with people gone mad (or maybe a bot without control), just one click to fix everything.
I think it would be nice to have another parameter YYYYMMDDHHmm, to not rollback EVERY edit, but the ones that are after the date specified in the parameter.

ml wrote:

Additionally blocking nukeAll'd user isn't in initial request message above, but that would obviously be nice. And/or add to Special:Block when available, as I just submitted an enhancement request for Nuke to be https://bugzilla.wikimedia.org/show_bug.cgi?id=32179

tim.starling wrote:

content hidden as private in Bugzilla

ml wrote:

*** Bug 42230 has been marked as a duplicate of this bug. ***

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:01 AM