We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 39446 ☆ A M B ☆
    • 51 Posts
    I have looked all over the place and spent a great deal of time only to come to the understanding that MODX's Resource Group functionality just won't do what I want to do (which I honestly believe to be a very simple thing). You cannot simply restrict a users access to only a certain resource or resources without a huge headache, and then if you succumb to the headache of setting it up, you are essentially presented with the truth that what you have done is set the end user up for a continuing future headache and taken away the dynamic capabilities of MODX.

    Before I explain the simple scenario that I wish to accomplish, let me start by saying that lot's of people have tried to explain ACL's and all come up with the conclusion that they are complex. Also I am not oblivious to the fact that user permissions and roles are a complex thing in general (I once used a Wordpress plugin to accomplish this very thing and it was a pain also), So I am not trying to single out MODX. MODX is amazing and I love it, but like any love relationship there are frustration as you grow with your love.

    Here are a few of the love doctors I have sought out for help on the topic of MODX permissions and resource groups.[/url]
    http://rtfm.modx.com/revolution/2.x/administering-your-site/security/resource-groups
    https://forums.modx.com/thread/16962/restrict-a-users-access-to-specific-page-or-pages
    http://www.bmv-interactive.com/home/modx-acl-tutorial.html
    http://designfromwithin.com/blog-webdesign-development/2012/08/28/modx-acl-customize-the-manager-using-access-controls,-user-groups-and-roles/
    and plenty more I swear smiley

    Here is the scenario:
    I am creating a website for a Tattoo Shop featuring portfolios for artists as well as basic informational pages. (I actually made the site once in Wordpress and hated it so I am remaking it in MODX.) The site can be found here tattoolicious.com

    I want to create levels of access to the manager.

    The Owners/Managers would have an administrators access to the site where they can see and do anything on the site short of mess with the "files" and "elements" tabs in the file tree.

    The Tattoo Artists/Employees should only have access to there "individual portfolio pages/resource" or at least the containing folder where all portfolios are kept on the manager.

    OK, great! Resource Groups to the rescue right? Wrong.
    When creating a resource groups, you you have to create two groups, one called "AllDocs" and another called "Portfolios", then drag every page in the site (which is tedious on larger sites may I add) into the "AllDocs" group, and then only the portfolio resources into the "Portfolios" group.

    OK, even though that was tedious were all done right? Wrong.
    What if the Owner/Manager creates a new informational page, he would then have to go into the resource groups and add the page he just made into the "AllDocs group". Every time for every page he creates he must do this to keep it from the Tattoo Artists/Employees.

    This is a problem right? This takes away MODX's ability to be a dynamic CMS and abstract all the tedious work away from the user.

    I tried using a package like DefaultResourceGroup but It still left me hanging without a solution.

    I know this has been talked about before, but is there a better way, that is user friendly and logical?

    -Jesse

    This question has been answered by jesseatomic. See the first response.

    [ed. note: jesseatomic last edited this post 12 years, 3 months ago.]
      Mahalo,
      Jesse Showalter

      My Portfolio: http://www.jesseshowalter.com
      MODX Video Tutorials: http://jesseshowalter.com/search-results.html?search=MODX&id=22
    • discuss.answer
      • 39446 ☆ A M B ☆
      • 51 Posts
      I found the answer to my issue. You can make what I described happen by using Bob Ray's DefaultResourceGroup Extra.
      https://github.com/BobRay/DefaultResourceGroup

      If anyone needs a similar solution as this, I will probably blog about it soon.
        Mahalo,
        Jesse Showalter

        My Portfolio: http://www.jesseshowalter.com
        MODX Video Tutorials: http://jesseshowalter.com/search-results.html?search=MODX&id=22
        • 21739
        • 49 Posts
        Perhaps I'm missing some details here, but doesn't the inheritance of access permissions (resource group) for a resource from it's parent container do all you need?

        I believe it should also be possible to set resource specific access permissions, using a plugin that sets a default template & default resource group depending on the user group the current user is part of, when creating a new resource.