Revisioning | drupal.org

Revisioning is a module for the configuration of workflows to create, moderate and publish content revisions. You use it in scenario's like this:

• Authors write content that prior to being made publicly visible must be reviewed (and possibly edited) by moderators. Once the moderators have published the content, authors should be prevented from modifying it while %u201Clive%u201D, but they should be able to submit new revisions to their moderators.
• Both authors and moderators should be allowed to only access content relevant to their department (or region or division etc.).
• Finally, we shouldn't have to grant these roles %u201Cgod-like%u201D powers (e.g. "administer nodes" permission) to implement this.

In realising this functionality we initially looked at the Revision Moderation module, but found that the additional functionality that our customers required could not be implemented via a simple patch.

• In the RM module the permissions to 'edit' vs 'revert/publish' content are lumped together, so that it isn't possible to enforce separation of these responsibilites by role. Revisioning allows you to assign distinct permissions for authors (to only create and edit content) and moderator roles (to review, publish, revert, unpublish and optionally delete content).
• By taking advantage of the Module Grants module, Revisioning let's you set up workflows and control access to pre-published (as well as published) content, whether it's archived, current or pending review.
• Also thanks to Module Grants this module integrates better with the Workflow and Taxonomy Access Control or TAC Lite modules. This means that by adding one or both of these modules you can easily implement fine-grained access control based on workflow states ("draft", "in review", "live"), as well as content categories, like departments or regions.
• Navigation has been altered slightly so that users are invited to first select the desired revision, then the operation they'd like to perform (i.e. view, edit, publish, revert, unpublish or delete).
• Revisioning is frugal with disk space. By default, a new copy of a revision is created only when you update a current or previously published revision. When you update a pending revision (i.e. a work in progress not yet visible to the public), all edits are saved to the same copy, until it is published. You can switch this feature off though, in which case a new revision is created with every save, thus allowing authors to compare editions prior to moderation. See Content management>>Content types>>edit.
• Triggers are provided for the publish, unpublish and revert events, allowing configurable actions to be executed, such as the sending of emails to authors when their submissions are approved or declined. With Token actions installed, these emails may be tokenised. See the Revisioning at its simplest tutorial for an example.
• Revisioning does not require any additional database tables

Note: to use this module also download Module Grants. If you want the side-by-side revision comparison function, then download the Diff module as well.