Hi, We are using/evaluating Magnolia 4.0.1, in particular the Data Module. we've set the following ACL entries on a user role:
DATA read only selected & sub / read-write selected & sub /content/item A user with the role can see and edit all the elements under /content/item, which is as expected. The user can also change the name of item, but upon doing so a javascript alert is fired with the text: "Can't rename: User not allowed to (Add, Set, Read) path [/content/item/MetaData]" The folder does appear to be renamed and is now locked for editing. It appears that the rename operation is not atomic - hence the problems. So, my questions form two parts: 1. ideally we'd like to prevent users renaming folders but allow them to add content to those folders, the sub nodes only access level seems to prevent this but the selected & sub nodes mode allows too much control (and appears broken - unless I've missed something) - any ideas? 2. the folder rename works strangely with ACLs - surely it should either be an atomic operation that moves the MetaData too or it should check the permissions of the parent to see if the user has permissions to make changes there. FWIW I'd say the second approach is better, but the first might be needed elsewhere? Thanks, Toby. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
