[
http://jira.magnolia-cms.com/browse/MAGNOLIA-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25384#action_25384
]
Jan Haderka commented on MAGNOLIA-2903:
---------------------------------------
It's tad more complicated then that, as we do not move the original node
anywhere and security check needs to happen for all properties as well not just
at the node level, but yeah, the temp node has to be indeed handled in system
context.
> activation: users having only write permission in a subpart of the hierarchy
> are not able to activate
> ------------------------------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2903
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2903
> Project: Magnolia
> Issue Type: Bug
> Components: activation
> Affects Versions: 4.1.1
> Reporter: Philipp Bärfuss
> Assignee: Jan Haderka
> Priority: Critical
> Fix For: 4.1.3, 4.2.2
>
> Attachments: activation_error_1.log, activation_error_2.log,
> screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg
>
>
> In the following line a temporary node is created in the root of the
> workspace (the node name is the uuid)
> --> ReceiveFilter.importOnExisting(ReceiveFilter.java:420)
> If a user cannot write to the root, but only to a sub hierarchy, he cannot
> create this temporary node.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
