[wp-hackers] Breaking down the Edit_Pages capability

[Chris Casciano]

On Jan 21, 2006, at 11:42 AM, Andy Skelton wrote:

> On 1/21/06, Chris Casciano <chris at placenamehere.com> wrote:
>>
>> pages. The posts capabilities are granular enough, but the Edit_pages
>> capability seems to wrap up both the ability to write new pages *and*
>> edit existing ones into the one flag.
>>
>> Is there any particular reason for this setup or is it simply an
>> oversight that comes with the first implementation of roles? Is there 
>> a
>
> One thing to consider is that we do not have "draft pages" at this
> time. The "draft" status makes it possible for Contributors to write
> posts but not publish them or edit existing pages. Without the ability
> to hold back a new page for moderation by an Editor, there is little
> reason to split the capabilities for pages as you suggest.
>
> Andy

In my particular case I don't want a copy editor to draft new pages 
either -- the draft case doesn't have anything to do with my approach 
here (although it may be another hole in the current capabilities set). 
I simply want to (as an admin) lock down the site structure to the blog 
+ 3 or 4 pages that can easily be edited, and then create a user that 
is in charge of managing the content in all those spots. Write+manage 
access for posts, but only manage access for pages.

If there are new pages to be created that would be the call and 
responsibility of someone higher up the food chain.

-- 
[ Chris Casciano ]
[ chris at placenamehere.com ] [ http://placenamehere.com ]