Complianz not visible to ordinary site admins in Multisite network

@ecce-homo the settings are linked to the manage_privacy_options capability, which is a WordPress capability that is connected to the manage_options capability. Om multisite however it is mapped to the manage_network capability. It seems a WordPress bug that it’s not an actual capability in itself

We will add a filter soon to allow filtering of this capability. For now, you can use a user role plugin to adjust this.

hope this answers your question.

@rogierlankhorst Thanks so much for the rapid response.

I am unable to get it working with the Menu Editor Pro tool … although that plugin suggests that it should be available when I change the role access for the menu or the user, it still won’t show Complianz when I switch user on the site mentioned in my original post or a test install.local where I experimented with some other role/capability plugins.

I may be missing something really obvious …

@ecce-homo which capability did you use, manage_privacy_options, or manage_options?

@rogierlankhorst

On the Permissions screen I tried granting “Administrator” access. This doesn’t seem to make any difference except that MEP thinks the user should be able to see the menu.

Adding a multisite capability to a user by Role (like manage_network) does work, but that is obviously not a good idea (and create_sites which I reckoned might do the trick doesn’t work).

Manage Options seems to be active, as you would expect.

The MEP tool has an extra capability check, but that would surely mean that more_privacy_options and what_ever would need to be true?

@ecce-homo I think the root of the problem is the weird way in which the manage_privacy_options capability is added in WordPress core. I think because it is not a “real” capability, but a mapped one, it does not really allow for fine grained capability control.

I’ve added a filter here:

https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/add-cmplz_capability-filter

Which you can use to set your own capability which is required for the manage_privacy permission. You can use it in a mu-plugin like this:

add_filter('cmplz_capability', 'set_cmplz_capability');
function set_cmplz_capability($cap){
    $cap='custom_privacy_cap';
}

Then you can set the capability in the user roles manager.

This should resolve the issue for you in the short term. For the long term, I’ll discuss internally if we wait for WordPress to fix it, or if we add our own capability in the meantime.

Edit: I’ve just discussed this internally. We don’t see WordPress fixing this any time soon, so we’ve decided to drop the WordPress core capability, and add our own: ‘manage_privacy’. It’s included in the above branch. It will add the new capability to all administrators on upgrade, or on plugin activation.

You won’t need the user role manager anymore if only administrators need access.

• This reply was modified 2 years, 2 months ago by Rogier Lankhorst.

Thanks for dealing with this and so quickly. I’ll see if I can fix it pro tem, using the new capability. ??