[wp-hackers] User roles - GSOC proposal

[Mike Schinkel]

Andrew:

Thanks. I assumed by your comments that those capabilities might be going away.  Very cool, glad they are not.

-Mike

On Mar 29, 2010, at 7:19 PM, Andrew Nacin wrote:

>> 
>> Really? With custom post types and CMS functionality I can see this being
>> problematic as I can easily see a user have different roles for each content
>> type.
> 
> 
> A custom post type has its own complete set of capabilities you can assign.
> From the inline documentation of register_post_type:
> 
> edit_cap - The capability that controls editing a particular object of this
> post type. Defaults to "edit_$capability_type" (edit_post).
> 
> edit_type_cap - The capability that controls editing objects of this post
> type as a class. Defaults to "edit_ . $capability_type . s" (edit_posts).
> 
> edit_others_cap - The capability that controls editing objects of this post
> type that are owned by other users. Defaults to "edit_others_ .
> $capability_type . s" (edit_others_posts).
> 
> publish_others_cap - The capability that controls publishing objects of this
> post type. Defaults to "publish_ . $capability_type . s" (publish_posts).
> 
> read_cap - The capability that controls reading a particular object of this
> post type. Defaults to "read_$capability_type" (read_post).
> 
> delete_cap - The capability that controls deleting a particular object of
> this post type. Defaults to "delete_$capability_type" (delete_post).
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers