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

    I just started using revolution and I am a bit puzzled with the permission system. It seems very powerful and I read a couple of very nice articles about it, but still I am trying to figure out the policy set for my site editors. To be more specific:

    I would like to have a group of users (I called them arbitrarily "Content Editors") that can do anything they like with the resources, but do not have access to the elements and the rest of the site. The can add, edit, delete, move around, publish, schedule resources, clear the cache and similar things site-wide.

    In evo this was pretty straightforward. In revolution the default access policies available (Resource, Load List and view etc) end in a "Permission denied to any user that logs in to the manager).

    I managed to create a policy set by duplicating the "Administrator" and removing a lot of unwanted stuff, but I have some unwanted side effects. The worst one is that when a user clicks on a resource, the left side column (tree) is lost.

    Does anybody know what policy would allow the resource tree to be displayed all the time?

    I think that a policy set for users who can do anything they like with the resources but not the site structure (elements, configuration) would be a very useful addition to the revolution built-in access policies.

    [Edit]
    MODx Revolution 2.0.4-pl2
    Debian Lenny 2.6.26-2-amd64
    Apache 2.2.9
    Mysql 5.0.51
    PHP 5.2.6-1+lenny9 with Suhosin-Patch 0.9.6.2 (cli)
      • 18373 ☆ A M B ☆
      • 3,141 Posts
      resource_tree: To view the Resource Tree in the left nav.

      http://rtfm.modx.com/display/revolution20/Permissions+-+Administrator+Policy


      Altho it shouldn’t be showing and then disappearing no matter what is set afaik.....

      2.0.5 will have quite some improvements when it comes to the ACLs, so you might be looking forward to that release.
        Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

        Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.
        • 13785
        • 7 Posts
        Hi Mark,

        Thank you for the link, I already use the policy. It is a bit weird that the tree is disappearing when editing resources. I think I will wait for the new release, or if i get the time, try to incrementally remove permissions till i get to the one that causes the problem.