How can one disallow a none-Administrator manager to edit and delete specific resources under MODX Evolution 1.0.10?

Instead of having the container protected and hacking = destroying the security features built in, let the container be accessible and restrict access to it with ManagerManager:

I maked this (mm_widget_accessdenied) this one variant... But editors can delete container documents and make trouble without not even specifically. We have many editors and they may come and go out from company))

Better to make that access permitions of new document every time will be withot protection group.. I will try))

- You could set up NewsEditor/Publisher or pubKit and have them add/delete/publish through the front-end as web users instead of giving them manager access.

- You could backup duplicates of the containers to restore them easily.

- You could restrict users from purging the resources, and then write a plugin that undeletes deleted parents! [ed. note: mrhaw last edited this post 12 years, 3 months ago.]

Quote from: magerik at Jul 06, 2014, 05:27 PM

I maked this (mm_widget_accessdenied) this one variant... But editors can delete container documents and make trouble without not even specifically. We have many editors and they may come and go out from company))
Better to make that access permitions of new document every time will be withot protection group.. I will try))

There's interestingly named system event OnBeforeDocFormDelete - maybe it could be used to extend mm_widget_accessdenied with resource deleting protection?