We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 13460
    • 47 Posts
    Hey you guys,

    I've got a case which I can't figure out how to resolve. In the resources I've got a container which holds child-documents. In the content-placeholder of this container there is a getResources-snippet which gets the data of it's children. The children are not visible in navs. Children are like sections of a page; the container.
    Now I want Editors have permissions to alter childs but NOT have the ability to make changes on the container.
    So I thought Okay make a new Resource Group with only the children (and some more) but without container. It appears children are not shown in resource-tree because parent, the container, isn't part of that Resource Group. That's a big bummer.

    How can I overcome this "problem"?!
      UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
      • 3749
      • 24,544 Posts
      You could just check the "Lock for editing" checkbox for the parent (as long as the users don't have permission to remove locks).

        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
        • 13460
        • 47 Posts
        I can't find that checkbox anymore in v2.2.5. Only Container, Searchable, Rich Text, Freeze URI, Cacheable, Empty Cache and Deleted exists in Settings-Tab of this all Resources! And yep I'm super-user ;-)
          UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
          • 3749
          • 24,544 Posts
          Yikes. Neither can I in 2.2.6. I'm not sure what this means. It hasn't been reported as a bug as far as I can tell.
            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
            • 13460
            • 47 Posts
            I can't find it with web developertools so no styling/layout-thing. It's not there.
              UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
              • 40045
              • 534 Posts
              Sounds like the Update button in the error log that was suddenly gone =)...seems that things like this happen in the MODx world somehow...
              • Locking for Admin editing has been in elements for a long time, but to be honest I've never been aware of it in resources.
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 3749
                  • 24,544 Posts
                  I could swear I've seen it, but then I'm getting pretty senile. wink
                    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
                    • 13460
                    • 47 Posts
                    Okay It's not there how do I solve my problem? Resource has to be in Resource Group otherwise children are not visible but excluding it from editing in any way by 'Content Editors' Group.
                      UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
                      • 3749
                      • 24,544 Posts
                      You need to put the container resource in another Resource Group (and remove it from the group with the editable resources).

                      Leave what you have for the Editable resources.

                      Connect the container's Resource Group to the Administrator group with a Resource Group Access ACL entry :

                      context: mgr
                      policy: Administrator
                      minimum role: Super User

                      That will hide it. To unhide it, but not allow editing, connect the container's resource Group to the Content Editors Group with another Resource Group Access ACL entry:

                      context: mgr
                      policy: Load, List, and View
                      minimum role: Content Editor

                      The container will be visible but not editable and the children should show up.
                        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