Workbench Revision Cleanup

The Workbench Revision Cleanup module helps to clean up the revisions for a site utilizing the Workbench Moderation module. This module helps to ensure the current drafts, which are newer than the published node, are not removed during a revision cleanup. All drafts newer than the current, published node are not considered for revision deletion.

There are 2 methods to trim the revisions:

1. Bulk process: The revisions will be cleaned up using Drupal's Batch API. You can select the content type and provide the number of revisions to maintain. This is a manual process that will only trim the revisions at a particular point in time. It will not maintain the provided number of revisions in the future and they will continue to grow as usual.
2. Node update: The revisions will be cleaned when the node is updated. This is an automatic process that will occur every time a node is updated if the feature is enabled. All drafts newer than the current, published version are safe from removal. Only older revisions will be affected. In addition, this has a check in place to prevent PHP memory errors from attempting to remove too many revisions. If a node is encountered that has too many to remove via hook_update, it will notify the user that they should run the bulk process.

Instructions

1. Download and install the module as usual.
2. The Workbench Revision Cleanup makes a permission available that allows only users with the proper permission to make use of bulk revision cleanup. Users with the
   'workbench revision cleanup bulk' permission will be able to use the tool.
3. Visit "admin/content/workbench-revision-cleanup"
4. Choose your desired content types and settings and run the batch process.
5. Once the batch process has ran, you should specify an ongoing revision cleanup per content
   type via the node type edit form accessible via "admin/structure/types".

Requirements

• Workbench Moderation

Roadmap

Ideally, I'd like to integrate the ability to specify the number or date range of revisions on a per node basis.

Similar projects and how they are different

• Node Revision Delete
  Does not account for the Workbench Moderation drafts that are newer than the published version of the node.
  Only runs periodically. Does not clean up revisions during each node edit.
• Revision Deletion
  Does not account for the Workbench Moderation drafts that are newer than the published version of the node.
  Only runs periodically. Does not clean up revisions during each node edit.
• Node Revision Bulk Delete
  Does not account for the Workbench Moderation drafts that are newer than the published version of the node.
  Only runs on per-node basis. Very granular controle, but also very time consuming for large sites.
• Node Revision Cleanup
  Does not account for the Workbench Moderation drafts that are newer than the published version of the node.
  For VERY large databases with only a Drush command to remove revisions.
• Node Revision Cleanup
  Does not provide a way for bulk updates. The revisions are only cleaned when a particular node is updated.

Supporting Organization

Saint Mary's College of California