Hello Magnolians, I managed to set up authorities in a role so a user with that role can edit only one tree of pages in the Website repository. Unfortunately the user seems not to be able to activate pages in its tree unless it has read/write rights for the complete Website repository. Is this expected behaviour? I have been searching the documentation and wiki for more detailed information about this, but couldn't find it. (Did I miss it?)
I use magnolia 4.2.1. I activated the user and the role. I do logout the test user in between changes. Here's my configuration: [cid:[email protected]] This way the user can only edit the /testsite tree. The other trees he can only read, except the /TEMPLATE* and /project* trees, which he cannot see at all. Activation of a page in the testsite tree does not succeed until I remove the last entry (read only subpages /*). But I do not want to remove that line, because I do not want the user to edit other trees. The message "Can't activate etc" is quite mysterious even. Every time I try to active the same node, the path in the message is different every time. "User not allowed to (Add, Set, Read) path [/<someUUID>/Metadata]". The <someUUID> is a different id every time, and I cannot find it in any export of the website repository I make. Any help or hint is much appreciated! Best regards, Bert ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
<<inline: image002.png>>
