We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 3749
    • 24,544 Posts
    Quote from: onepack at Oct 23, 2010, 03:42 AM

    Hi Bobray,

    Thanks for your reply.. but... I still don’t understand the logic... I’m really sorry.

    I see that there are some standard access policy sets like admin, resource, "load only" etc.
    You also get the option to add/create a new policy set. Lets call that one Custom.

    Why can’t the "custom" set ever give a user enough permissions to show the files so they can work with pictures in the file system?
    If I understand your explanation it doesn’t matter what I do. Even though I assign all permissions to "custom" it won’t ever show the files.
    Only the "admin" example, the standard permission set admin can do this.

    But what if the admin set gives too many rights? I can remove some rights but this will alter the standard Admin permission set.
    If an other user is allowed to have more rights I cannot create a new admin set because you just explained that will never give enough rights to see the files.

    Anyway, what I did was follow your advice and assign the admin permission set as well to the user and flushed all sessions, log in again with the standard user.

    The result was the same.. no files could be seen for the other user. The same as my previous screenprint.
    Sorry for the long story, I just try to make it clear.

    Thanks again for the help!

    Sorry if I wasn’t clear. The easy way to do thing is to "duplicate" that correct kind of policy and remove unwanted permission rather than creating a new one from scratch. Creating a new one and adding permissions risks misspelling a permission or two or forgetting to add a key permisson and spending a long time wondering why it doesn’t work.

    The end result is the same if you get everything right.


    Anyway, what I did was follow your advice and assign the admin permission set as well to the user and flushed all sessions, log in again with the standard user.

    This makes it hard to help you, because it’s not clear what you actually did. It sounds like you created an ACL entry, but what kind, with what minimum role, and what policy?

    I would say to try this:

    Delete the domain admin group.
    Delete any user settings you created for the user related to the file tree.

    Follow these steps exactly:

    Duplicate the standard Administrator policy -- call it domainAdmin.
    Create a role of DomainAdmin with a level of 5.
    Add the user to the Administrators User Group with a role of DomainAdmin.
    Create a Context Access ACL for the mgr context with a minimum role of DomainAdmin and a policy of domainAdmin.

    See what that gets you.

    The user will be an admin Super User, but we’ll change that after it gets the Files tree back.



      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
      • 22244
      • 144 Posts
      Thank you so much for your great support! I really appreciate it.
      Thanks to your guidance and the power of deduction I solved the mystery.

      First I did as you told me. I gave the dear user the power role ;-) and the file system came up. (after flush and login)
      Then I compared the two rule sets and found out that "Directory List" was missing. Very strange because I was certain I added the rule before..

      My mistake though!

      Thanks and enjoy the weekend!

      PS. I added an improvement request in Redmine to display the permissions in a list and displaying the selected and not selected rules in a clear overview instead of working with a popup.
      It’s too hard to work with a popup.
        • 3749
        • 24,544 Posts
        I’m glad you got it working. 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
          • 1289
          • 6 Posts
          Hi bob,

          I got the same problem and just follow your advise and it works.
          But my problem is, i have setup my different context per users.
          When i logon, i see all the context,. Is there anyway to hide each context per users with their different file upload folder?

          Thanks and more support for Modx Team
            • 3749
            • 24,544 Posts
            Quote from: alyainec at Nov 02, 2010, 04:37 AM

            Hi bob,

            I got the same problem and just follow your advise and it works.
            But my problem is, i have setup my different context per users.
            When i logon, i see all the context,. Is there anyway to hide each context per users with their different file upload folder?

            Thanks and more support for Modx Team

            If each context has its files in a different folder, you can set a context setting (or a user setting) called filemanager_path that will limit users to just the files and folders under that path.
              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
              • 20407
              • 82 Posts
              In case this helps someone else, it seems you also have to add the same policy to the ’web’ context (not just the mgr context) in order for the user to see all the directories in the Files list.
                • 3749
                • 24,544 Posts
                Thanks for reporting that. I would not have guessed it. In fact, you might report that as a bug at modxcms.com/bugs.

                I can’t think of any reason whey a web Context ACL should affect file visiblity in the Manager.
                  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
                  • 20407
                  • 82 Posts
                  I reported the bug, or possibly a different one, because now it just fails randomly (apparently). In fact, it failed during a session where I was showing the client how to use the Manager... maybe it fails after making changes to the directory contents? but then, what makes it work again? In my case I have only the contents of /assets/ showing.
                    • 3749
                    • 24,544 Posts
                    Check the MODx error log under Reports.

                    Is it possible that the files it doesn’t work on are in specific contexts or resource groups that the current user doesn’t have full rights to?
                      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
                      • 20407
                      • 82 Posts
                      I think it’s cookie corruption or a javascript bug reading the cookie, because clearing cookies fixed it. I’ve updated the bug report.