Curtiss Grymala

<p>This plugin adds a minor bit of workflow to the WordPress interface. When anyone edits a post or a page that has already been published, a few extra options will be available in the “Publish” metabox. Any time the appropriate option is chosen, the changes will be saved as a revision to the page or post, and the previous revision (the version that was already published) will remain published.</p>
<p>The person editing the page can choose from the following four options:</p>
<ul>
<li>Publish these modifications normally – This will avoid running any of the functions in this plugin and publish the changes the way they would normally be published. This is always the default.</li>
<li>Save these changes as a revision, but don’t notify anyone – This will revert the page or post to the version that was already published, saving the modifications as a post revision. This will not send out any notification emails.</li>
<li>Save these revisions as a draft and notify reviewer – This will revert the page or post to the version that was already published, saving the modifications as a post revision. This will also send out an email message to the email address entered in the options.</li>
<li>Publish these modifications, but notify a reviewer that changes were made – This will publish the changes normally, but will still dispatch a notification message to the email address provided.</li>
</ul>
<p>If the third or fourth option is selected, a box will appear asking the user to provide an email address (or multiple addresses separated by commas) to which to send the notification message. If that box is left empty, the plugin will attempt to retrieve the value of the “dpn_reviewers” option from the individual site. If that option doesn’t exist, the “dpn_reviewers” option will be retrieved from the network (if installed in a multisite environment). You can edit those options in the Settings -> Writing and Network Admin -> Settings -> Network Settings (multisite) screens within the administrative area. If neither of those options exist, the email address of the site’s admin will be used.</p>
<h3>To Do</h3>
<ol>
<li>Include multi-network activation options</li>
<li>Implement the ability to add this functionality to custom post types</li>
</ol>
<h3>Known Issues</h3>
<ol>
<li>The interface to review and approve modifications (the default revision comparison built into WordPress) is not extremely user-friendly. Some training will most likely be necessary to teach reviewers how to identify and approve the appropriate revisions.</li>
<li>If multiple reviewers are notified of modifications, there is no easy way to let them all know when one of them reviews and approves (or potentially rejects) the changes.</li>
<li>There is no interface currently available to delete revisions, which means there is no way (other than taking no action at all) to actually reject any changes.</li>
<li>When a post is revised multiple times before the revisions are approved, the changes begin to cascade.</li>
</ol>


Post Revision Workflow

Allows anyone editing a published page or post to draft changes before those modifications go public.

Paul Ryan

<p>Limit Revision Publishing restricts edits made by users without the publish_posts capability. Their edits will be saved as an unpublished revision, and the original post will remain published. The All Posts view in the WordPress Dashboard will contain a column indicating posts with unpublished revisions. Notification emails can be sent to a subset of users whenever a new revision has been submitted so users with elevated privileges can publish them. Finally, specific roles can be marked as limited, so any users with that role will be restricted from publishing revisions on all post types.<br />
Note: this plugin only works with the Classic Editor (TinyMCE). Users of the Block Editor (Gutenberg) will be able to publish any post types granted by the capabilities in their assigned role.</p>


Limit Revision Publishing

Limit Revision Publishing restricts edits made by users without the publish_{post_type} capability.

Post Revision Workflow vs Limit Revision Publishing