How to give quick edit permissions for only one page?

I’m running 0.9.2.1, and there is not option in the roles section of users to kill the right to use the backend manager.

Quote from: seventhapex at Jul 20, 2006, 11:28 AM

I’m running 0.9.2.1, and there is not option in the roles section of users to kill the right to use the backend manager.

Yes, it’s grayed out, but you can get it enabled though. What are you trying to do`? If you are trying to setup a user who cannot access the manager but could use quick edit, it’s not possible currently I’m afraid. If this is what you are after, you could check the following links to read what can and can’t be done and why. Dimmy has done a bit testing on this. This issue will be gone after the separation between web users and manager users is removed, but for now, I guess you could get it working by doing little research..

FS#161 — Setting off "Manager Interface Access" on User Setting
How to create User that can edit only from the QuickEdit?

thanks for the replay doze ^zzzzz jk

this is indeed what I’m attempting to do. (front end content management)

I have read the bug report on this issue and have had the same problem myself, the option however is in the "user setting" within the "manage users" tab, I’ve been researching this issue for two days, and I’m not PHP savy enough to get it working through a hack, module or plugin... Perhaps a better way to put it is I don’t really wanna completely screw up my install yet.


I followed the links you posted out to the far reaches of the modx forum community and it looks honestly like, without an update to the current core code it’s not going to be possible, without a hack job.

it’s obviously possible to create pages from a web users login ie. "Ditto" and the "newslistings" snippit. it should therefor be possible to edit them also correct?

There is a newsmanager snippet package (newspublisher, manager, editer) that you can use to edit documents, but not tv values. Then theres Wendy’s docApi library, what you could use to create a own frontend edit thing.. but there isn’t nothing ready made to do all that quickedit does.. I think that the easiest route would be to hack quickedit to work even if manager access is disabled, but I might be wrong because I haven’t take a look to see what’s the problem with it..

EDIT: But all these needs PHP knowledge.. so I think if you are not up to it, you just have to wait. Sorry

I’ll look into the quickedit hack, that’s probably going to be my short term solution.

Now that I read what I wrote, I see that it might be understood wrong, so here’s an explanation: QuickEdit uses manager pages to get the editing area, so you need your users to login to the backend, but you don’t want them to be able to access manager. So one quick solution (and not a secure way to disable backend usage altogether) would probably be to use ManagerLogin snippet to get users login without going to the manager login page, then modify the manager index.php file to check if the user does not have rights to request manager frames, then deny access IF the request is not a quickedit action.. look what url parameters quickedit uses in it’s index.php call and maybe work with those..

These are just thoughts how it might work as I don’t really know the underlying code.. and this will not prevent users who are logged to the backend through your ManagerLogin snippet to access some manager pages totally.. but if you need this just to disable manager usage from certain users what do not know even what backend manager is, then maybe it’s not a problem..

that’s a great solution, and probably not terribly complicated in implementation, it should work until the update is released anyway.

Thanks for your help doze

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.

in order to let each user edit just his/her page, the site manager has to iterate the above process for each user, quickly filling up the MODx manager with lots of one-member UserGroups granted edit access to one-document DocumentGroups!

check Learningmodx.com, the author promised to release his snippet soon, but I do believe this is a very crucial functionality that will have to be included in the CMS core sooner or later, e.g. a ’create personal-page in...’ checkbox in the user creation form, + some extra elements in the ’user settings’ tab to manage the page (actually the ’Manager Login Startup’ for default page-id is already in there!)

why you think it would "have to be included to modx core sooner or later"? The less there are stuff by default the better. Why these could not be addons? For example, i would like to see the whole native user system of modx as an separate addon.

Indeed. I would be very happy to have the core itself just support a single "admin" user, with a good user management API library, and all other user management is provided with add-ons. This would allow for considerable flexibility in user management according to the needs of the site.

I’m hoping to see the day when I can install a bare-bones system with no fancy javascript editors, no embedded javascript resource browsers, one default admin user, and one default manager template. Sort of like the two options for the front-end, one default minimal page, or a whole sample site; have the same option for the back end. Have a choice of installation packages.