Quote from: Tom at Feb 14, 2013, 07:25 AM
Our suggestion would be to have:
- Security reset button - Clear all security and go to default.
- Basic/Advanced Securty Site parameter - If selecting Basic, all we can do is to have a context parameter where we simply can select *one* user group that is allowed to edit pages. No more? Right! No more. Simple and happy for 95% of sites
I'm sorry that you didn't get it worked out. I know working with MODX security permissions can be frustrating.
On your ideas -- Number one is a great idea. I've thought of writing an extra for that.
On number two, please don't see me as defending the current Revo security system, but I don't think it's accurate to say that would handle 95% of sites. It would be nice, but people have very different needs.
Here, in my experience, are the most common issues (in order of complexity):
1. Developer is the only user -- no security needed
Users/Clients who need:
2. to have scary parts of the Manager hidden
3. full access, but not to all resources
4. their actions limited (e.g., can't delete; can edit but not publish; etc.), but can access any resource
5. different access levels to different resources
6. the features above, but for elements and/or contexts
Not every site needs levels 5 or 6, but a surprising number of sites do. The trick is to accommodate those needs and still have a simple system. It's difficult to create a security architecture that will do both.
☆ A M B ☆
