[wp-trac] [WordPress Trac] #44176: Un-map Privacy Capabilities
WordPress Trac
noreply at wordpress.org
Sat Jan 18 13:24:33 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 Ov3rfly):
Replying to [comment:33 xkon]:
> Editors never had these caps ...
>
> 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.
See rest of thread, e.g. "Example 1" in
[https://core.trac.wordpress.org/ticket/44176?replyto=33#comment:4 comment
4].
> 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 ..
..which would require manual changes to hundreds of sites and extensive
testing and additional cost for clients to provide the features to those
site.
In realworld "WordPress as CMS" usage, nobody in charge of public visible
content of the website is an administrator role. All these sites currently
can not use the privacy features or even the "privacy page" functions.
My request was/is: If an "auto-assign" for administrator roles is provided
in the patch, see
[https://core.trac.wordpress.org/ticket/44176?replyto=33#comment:27
comment 27], also an "auto-assign" of the caps to editor roles should be
added.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/44176#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list