[wp-trac] Re: [WordPress Trac] #2787: New Method of storing and calculating cap2user and user2cap

WordPress Trac wp-trac at lists.automattic.com
Wed Jun 7 13:34:40 GMT 2006


#2787: New Method of storing and calculating cap2user and user2cap
----------------------------+-----------------------------------------------
       Id:  2787            |      Status:  assigned                
Component:  Administration  |    Modified:  Wed Jun  7 13:34:40 2006
 Severity:  normal          |   Milestone:  2.1                     
 Priority:  normal          |     Version:  2.1                     
    Owner:  markjaquith     |    Reporter:  markjaquith             
----------------------------+-----------------------------------------------
Comment (by ringmaster):

 The p-code process you've describe seems reasonable, with one exception.

 If a user is denied a cap that they already have, then the extra_cap flag
 should also be set.  This will make it easier to query for caps that are
 applied only to that user, and not those coming from a role.

 This system should value user-granted caps over role-granted ones.  If a
 cap is granted or denied explicitly to a user, it should be retained if
 their roles are changed.

 The patch I was writing did not include the form for creating new caps
 (since that's mostly a developer tool, and not really useful for end-
 users), and there isn't a form for renaming caps, but I think you meant
 renaming roles.  Assuming it was upgraded to your specs (er, made to
 work), it's probably useful.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/2787>
WordPress Trac <http://wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list