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

WordPress Trac noreply at wordpress.org
Sat Jan 18 14:32:46 UTC 2020


#44176: Un-map Privacy Capabilities
-------------------------------------------------+-------------------------
 Reporter:  desrosj                              |       Owner:  xkon
     Type:  defect (bug)                         |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.4
Component:  Privacy                              |     Version:  4.9.6
 Severity:  normal                               |  Resolution:
 Keywords:  2nd-opinion has-patch dev-feedback   |     Focuses:
  has-screenshots reporter-feedback              |
-------------------------------------------------+-------------------------

Comment (by xkon):

 Let me take a step back & make a recap of the above in full @Ov3rfly  with
 some extra additions & explanations to see if we can agree to what you're
 proposing as I think we got lost somewhere in the context (maybe I didn't
 read something correctly or I don't know..).

 ---

 Editors never had this choice so this doesn't actually bring changes to
 hundreds of sites. Instead it brings the option to do it from now on and
 bind these caps to roles as needed. That's totally different and if that's
 what you mean then personally I'm fine with it as that's the way it
 should've been since the start and we, unfortunately, missed it and that's
 why this task was created, to address this issue.

 ---

 Now regarding the "caps". Editors by default (IMHO) do not in any way need
 access to `erase_others_personal_data` & `export_others_personal_data`.
 It's not within the scope of their default role to freely download any
 other persons Personal Data Exports in any way or remove them. It's like
 saying that Editors all of a sudden have access to delete other users.

 If you meant only the `manage_privacy_options` cap then sorry if I missed
 it but it wasn't clear at least to me as "caps" was mentioned I assumed
 you meant all 3 that this ticket takes care of.

 What we could do since we are splitting these caps "on their own" is that
 we can have a new ticket if you like and propose Editors to have the
 `manage_privacy_options` cap only which is connected to the Privacy Policy
 page + the Privacy Settings admin screen ( that's why I mentioned in my
 comment that more tickets after this will be following since we have to
 re-adjust who has access and where).

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


More information about the wp-trac mailing list