<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thank you Claus, now I understand the meaning of <i>overwriting
inherited</i>.<br>
I tried to uncheck the write and publish permission over the directory
to the parent group and I found that it isn't enough: you must unchek
permission to Users group too, even if it isn't in relation with my
groups (probably there is an intrinsic relation between Users group and
groups created by an operator). After this action everything works.<br>
Just a note, in the 6.2.3 version the same login doesn't work!<br>
Bye and thank you again<br>
Roberto<br>
<br>
Claus Priisholm wrote:
<blockquote cite="mid:48D0C8C6.50102@codedroids.com" type="cite">Not
sure I follow exactly what it is you are trying to do, but remember
that explicitly denying a permission is different from removing the
permission.
<br>
If you explicitly deny a permission then it cannot be overridden
whereas if you remove (uncheck in the UI) a permission on the folder,
then you can allow it for a file inside the folder (by checking it in
the UI).
<br>
<br>
Roberto Melino wrote:
<br>
<blockquote type="cite">I've a lot of file in a folder and I need to
create a group for every file to operate (write/publish) on it (one
group only on one file).
<br>
My first idea was to deny actions on parent group of my set of groups
over the container folder and, than, enable for each file the
permission for the owner group. I thought, wrongly, that using the flag
/overwriting inherited/ will modify the denied permissions to enabled
where the group change the permissions from the parent ones. I learned
to my cost that the ACL login doesn't work in that way. The enabled
permissions are overwritten, the denied ones are added.
<br>
I found on Dan Liliedahl' book /OpenCms 7 Development/ that the way to
obtain the permission behavior that I need is to set enabled and denied
permissions for every group on every file. This solution is not
applicable for me because groups and files change continuously and are
too much to be managed in such a way.
<br>
Have anyone of you an idea to solve my problem?
<br>
Thanks in advance.
<br>
-- <br>
*Roberto Melino*
<br>
<br>
<br>
------------------------------------------------------------------------
<br>
<br>
<br>
_______________________________________________
<br>
This mail is sent to you from the opencms-dev mailing list
<br>
To change your list options, or to unsubscribe from the list, please
visit
<br>
<a class="moz-txt-link-freetext" href="http://lists.opencms.org/mailman/listinfo/opencms-dev">http://lists.opencms.org/mailman/listinfo/opencms-dev</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>