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

[WordPress Trac]

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

Comment (by dingo_bastard):

 What is necessary to move `export_others_personal_data`,
 `erase_others_personal_data` and `manage_privacy_options` to 'primitive'
 capabilities? Just add a custom capability on line 545 in `wp-
 includes/capabilities.php` like

 {{{#!php
 case 'export_others_personal_data':
 case 'erase_others_personal_data':
 case 'manage_privacy_options':
   $caps[] = 'privacy_management';
   break;
 }}}

 or would more work need to be done? Is there something more that we need
 to modify when creating the primitive capability?

 This really is a blocker if you want to create a new user role that will
 only handle user management, as the export and erasure of private **user**
 data is something that should fall under user management.

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