[wp-trac] [WordPress Trac] #44176: Un-map Privacy Capabilities

WordPress Trac noreply at wordpress.org
Mon May 21 15:00:51 UTC 2018


#44176: Un-map Privacy Capabilities
-------------------------------------+------------------------------
 Reporter:  desrosj                  |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  Privacy                  |     Version:  4.9.6
 Severity:  normal                   |  Resolution:
 Keywords:  needs-patch 2nd-opinion  |     Focuses:
-------------------------------------+------------------------------
Changes (by johnbillion):

 * keywords:  needs-patch => needs-patch 2nd-opinion


Comment:

 These are meta capabilities that map to a primitive capability in the
 `map_meta_cap()` function.

 The same problem is true for the other meta capabilities that have been
 introduced recently, for example the term management capabilities
 introduced in 4.7: https://make.wordpress.org/core/2016/10/28/fine-
 grained-capabilities-for-taxonomy-terms-in-4-7/ . There's really no way
 around this other than an update to the role management plugin to add
 support for the newly added capabilities.

 It's not really possible to add new primitive capabilities any more
 because there will always be custom user roles that don't get those caps
 and therefore can't perform an expected action.

 cc @flixos90

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44176#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list