|traversal||# Posted on March 8, 2013 at 5:59 pm|
I’ll have to take a look at that specific scenario, since something is definitely not quite right there for those field permissions.
In the meantime though, there might be one way out. If you head into Settings -> MasterPress, there’s a “MasterPress capabilities” panel, with two radio buttons representing capability modes:
Standard: which simply uses “manage_options” for everything, and
Specific: which allows more fine-grained control over the capability keys used to block access to various sections of the Masterplan.
If you check Specific, and check (or leave checked) the “On save, add capabilities above to roles with the manage_options capability” and update, what you should then find is that when you edit the Manager user role (via User Roles in under Masterplan) you’ll see a tab for “MasterPress” under capabilities now, which will allow you to disable access to MasterPress in a more granular way.
If you do it this way, it should hopefully solve the other problem too, but let us know if it doesn’t.
I will look into the issue when using “manage_options” as soon as I can.
It was brought to our attention that MasterPress would give a tonne of warnings and deprecation notices when used with PHP 7.4 – this update addresses those.