[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22617#action_22617
 ] 

Hudson CI server commented on MAGNOLIA-2396:
--------------------------------------------

Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif! 
[magnolia_main-trunk 
#818|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/818/]
      
- Ensure metadata are _always_ updated after (de)activation.
- be consistent in placing auditing code.


> User context is used to update activation metadata
> --------------------------------------------------
>
>                 Key: MAGNOLIA-2396
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2396
>             Project: Magnolia
>          Issue Type: Bug
>          Components: activation
>            Reporter: Philippe Marschall
>            Assignee: Jan Haderka
>            Priority: Minor
>             Fix For: 4.1
>
>
> For activation of content an arbitrary user can be used. The method 
> {{info.magnolia.cms.exchange.Syndicator.init(User, String, String, Rule)}} 
> allows to pass the user to be used in the syndicator. However to update the 
> activation details the user from the current web context is used. This is a 
> problem if the current web user is not allowed to edit the metadata of an 
> activated node.
> I think the methods #updateActivationDetails and #updateDeactivationDetails 
> in BaseSyndicatorImpl should use the system context instead of the current 
> web context.

-- 
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]>
----------------------------------------------------------------

Reply via email to