We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36225
    • 20 Posts
    Hello,

    With a new fresh install of modx 2.0.8-pl traditional, I’ve got trouble in building a "1 page accessible to 1 editor only".

    I’m wondering if the system is buggy?
    For ex. In User Groups > Update User Group > Context Access and Resource Group Access for an Add or Update action, the Access Policy dropdown does not list all the existing Access Policies.
    In Context Access > Add/Update little popup window: Element and Resource and all new Access Policies I’ve created are missing.
    In Resource Group Access > Add/Update little popup window: Administrator, Content Editor and Element Access Policies are missing, but my new ones (duplicate of Resource) are there.

    Weird thing, when I update the Administrator User Group, the Context Access > Update > Access Policy : Resource is visible in the dropdown. For the other User groups, it isn’t.
    Thanks a lot for your help.
      • 3749
      • 24,544 Posts
      The resource policy is only appropriate for Resource Group Access ACL entries. The Element policy is only for Element Category Access ACL entries.

      In later versions of MODX, only the appropriate policies are shown when creating an ACL entry.
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 36225
        • 20 Posts
        Would I read your guide http://bobsguides.com/revolution-permissions.html to the end, would I seen that information... or have you added Where’s my policy? chapter just after answering my question? ;-)
        Thanks a lot for your quick answer and for your guides.

        May I ask one more question about Resource/Element policies: is it possible to allow a user "supervisor" to view a resource with all its tabs (Create/Edit document, Page settings, Templates variables) but not to edit anything? Playing around with Resource and Content Editor policies gives me the possibility for my "supervisor" to click on the resource tree and get the resource in view mode only, but the usual tabs are replaced by General, Changes and Cache Output tabs; the most annoying thing is that I don’t see the resource content and the template variables.

        PS: yes, this time, I’ve read http://bobsguides.com/controlling-access-to-resources-in-the-manager.html smiley
          • 3749
          • 24,544 Posts
          Quote from: twust at Jun 01, 2011, 11:32 AM

          Would I read your guide http://bobsguides.com/revolution-permissions.html to the end, would I seen that information... or have you added Where’s my policy? chapter just after answering my question? ;-)
          Thanks a lot for your quick answer and for your guides.

          May I ask one more question about Resource/Element policies: is it possible to allow a user "supervisor" to view a resource with all its tabs (Create/Edit document, Page settings, Templates variables) but not to edit anything? Playing around with Resource and Content Editor policies gives me the possibility for my "supervisor" to click on the resource tree and get the resource in view mode only, but the usual tabs are replaced by General, Changes and Cache Output tabs; the most annoying thing is that I don’t see the resource content and the template variables.

          PS: yes, this time, I’ve read http://bobsguides.com/controlling-access-to-resources-in-the-manager.html smiley

          I did add the "Where’s my Policy" section, but it was at least several weeks ago -- maybe you had an older version in your browser cache. wink

          I’m not sure about your other question. You might try just changing the Resource policy alone to remove the "save, create, delete, copy, and remove" permissions (this would be for the Resource Group Access ACL entry). Give them full rights to resources in the policy attached to the mgr Context Access ACL entry. That way your supervisor should see everything normally but won’t be able to change any resources.
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting
            • 36225
            • 20 Posts
            You might try just changing the Resource policy alone to remove the "save, create, delete, copy, and remove" permissions (this would be for the Resource Group Access ACL entry). Give them full rights to resources in the policy attached to the mgr Context Access ACL entry. That way your supervisor should see everything normally but won’t be able to change any resources.

            Well, I’ve tried lots of configuration and I can’t get this right: my aim is a content supervisor that can see what a normal Content Editor sees when he clicks on a page in the resource tree (a document opens, and the tabs Create/Edit Document, Page settings, Template Variables and Access permissions are visible), but in read-only mode.

            Here’s my steps.


            • create a page: view-only directly with web as parent (so there’s no question about inheritance or whatever)
            • create a user "supervisor"
            • create a resource group "view only" and put the view-only page into it
            • duplicate the Resource access policy, rename it "Resource view" and remove "save, create, delete, copy, and remove" permissions
            • duplicate the Content Editor access policy, rename it "Content supervisor" and remove the "edit_document" and "save_document" permissions
            • create a user group "supervisors", update it by adding the supervisor user with the "Member" role.

            Test 1: "Content Editor" (the original access policy) + "Resource view"

            • update the user group "supervisors" as following.
            • add the context accesses: mgr, Member-9999, Content Editor and web, Member-9999, Content Editor
            • add the resource access: mgr, Member-9999, Resource view
            • open another web browser, login as supervisor and click on the page view-only
            • result: the resource tree only displays the view-only page, but clicking on it throws the message "Error! Access denied.", nothing but this message is visible in the main area of the manager.

            Test 2: "Content Supervisor" + Resource (the original access policy)

            • update the user group "supervisors" as following.
            • add the context accesses: mgr, Member-9999, Content Supervisor and web, Member-9999, Content Supervisor
            • add the resource access: mgr, Member-9999, Resource
            • open another web browser, login as supervisor and click on the page view-only
            • result: the resource tree only displays the view-only page, but clicking on it displays only the following tabs: General, Changes and Cache output. All fields are read-only. In General tab, I see Title, Uses Template, Long Title, ..., Rich text, Container. But no Resource Content, and I don’t have any Template Variable tab.

            So, any clue?
              • 3749
              • 24,544 Posts
              I’m not sure because I’ve never tried what you’re attempting. It may or may not be possible.

              First, you should create a new role for the supervisor with a lower authority number, because you may want to use the Members group for something else later.


              I think #1 is closer to what you want, but you should try enabling edit_document and save document in the Context Access policy and control things with the Resource Group Access
                Did I help you? Buy me a beer
                Get my Book: MODX:The Official Guide
                MODX info for everyone: http://bobsguides.com/modx.html
                My MODX Extras
                Bob's Guides is now hosted at A2 MODX Hosting