-
1. Re: Permissions on groups
julien1 Dec 5, 2003 4:10 PM (in response to j0lea)the rules are matched in the way they are declared. so if you match a rule before another, this rule will take precedence over all the other rules.
according what you say, I think you have understood how it works.
did you try to put the rule HtmlWriter before the one for User ? in that case it should match the html writer rule before.
or you can make HtmlWriter and HtmlReader group exclusive.
julien -
2. Re: Permissions on groups
j0lea Dec 5, 2003 5:52 PM (in response to j0lea)ok, that did it, I had the rules in thw wrong order, now it works:
.
.
.
<!-- ************** -->
<!-- * REGISTERED * -->
<!-- ************** -->
<!-- displays any html content -->
<permission component-pattern="html::" group="HtmlWriters" instance-pattern=".*::" level="EDIT"/>
<permission component-pattern="html::" group="Users" instance-pattern=".*::" level="READ"/>
<!-- Main Menu block -->
<permission component-pattern="core:menu:" group="Users">
.
.
.
I did the change in the nuke_services_attributes table, row pn_aid='Security'.
One things is still missing though: there is no way to specify that this user should have only EDIT access to a group of pages (specified by a prefix). Maybe the rules for the html module need to be changed to something similiar to those of core:menu, right? -
3. Re: Permissions on groups
julien1 Dec 6, 2003 5:35 AM (in response to j0lea)yes this is possible because these are regular expression so you can have :
instance-pattern = "/foo/.*::"
julien