Give user the option to delete revisions by criterion

Created on 9 June 2014, over 10 years ago

Updated 7 March 2024, 9 months ago

Give the user the ability to delete revisions using higher visibility criterion.

Currently, the system selects which nodes to delete by selecting all nodes with revisions in the tracked content types, ordering that list by nodes with the most revisions. When I've run the query on it's own, with over 8200 results, I can't really see any order at the NID level; one assumes it's by most recently updated NID, but I can't prove that.

In testing this module with a database containing 8200 nodes in a tracked type with ~2mil rows in node_revision, finding nodes that had been acted upon became pretty difficult. This offering a strategy for node deletion would give users in my situation the ability to use the "Updated" sort on the main content screen (with the last two options) to sort content appropriately and find nodes which had or had not been acted upon to make sure the module is working as designed in large scale systems.

I propose letting users select a strategy for deletion from among the following:

by most revisions
by oldest node id (count of revisions unimportant)
by newest node id (count of revisions unimportant)
by oldest node id with the most revisions
by newest node id with the most revisions
by least recently updated
by most recently updated

Setting low priority and assigning to myself to get an ID for the patch I'll be submitting a bit later.

✨ Feature request

Status

Active

Version

2.0

Component

Code

Created by

🇺🇸United States jeremyclassic

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment almost 2 years ago →
🇳🇱Netherlands seanB Netherlands
We just added a 2.x version of the module. This is a complete rewrite based on plugins to determine which revisions can be deleted. It also uses a queue worker to actually delete revisions. This means you are now able to add a custom plugin of type NodeRevisionDelete to implement any custom logic and skip deleting revisions. Could you please test if this solves the issue you currently experience?
Comment 9 months ago →
🇨🇦Canada adriancid Montreal, Canada
arriving soon to the 10 anniversary :-D, let's see if this ticket is fixed someday.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024