Hi Folks
I'm in the throes of getting to grips with the mechanics of Permissions.
When I assign the Admin group to a series of categories
I find that the user, as intended, does not see those elements within those categories
in their Elements tree.
However they do still see the empty category folders.
As there are one or two chunks they need to be able to edit I cannot simply hide the Elements tree as a whole.
I've tried all sorts of things without success…
ie nesting the categories, but that simply results in the user
seeing a group of nested empty folders.
Perhaps I'm missing the function/purpose of a particular permission *
So in the interest of a decent editing experience i.e. hiding extraneous stuff,
is there any way of getting rid of the folders too?
Obviously this is not a function-critical issue but more an optimisation one.
* Also is anyone aware of any documents explaining in more detail the
workings of the individual permissions, as I find I'm constantly tripping myself up
with the hierarchical and dependent nature of some of them?
Or am I over thinking things here?
Any pointers would be much appreciated.
Many Thanks
Chris
My setup:
MODX latest (2.5.2)
MAMP (latest (3.0.7.3))
PHP (5.5.26)
MySQL (5.5.38)
Chrome: Std and Canary (latest versions allowable by OS)
Mac OX (Mountain Lion-10.8.5).
[ed. note: geordiechris last edited this post 9 years, 10 months ago.]
Try flushing both sessions and permissions, then manually deleting all files in the core/cache directory. If that doesn't help, It sounds like a bug in MODX.
BTW, you did protect the category with an Element Category Access ACL entry with a context of 'mgr', right?
Here's some info on permissions:
http://bobsguides.com/revolution-permissions.html
There is also this
51-minute video, that explains the permissions system from the inside out.
Hi Bob
Yep tried flushing and cache emptying (I tend to do that on a very regular basis these days).
And yes I had added the protection you mention with an Access Policy of 'Element'.
I've also added an identical entry with a context of 'web'.
I have also watched your video a couple of times; once when I started learning MODX and more recently
(where it made a whole lot more sense!).
I've also worked through the relevant guidance on your site too.
But I'll go through things again.
Thanks for your time
Chris
If you protected the category itself (not just the elements in it), it does sound like a bug.
You could report if here:
https://github.com/modxcms/revolution/issues
Hi Bob
This is what I'm doing…
Access Control Lists
'User Groups & Users' Tab
Right-click 'Administrator' > 'Update User Group'
'Permissions' Tab > 'Context Access' Tab
Context: mgr
Minimum Role: 'Super User'
Access Policy: 'Administrator'
Ditto for web context.
'Element Category Access' Tab
Category: 'MyCategory'
Minimum Role: 'Super User'
Access Policy: 'My duplicate of Element'
Context: 'mgr'
Ditto for web context.
---------------------------
'User Groups & Users' Tab
Right-click 'MyUserGroup' > 'Update User Group'
'Permissions' Tab > 'Context Access' Tab
Context: mgr
Minimum Role: 'Member - 9999'
Access Policy: 'My duplicate of Context'
plus
Context: web
Minimum Role: 'Member - 9999'
Access Policy: 'My extreme minimal version based on Admin'
---------------------------
This should hide 'MyCategory' and its contents from all other users with
a default role of 'Member - 9999' in their web context ACL, right?
Am I missing a step perhaps?
(despite studying this for a few hours now, my grasp
on the correct usage of Contexts is not crystal clear just yet)
Otherwise if I am on the right track, as you say, maybe this is a bug that I need to flag...
Many thanks
[ed. note: geordiechris last edited this post 9 years, 10 months ago.]
