We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
  • Evo had a system setting to allow all resources to be viewed in the Tree, but protected ones still couldn't be edited. I don't see anything like that in Revo, unless I just missed it.
      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
      • 13460
      • 47 Posts
      Quote from: BobRay at Feb 01, 2013, 03:31 AM
      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.

      BobRay your my lifesaver; or better said your our website-saver. Our Digital-illiterates @work can't f~%k up anymore ;-) Look but no touch......hih.
        UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
        • 3749
        • 24,544 Posts
        I'm glad it worked for you. Thanks for reporting back. smiley
          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
          • 47212
          • 40 Posts
          Is this still works on 2.4.2 ? I can't make it work, maybe I'm not good enough with access policies... But the access policies changed since this post, am I wrong ?
          I wrote a little plugin that prevent accessing containers by simply reload the manager dashboard when we try to edit a container.

          Here is the plugin code, fired on "OnManagerPageBeforeRender" event :
          <?php
          $id = $controller->scriptProperties['id'];
          $action = $controller->scriptProperties['a'];
          $modx = $controller->modx;
          $doc = $modx->getObject('modResource', $id);
          
          if ($action === 'resource/update' && $doc->get('isfolder') === true) {
              $url = MODX_MANAGER_URL;
              $modx->sendRedirect($url);
          }
          
          unset($id, $action, $modx, $doc, $url);


          But it's not really the way I need this to work, I just don't want that nothing happens when I click on a resource container in the resources tree. [ed. note: romainfallet last edited this post 8 years, 5 months ago.]
            • 3749
            • 24,544 Posts
            It should definitely work in 2.4.2, though I haven't tested it and don't have time to right now. I very much doubt that the permissions code has changed.

            Be sure to flush both permissions and sessions before testing any changes, and never test in the same browser where you're logged into the Manager (even in a separate tab).

              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
              • 47212
              • 40 Posts
              I am sorry to bother you with an already answered question, I am just lost between Resources Group, Users Group, Access policies, Access policies template, Roles, that fact that I can't edit Resources Group after its creation…

              I don't know neither why the list of Access policies is different between here and here :




              Also, by default, I only have two roles : Member and Super User. I don't have "Content Editor" role, or we don't talk about the same thing.
                • 3749
                • 24,544 Posts
                Here are a couple of things that might help.

                This is a 50 minute video of me explaining how the security permissions system works: https://vimeo.com/54360208.

                This is a whole lot of information about the details (click on MODX -> MODX Security Permissions): http://bobsguides.com/.
                  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