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

    I tried to set up modx so that one user x has permissions to edit only "his" page y (and user z his page y2 etc).

    Ideally that user should be able to edit that page with quick edit, so quick edit should show up only when user x sees his page, but not on all other pages.

    I tried and tried... but I did not find a solution for this.

    I hope someone can help me and give me detailed instructions on how to achieve this... Thanks!
      • 1764
      • 680 Posts
      Right now, when a user is logged in they see the QuickEdit toolbar, even if they don’t have permission to edit that page. This is done so that they have access to the Manager and Logout links.

      In the future I hope to create a configuration page for QuickEdit where you could set these sort of options.
        • 1448
        • 15 Posts
        Thanks - I understand that, but my test user seems also to be able to edit all pages, although I tried to configure the user so that he only has access to one page for editing.

        Can someone please tell me briefly how to achieve that (I don’t seem to get the permission system...)?

        Also is there a possibility to only display the quick edit button to modify the content of the page, but NOT the menu that gives access to the manager, hide links, logout etc.?

        Thanks!
          • 32241
          • 1,495 Posts
          I’m not sure whether there is an easy way to do this, but you can achieve this with user groups and document groups.

          Setup a new user groups and document group. Assign the user group to the document group. And set the document group to contain the specific document that you want the user in user group to be able to edit them. Then set the user into the newly created user group that you just made. Now set a user role, so that the user doesn’t have access into the advanced manager area and assign it to that specfic user.

          That’s all folks...

          Hope I answered what you’ve requested. For more information about this, you can actually read the documentation. It’s easy to read and full of graphic to explain it in more detailed smiley

          Btw, I like this approach, so that I can add another documents or users later to this user group and document group. The best thing is, the user on the user group, if you granted them the ability to create a new docs, the new doc will be automatically assigned to the document group.

          Hope that helps.

          Sincerely,
          Wendy Novianto
            Wendy Novianto
            [font=Verdana]PT DJAMOER Technology Media
            [font=Verdana]Xituz Media
            • 17883
            • 1,039 Posts
            Hi,

            I have a similar question/problem.

            That´s what I´ve done:

            -created a User "testmanager"
            -created a user group "testmanagergroup"
            -created a role with permissions on editing/saving documents "testmanagerrole"
            -assigned user to this role
            -created a document group "testmanagerdocs"
            -assigned the testmanagerdocs to testmanagergroup
            -put 2 documents in this testmanagerdocs

            I thought this would give me the permission to edit these two docs with this testmanager from the frontend (after logging in with the managerlogin snippet), but the quickedit doesn´t render at all. If I log in with my admin account, all is fine. Spent three hours now, but don´t see the problem. Deleted Cookies already etc... BTW: If I login in the manager with this testmanager, I can edit the documents.
              • 25663 MODX Staff
              • 12,272 Posts
              MadeMyDay,

              Created a User or a Webuser?
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 17883
                • 1,039 Posts
                @ Ryan: A User, no webuser.
                  • 32241
                  • 1,495 Posts
                  Are you sure that you’re on the same domain when you login?
                  For example when you login using domain.com/manager, then when accessing the page to be edited, it will be domain.com/editedcontent.html. If you did that, and you did all the steps that you described, you’re suppose to be able to edit the document on the front end.

                  Have you tried logging in with manager id=1, and did you see the quickedit rendered on the front end?

                  Try to change the user into admin role, and see whether the quickedit will be rendered or not? If yes, try to edit the new role with all the document editing capability, including delte and etc, and try to login again. Does it rendered the quickedit?

                  Hope this troubleshooting does help you solve the problem.
                    Wendy Novianto
                    [font=Verdana]PT DJAMOER Technology Media
                    [font=Verdana]Xituz Media
                    • 17883
                    • 1,039 Posts
                    Hi, thx for your effords, I think I got it now:

                    Are you sure that you’re on the same domain when you login?

                    yes, its local.

                    Have you tried logging in with manager id=1, and did you see the quickedit rendered on the front end?

                    yes, no change.

                    Try to change the user into admin role, and see whether the quickedit will be rendered or not? If yes, try to edit the new role with all the document editing capability, including delte and etc, and try to login again. Does it rendered the quickedit?

                    That brought me to read again all the permission possibilities... It has to be checked "run modules", sure, the quick edit is also a module, and if the manager has no right to run it, it will not render wink So, now it renders with my testmanager. But I made an error in reasoning: All other pages are set to public, so I have to create (at least) one other group, where I restrict the permission only to admins and assign the pages to it. I thought I could give this testmanager the permissions to edit special content, but I also have to restrict the other content from editing by them. Right?! wink

                    Greetz Marc
                      • 32241
                      • 1,495 Posts
                      Cool you got it working.

                      Yes it’s true that you need to restrict certain pages that you don’t want the testadmin to be able to edit, which means you need to assign a document group to the pages and assign a manager user group to the doc group for it to be private.

                      Btw, good try on the run module, it does makes sense that you need the ability to run the module. If you set this to off, then the user might not be able to run QuickEdit, because it’s a module and needs to be run by the user.

                      Thanks for giving us a feedback.
                      Regards,
                        Wendy Novianto
                        [font=Verdana]PT DJAMOER Technology Media
                        [font=Verdana]Xituz Media