[ 
http://jira.magnolia-cms.com/browse/MAGNOLIA-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Haderka updated MAGNOLIA-2599:
----------------------------------

    Fix Version/s: 4.3.x
                       (was: 4.3.2)

> Make audit logging fully configurable
> -------------------------------------
>
>                 Key: MAGNOLIA-2599
>                 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2599
>             Project: Magnolia
>          Issue Type: Improvement
>    Affects Versions: 4.0
>            Reporter: Jan Haderka
>            Assignee: Boris Kraft
>             Fix For: 4.3.x
>
>
> Currently only after all data is gathered, AuditLoggingManager is called. It 
> should be possible to instrument all the aspects of logging even obtaining 
> user name as in some situations (startup, installation) such data might not 
> be available and attempt to obtain them causes chain of failures (nice 
> example is recent update of node types in user workspace ... can't really 
> read user names while manipulating the nodes representing users themselves).

-- 
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: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to