Surely there is a simple solution to this: edit_publish_posts notifies
the editor OR more dramatically - changes the status back to draft.
That way there would always have to be peer review, and it makes more
sense in that workflow. A single edited site wouldn't have any issues
with the new system.
Thoughts?
-- Greg
Owen Winkler wrote:
Here is a sample scenario using the current default permissions:
Alice does not have the publish_posts capability. Alice writes a post
and submits it to Bob, her editor, for review and publication. Bob
reviews the post, and in accordance with their editorial policy,
removes Alice's bias toward BrandX products. Bob subsequently
publishes the post.
Alice, who has been granted edit_published_posts capabilities under
the recent WP code update, can now edit that published post,
re-inserting the brand bias and possibly adding any number of bad
things that absolute editorial review would have prevented.
That is what the current workflow allows. I grant that a majority of
bloggers don't care about this workflow, since most sites are small
and self-edited. But remember that even small seemingly innocuous
changes such as this one can have greater effects than expected.
Personally, this change is great for me, since it means that larger
blog sites will need to change their caps to enable true editorial
review, and even with a Role Manager plugin in place, they're still
going to need to pay someone to figure out how their site should be
configured. So yeah, that suits me fine.
Owen
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
