Choosing between two bad options...protected pages

Hi,

I have 200+ documents in the tree and I want to add another document, but it is buried deep into the menu structure of the site. This new document needs to be edited by a new manager that has only access to this specific document.

Two options:

• if I don’t set "protected pages" to on, my manager user will never see the page in the tree, since it is the child of a parent document she doesn’t have access to.
• If I do set "protected pages" to on, my manager user will never find the page in the tree, because it’s buried so deep. She will see

I guess there’s no in between way of showing only documents to which the user has edit rights to? What would be te best choice here?
Or should I place the new document in the root, not visible, not published, and have the document contents be retrieved through a snippet on a page in the tree (don’t want to go there....)?

Thanks.

what is with using qm+ and editing this page directly from frontend?

Quote from: Bruno17 at Oct 29, 2009, 02:39 AM

what is with using qm+ and editing this page directly from frontend?

Hmm, never really thought of that. I’ve never used QM and deleted all references of this...I guess if I upgrade to Evo 1.0.1 I can get it back.
The page has text, a MaxiGallery call and possibly a call to the FileDownload snippet. For the latter, they would need to be able to access the file manager in the manager anyway.

Would QM also work with MaxiGallery?

they would need to be able to access the file manager in the manager anyway

you could create a file-TV to have access to the file-manager out of the qm-box.

Would QM also work with MaxiGallery?

I think it depends on the embedtype of MaxiGallery. If not I’m sure there are workarrounds. I would try it out.

Quote from: sderuiter at Oct 29, 2009, 02:44 AM

Would QM also work with MaxiGallery?

Yes, with the following ManagerManager widget:
http://modxcms.com/forums/index.php/topic,29875.0.html

Would QM also work with MaxiGallery?

Yes, with the following ManagerManager widget:

...why would you need that widget to edit a page in the frontend with QuickManager + MaxiGallery? ...it’s rather to manage your galleries from the backend (sure, you could manage the gallery in the QM interface using that widget - would be nice though ...but not necessarily). with QuickManager your’re already on the frontend where you got the option to edit your galleries already+ manage other page content with QuickManager