Limit Privacy Policy screen to Super Admins in Multisite

[iandunn]

Similar to #43919, the new Privacy Policy page may not be appropriate for single-site admins in some Multisite use cases. For example, networks like WordCamp.org and WordPress.com will probably want to provide a single policy that covers all sites (using the privacy_policy_url filter). When that's done, the admin UI on individual sites becomes unnecessary, and may confuse admins when they see that their changes don't take effect.

We could follow r43085 and require a new capability for editing the privacy policy, which would be given to Administrators in single-site installs, but only to Super Administrators in Multisite installs. If the Super Admin wanted to delegate setting a privacy policy to individual site admins, they would need to use a plugin to modify the capabilities.

Are there any use cases of Multisite where that would cause a problem, or any better solutions?

[iandunn]

I think 43935.diff​ is ready for commit, but would like a second pair of eyes just to make sure.

[iandunn]

The patch will probably need to be refreshed if this is committed after #43873.

[iandunn]

In 43147:

Privacy: Limit Privacy Settings screen to Super Admins in Multisite.

In many common Multisite use cases, the network administrator will want to set a network-wide privacy policy -- via the privacy_policy_url filter -- for consistency and convenience. When that's done, the Privacy Settings screen on individual sites becomes unnecessary, and may confuse administrators of those sites when they see that their changes don't have any effect on the policy link in the footer.

Since we can't programatically determine which behavior the network admins would like, the safest default setting is to restrict the ability to super admins, and let them delegate it to individual site owners via a plugin, if they'd like to.

Fixes #43935.

[iandunn]

Reopening for backport to 4.9.

[ocean90]

For forward-compatibility, manage_privacy_policy doesn't sound right since the privacy policy may only one of the available privacy settings.

[iandunn]

@ocean90, what do you think about manage_privacy_options, or manage_privacy_settings?

If that sounds good, do you have time to commit that before the deadline? I've got my hands full with other tickets.

[desrosj]

Change capability to manage_privacy_options

[azaozz]

In 43153:

Privacy: Limit Privacy Settings screen to Super Admins in Multisite.

In many common Multisite use cases, the network administrator will want to set a network-wide privacy policy -- via the privacy_policy_url filter -- for consistency and convenience. When that's done, the Privacy Settings screen on individual sites becomes unnecessary, and may confuse administrators of those sites when they see that their changes don't have any effect on the policy link in the footer.

Since we can't programatically determine which behavior the network admins would like, the safest default setting is to restrict the ability to super admins, and let them delegate it to individual site owners via a plugin, if they'd like to.

Merhes [43147] to the 4.9 branch.
Fixes #43935.

[desrosj]

43935.2.diff​ goes with manage_privacy_options instead of manage_privacy_policy . I felt that this option fell more in line with other capabilities (manage_options, manage_theme_options, manage_network_options, etc.).

[azaozz]

In 43155:

Privacy: rename manage_privacy_policy to manage_privacy_options.

Props desrosj.
FIxes #43935.

[azaozz]

In 43156:

Privacy: rename manage_privacy_policy to manage_privacy_options.

Props desrosj.
Merges [43155] to the 4.9 branch.
Fixes #43935.

[desrosj]

Moving to the new Privacy component.