[opencms-dev] Permission problem with ADE content structure

[Alexander Kandzior]

Tobias,

First, there is certainly no permission problem in ADE as everything works
as expected by the developers. Apparently you just expect something
different :)

ADE was "introduced" 4 years and 4 major releases ago. Rest assured that the
permission model is working fine.

As Kai has already pointed out, you can achieve what you want when you
create two subsitemaps with individual content folders, and then set
permissions to the folders individually.

Kind Regards,
Alex.

-------------------
Alexander Kandzior
                                                              
Alkacon Software GmbH  - The OpenCms Experts                 
http://www.alkacon.com - http://www.opencms.org                  




-----Original Message-----
From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Tobias Karrer
Sent: Tuesday, November 11, 2014 6:36 PM
To: The OpenCms mailing list
Subject: [opencms-dev] Permission problem with ADE content structure

Hi all!

As far as I can see, introducing ADE created a big permission problem, which
we didn't get solved by now satisfactorily.

Let's say we use resources of type "container" for editing content on pages.
So all Editors need to have write permission for folder
"/.content/container/". Further there are two Editor Groups which have the
right to edit different areas, e.g. two container-pages with a reference to
the containers above:

/.content/container/ - Permissions: Editors Press (+r+w+v), Editors HR
(+r+w+v)
     /c_00001.html
     /c_00002.html

/en/press/index.html - Permissions: Editors Press (+r+w+v)
     -> c_00001.html

/en/hr/index.html - Permissions: Editors HR (+r+w+v)
     -> c_00002.html

Finally, Editors Press won't be able to add or remove content in /en/hr/ and
vice versa, but they will be able to edit content of c_00002.html (as they
have +w on all containers).

I think the correct behaviour would be, that users must not be able to edit
containers, which are included in container-pages they don't have the right
to edit (or at least no until container is included in one container-page
they have the right to edit)

Someone already solved this problem?

@Alkacon: You never stumbled across this problem?

Best regards,
Tobias
_______________________________________________
This mail is sent to you from the opencms-dev mailing list To change your
list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev