[wp-trac] [WordPress Trac] #44176: Un-map Privacy Capabilities
WordPress Trac
noreply at wordpress.org
Sat Jul 25 19:15:16 UTC 2020
#44176: Un-map Privacy Capabilities
-------------------------------------------------+-------------------------
Reporter: desrosj | Owner: xkon
Type: defect (bug) | Status: reopened
Priority: normal | Milestone: Future
| Release
Component: Privacy | Version: 4.9.6
Severity: normal | Resolution:
Keywords: has-patch has-screenshots needs- | Focuses: multisite
dev-note has-unit-tests needs-refresh |
-------------------------------------------------+-------------------------
Changes (by carike):
* milestone: 5.6 => Future Release
Comment:
@SergeyBiryukov reverted this because of the impact on Multi-site
installations.
@desrosj punted to 5.6.
I am changing the milestone to Future Release (for now) instead, but would
really appreciate some input.
I would like to propose that we close this ticket in favour of a new
ticket, as there seems to be a reluctance to introduce new primitive caps.
What I would like us to consider, is treating this similar to the
unfiltered_uploads capability.
As per the documentation:
{{{
This capability is not available to any role by default (including Super
Admins).
The capability needs to be enabled by defining [a] constant.
With this constant defined,
all roles on a single site install can be given the unfiltered_upload
capability,
but only Super Admins can be given the capability on a Multisite install.
}}}
If we add a constant for privacy, say something like
{{{
define( 'ALLOW_DATA_PROTECTION_OFFICER', true );
}}}
is this not a possible solution for more flexibility when it comes to
export and erasure tools?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/44176#comment:65>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list