[wp-trac] Re: [WordPress Trac] #5255: Simplify role/capability for easier cap => user lookups

[WordPress Trac]

#5255: Simplify role/capability for easier cap => user lookups
-------------------------+--------------------------------------------------
 Reporter:  markjaquith  |        Owner:  anonymous
     Type:  task         |       Status:  new      
 Priority:  normal       |    Milestone:  2.4      
Component:  General      |      Version:           
 Severity:  normal       |   Resolution:           
 Keywords:               |  
-------------------------+--------------------------------------------------
Comment (by imwebgefunden):

 I'm the maintainer of WordPRess' Role Manager Plugin.
 The first time I came to the Role Manager I don't like the function to
 remove/set a single capability on users profile page. But in the meantime
 I used this way very often and today I like it. It's gives the
 administrator more flexibility to try single permission tests.

 In the last months of development for the Role Manager I'm missing the
 following things:

 1. The maximum length and allowed signs for roles and capabilities should
 be described. For a couple of days I released a new version 2.2.0. The new
 release set the max. length for roles and caps to 30 signs and only
 letters, digits and spaces are allowed for input. For caps all spaces are
 stored as a "_". But other plugins - such the very popular 'NextGen-
 Gallery-Plugin' don't do this translation and stores spaces as spaces. If
 you do so - you can have different capabilities one with a single space
 and one with a double space in the name, eg
 {{{
 cap 1
 }}}
 and
 {{{
 cap  1
 }}}
 Caps and Roles first should be trim'ed and then double spaces should be
 replaced by single spaces. And single spaces are stored as "_". We can go
 an other way - but what we need is a description for all plugin authors.

 2. We need a list, eg in the otions-table, with all capabilities - not
 only the assigned to one or more roles. I wrote a plugin to hide the
 dashboard. It's based on a capability "hide_dashboard". If a user has this
 capability the dashboard is hidden. Most plugins add all their
 capabilities on activation to the administrator-role. But if you have a
 "negative" capability such as "hide_dashborad" you "can't" add this to the
 administrator-role on this way. Maybe, a way can be, to only register a
 capability. In the next step the administrator can assign this capability
 to one or more roles or single user as an exra cap.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5255#comment:12>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software