• Resolved tosca30

    (@tosca30)


    I’ve defined a ‘manager’ role, that has the sames capacities as an ‘editor’, plus the ability to create and manage users.
    This ‘manager’ shouldn’t have access to all settings, extensions, apparence menu and the like.
    And though all its pods capabilities are unchecked in the Roles & Capabilities panel, he still has access to the whole Pods Admin menu!

    Is it a bug? Or am I missing something? How can I protect the whole Pods settings from any user?

    Thanks for your answer.

    https://www.ads-software.com/plugins/pods/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Jim True

    (@jimtrue)

    @tosca30 How did you define your ‘manager’ role? Did you create it with the Members plugin or some other method.

    Exactly which capabilities did you uncheck in the Roles & Capabilities panel for the Manager role? We’ll need that to test to see if we’ve got a bug or something else is the issue.

    Thanks!
    Jim

    Thread Starter tosca30

    (@tosca30)

    I create the new role with the Roles & Capabilities panel, and I assigned it the same capabilities as the Editor (those that are displayed – see below), plus the following:

    • add_users
    • create_users
    • list_users
    • promote_users
    • remove_users

    All the pods capabilities are unchecked, but this role seem to have them nonetheless.

    Another strange thing is the Manage Roles panel says Editor has 35 capabilies, and Manager only 34! But none all of them are displayed on the Edit Role panel… I’m a bit lost here!

    Thread Starter tosca30

    (@tosca30)

    I still have another capability issue, following this thread.

    For a custom taxonomy that only administrators can modify, I’ve defined the following capabilities:

    ["manage_terms"]=>
        string(14) "manage_options"
        ["edit_terms"]=>
        string(14) "manage_options"
        ["delete_terms"]=>
        string(14) "manage_options"
        ["assign_terms"]=>
        string(10) "edit_posts"

    However:

    1. whether I put the menu location for this taxonomy in either the Settings or the Appearance menu, a line still appears in the chosen menu even when the user role has no manage_options capability. And if the user clicks on this line, he get the message

      Alors, on triche ?

      on a blank page, so he must use the navigator back key in order to go back to the admin. I’d rather he doesn’t see any menu at all.

    2. in any case, when assigning terms to a post, a user is still able to create a new terms, whatever his role, though only the administrator has the manage_options capability

    So I’m unable to protect this taxonomy against modification as the capabilites don’t seem to work at all.

    Plugin Contributor Jim True

    (@jimtrue)

    Responding back on your former question to help narrow down the difficulties. So you activated the Roles & Capabilities component of Pods. My apologies, I actually thought you were talking about the Members plugin.

    I have tested this locally with a clean install of Pods and activating the Roles & Capabilities manager. Starting with the Editor role, since that was the one you templated Manager off of, I tested to see if I had access to the Pods Admin menu. I do not, so there must be something else going on in your installation. Can you list out ALL of the capabilities you have checked for your Manager role? Does your Editor role (who by default does only have 34 capabilities) have access to the Pods Admin menu?

    The manage_categories capability is what’s letting the person add terms to your category and what is making the category menu item show up in your menus; if you turn that off, they won’t have that menu item for your Custom Taxonomy in the post type and will only be able to access it on the Add/Edit Post Type page as long as you’ve associated your Custom Taxonomy with the post type. They also will not be able to add new categories, only the ones that a user who has manage_categories would be able to access.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Pods capabilities, how does it work?’ is closed to new replies.