[wp-hackers] Capabilities as a taxonomy

[Potkanski, Jason]

You need to consider that role based management will explode for Mu being in
WP 3.0. 

For what we use role based stuff for is:

Site Admins (Global Admins across all Markets, full permissions)
\/
Market Admins (Jr. Admins in a market, can create users in a market, change
blog names, etc)
\/
Group Administrators (Sports guys, editorial guys, across multiple blogs).
\/ 
Editors (Standard WP role)
\/
Bloggers/Contributors (Standard WP Role)

Please consider this hierarchy and it's complexities before nerfing any
backend APIs. We use those APIs extensively for custom purposes.

Drupal has a very robust permission/role based structure, would it be worth
it to port over?

-- 

Jason Potkanski
Application Developer, Blogs
Tribune Technology, Interactive Support
jpotkanski at tribune.com


On 1/22/10 10:23 AM, "Andrew Nacin" <wp at andrewnacin.com> wrote:

>> 
>> The ability for users to have individual capabilities was removed because
>> nobody really used it, no?
> 
> 
> Actually, that still exists.
> 
> The current system allows for a single user to have multiple roles and
> overriding individual capabilities as well. What has been proposed is
> limiting users to a single role with no opportunity for individual
> capabilities on top of that.
> 
> This could significantly increase performance in many situations, as
> currently the system can result in a lot of overhead. (For example, if you
> wanted to get a list of all users with a certain capability, and you have X
> number of users you have to calculate capabilities for...)
> 
>  We may need to introduce role management as either a feature or a
> core/canonical plugin at that point, that way roles can be cloned and
> fine-tuned.
> 
> See also: http://core.trac.wordpress.org/ticket/10201.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers