WordPress.org

Make WordPress Core

Changes between Version 57 and Version 67 of Ticket #10201


Ignore:
Timestamp:
03/12/11 23:53:27 (3 years ago)
Author:
scribu
Comment:

I changed the summary, since it's obvious that multiple roles are both desired and wouldn't reduce performance.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10201

    • Property Cc jer@… ryan_b added
    • Property Summary changed from Switch roles to use single role, and no user-specific caps to Remove user-specific caps
  • Ticket #10201 – Description

    v57 v67  
    11See IRC discussions from June 18th 2009 
    2  
    3 --- 
    4  
    5 summary courtesy of DD32: 
    6  
    7 My points from what i know: 
    82 
    93 * The current role system is rather complicated, But has a lot of flexibility 
     
    159 
    1610 * That we reduce the complex system to something much more simple: 
    17    * Roles are retained, 
     11   * Roles are retained: 1 role per meta entry, and since the meta API allows for multiple values for the same key, this would have the benefit of multiple roles, and direct lookups. 
    1812   * However: 
    19      * Limit users to 1 role (This would be on a per-blog basis, based off the permission prefix thinggi..) 
    20        * This could also be done as a multi-meta system, ie. 1 role per meta entry, and since the meta API allows for multiple values for the same key, this would have the benefit of multiple roles, and direct lookups. 
    2113     * Remove the ability for a user to be part of a Role, and have an extra capability added on top of that.  
    2214 * This has the ability to significantly increase performance, As now: 
     
    2719 * An upgrade path is available which doesnt require extra tables, and reduces the ammount of serialization 
    2820   * The other option is a whole new set of tables.. which.. those who are sane (And there are some insane people in WP Dev..) realise that its not really needed.  
    29  * Fine grain control has never been possible from WP without a plugin, Nothing would change here, If a user wants fine grained control over permissions, They'd still have to run a plugin, Its just that that plugin may have to do more heavy lifting now -- since wordpress's API/role system would be simpler and not support the extra fangledangles.  
     21 * Fine grain control has never been possible from WP without a plugin, Nothing would change here, If a user wants fine grained control over permissions, They'd still have to run a plugin, Its just that that plugin may have to do more heavy lifting now -- since wordpress's API/role system would be simpler and not support the extra fangledangles.