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

[WordPress Trac]

#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              |
-------------------------------------------------+-------------------------
Changes (by xkon):

 * keywords:  2nd-opinion has-patch dev-feedback has-screenshots => 2nd-
     opinion has-patch dev-feedback has-screenshots reporter-feedback


Comment:

 Replying to [comment:32 Ov3rfly]:
 > Please make sure that the caps also get added to the editor role. We
 need a solution ..

 Editors never had these caps so I'm not sure what you are suggesting here
 and would there be an issue?

 I'm also not in favor of granting every Editor out there the Privacy
 capabilities by default especially since they didn't exist up to now.

 The purpose of doing this move is that the caps are then free to be
 assigned to any role so any website owner has the free choice to add these
 caps to their Editors if they like or create an entirely new role for DPO
 purposes.

 --

 [attachment:"44176.3.diff"] applies fine for me and we have a couple of
 extra tickets that are waiting for this change so we can re-configured the
 caps needed.

 @desrosj, @SergeyBiryukov can you add any feedback here if there is
 anything else that might be needed regarding this change on caps? I'm OK
 for a commit if this does the trick as expected, so we can work on the
 extra tickets that are waiting.

 Note, I still need to do a "wp role reset administrator" for any plugin to
 re-read the caps freely, not sure if that would work by itself in a case
 of the release update as @pbiron says at comment [comment:32] with caring
 to the $db_version (maybe this is because I'm working from /src directly
 instead of /build) :).

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