We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 5568
    • 35 Posts
    Ok I have been looking and looking for an answer here until I am going in circles. I have studies your documentation page on this and there seems to be some differences.

    When I create a document, I get a several checkboxes near the bottom of the page to allow me to choose which group this document belongs to. I cannot multi-select, it is one group or another, not more than one.

    In your documentation you say a document can belong to more than one group, how?

    Also after the document is created and I choose it from the tree panel, the document is listed and displays the current settings and I can choose to Edit, Delete, etc. On this page I see 2 options:

    Web access: Private
    Manager access: Private

    However if I choose to edit the document, I only see the check boxes mentioned above, is there another setting that is supposed to show up here, Manager Access?

    What I am trying to accomplish here is this. I would like to create a page that is accessed to the Public without login, however that page can only be edited by one group, not all groups. Is this possible? Currently if I make it public on the frontend, it is accessible in the manage’s side to all groups.

    I am probably doing something wrong here, I just don’t know what. Any help would be greatly appreciated,
    Mark
      • 25663 MODX Staff
      • 12,272 Posts
      I’m unable to duplicate any restrictions on checking multiple options.
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 9191
        • 20 Posts
        You can’t check "All" at the same time as any group, but you can check as many individual groups as you want.
          • 5568
          • 35 Posts
          Quote from: evan at May 10, 2007, 10:06 AM

          You can’t check "All" at the same time as any group, but you can check as many individual groups as you want.

          Unless I check "All" the page is not public, correct?
            • 25663 MODX Staff
            • 12,272 Posts
            There are web groups and there are manager groups. Unless you restrict a document with a web group, it’s public.
              Ryan Thrash, MODX Co-Founder
              Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
              • 5568
              • 35 Posts
              Quote from: rthrash at May 10, 2007, 10:57 PM

              There are web groups and there are manager groups. Unless you restrict a document with a web group, it’s public.

              Great so I can make the page public, easy enough. Now how do I restrict the editing priviledges?
              From what I understand, I can make the page public, but I do not want all manager groups to have access to edit the page, can this be done?

              I only have one option to make this page public to the front end, but this option allows all manager groups to edit it.

              BTW, thanks for the quick responses here,
              Mark
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                You can assign a document to all the document groups you want and it won’t restrict it at all. Its restrictions depend on the user groups that are attached to the document group. If it’s attached to web user groups, then the front-end is restricted to web users belonging to those groups. Likewise, if the document group is attached to manager user groups, then back-end privileges are limited to those manager users belonging to those manager user groups. And the manager users can also be controlled by roles.

                Yes, it’s somewhat convoluted. That’s mostly because the web user management part is a later addition (actually one of the original Etomite MODx hacks, and one reason why I followed MODx when it forked, since Etomite had no front-end user management at all). The new core (0.9.7) will have a totally new user management system.
                  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
                  • 5568
                  • 35 Posts
                  Quote from: sottwell at May 11, 2007, 12:25 AM

                  You can assign a document to all the document groups you want and it won’t restrict it at all. Its restrictions depend on the user groups that are attached to the document group. If it’s attached to web user groups, then the front-end is restricted to web users belonging to those groups. Likewise, if the document group is attached to manager user groups, then back-end privileges are limited to those manager users belonging to those manager user groups. And the manager users can also be controlled by roles.

                  Yes, it’s somewhat convoluted. That’s mostly because the web user management part is a later addition (actually one of the original Etomite MODx hacks, and one reason why I followed MODx when it forked, since Etomite had no front-end user management at all). The new core (0.9.7) will have a totally new user management system.

                  BINGO!!! LIGHTS FLASHING!!! THANKS!!!!

                  I would not have ever figured that out if you had not said what you did, thanks a million, now I love this CMS!

                  1: Create Document.
                  2: Assign it to a document group.
                  3: Do not assign any web users to this document group, this makes it public in frontend.
                  4: Assign this document group to a managers group and only that managers group can edit it.

                  IT WORKS! You made me very happy at the moment, but I guess this is going to change, sad , oh well.
                  Thanks again,
                  Mark