scompt

<p>Zensor doesn’t work for the current version of WordPress, probably won’t be updated anytime soon, and could cause loss of life, limb, or data.</p>
<p>Zensor enforces a two-step publishing workflow in WordPress.  The two steps are:</p>
<ol>
<li>An author submits an article (post/page) for review.</li>
<li>A moderator approves or disapproves the article.</li>
</ol>
<p>The article is only visible after the second step.  The author can add a note that the<br />
moderator can read when evaluating the article.  Similarly, the moderator can include<br />
a justification for his/her decision.</p>
<h4>Moderators</h4>
<p>Who is a moderator is determined by the <code>zensor_moderate</code> capability.  Upon installation,<br />
the Administrator is assigned this capability.  Also, a new role, Zensor Moderator is created, which<br />
only has this capability and <code>read</code>.  This is a dedicated user for moderation, eliminating<br />
potential conflicts of interest.  The Zensor Moderator cannot modify posts in any way<br />
except to accept/reject them and add a note that will be sent back to the author.  Perfect for<br />
the boss who needs to sign off on everything, but shouldn’t be allowed to add his own opinion.<br />
If you’d like other roles to be able to moderate, then you can grant them the <code>zensor_moderate</code><br />
capability using the <a href="http://www.im-web-gefunden.de/wordpress-plugins/role-manager/" rel="nofollow ugc">Role Manager</a> plugin.</p>
<h4>Notifications</h4>
<p>Every time someone does something, the other party is notified.  These notifications include:</p>
<ul>
<li>Hello author, your article was just approved/rejected.</li>
<li>Hello moderator, an article was just saved that you need to look at.</li>
</ul>
<p>Notification frequencies for both author and moderator can be independently set<br />
to either immediate, hourly, or daily.  All messages can be edited through the<br />
options interface.</p>
<h3>Future Plans</h3>
<ul>
<li>Consolidate all of the options into a single option containing an array.  It’s too messy to have so many options for the messages.</li>
<li>A feed of the pages/posts in the moderation system.  Would have to be authenticated.</li>
<li>Should posts in the moderation system be private/draft?</li>
<li>Keep a copy of the old, approved version of a page/post while the new version is in the queue.</li>
</ul>
<h3>Version History</h3>
<h4>Version 0.7</h4>
<ul>
<li>Notifications frequency is now selectable</li>
<li>Added fix to work with <a href="http://www.vtardia.com/improved-include-page/" rel="nofollow ugc">Improved Include Page</a> plugin.  Thanks, Vincent!</li>
<li>Moved localizing out of javascript file</li>
</ul>
<h4>Version 0.6</h4>
<ul>
<li>Moved development to wp-plugins.org</li>
<li>Administrator is granted <code>zensor_moderate</code> capability on activation</li>
</ul>
<h4>Version 0.5</h4>
<ul>
<li>First push to <a href="http://www.siebold-gymnasium.de" rel="nofollow ugc">Siebold Gymnasium</a> website</li>
</ul>


Zensor

Zensor enforces a two-step publishing workflow in WordPress.

Alley

Matthew Boynes

<p>WordPress has a wonderful editing model with its “draft workflow”, where writers can save unpublished drafts, preview posts, submit drafts for review from a superior, and even schedule a post’s publication. This is all that most writers and teams ever needed for a blog. WordPress has extended beyond blogs, and has grown to be the preferred platform for any person or team writing for the web. While WordPress has evolved, its editing model has not, and this editing model is limited. Once a post is published, edits cannot follow the same workflow. That’s where this plugin comes in. This plugin has two powerful features, the ability to clone posts and the ability to replace posts with another, which combined, allow writers to leverage core’s “draft workflow” for published posts.</p>
<h4>Features</h4>
<ul>
<li><em>Create clones of existing posts.</em> The replicas are created as drafts, and have all the same data (including terms and post meta) as the original post. The only things not cloned are child posts (which include revisions, attachments, and other posts)</li>
<li><em>Replace one post with another.</em> The replaced post becomes a revision of itself, the replacing post is essentially deleted, and you’re left with the replacing post’s data with the post ID and slug of the replaced post.</li>
</ul>
<p>Combined, these features give writers a pseudo-“fork and merge” model. Published posts can be cloned, the clones edited as any other draft can be, then the originals replaced with the clones.</p>
<p>Individually, these features are equally as useful. You don’t need to use the “fork and merge” model to take advantage of this plugin.</p>


Clone & Replace

Gives you the ability to clone posts, and replace posts. Together, you have a very powerful tool for a fork/merge editing model.

Zensor vs Clone & Replace