-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
None
The audit log classes are only used used when using the Content API. When using the JCR APIs, it seems they're just never used.
This could be reimplemented by using the wrappers. I understand that all our session objects are already wrapped, so it shouldn't be too big a deal.
Also linking further improvement to the audit log API - to take into account, not necessarily implement as a fix to this issue.
Concept page: http://wiki.magnolia-cms.com/display/DEV/Concept+-+Move+AuditLog+from+Content+API+to+JCR+API
- depends upon
-
MAGNOLIA-4810 Wrappers don't wrap everything what should be wrapped
- Closed
- is causing
-
MAGNOLIA-5421 MgnlAuditLoggingContentDecoratorNodeWrapper ignores property types
- Closed
- is related to
-
MAGNOLIA-2730 Reimplement audit and security using HierarchyManagerWrapper, ContentWrapper, etc.
- Closed
-
MAGNOLIA-5013 Add possibility into AuditLogging inform about overcrowded log entries
- Closed
-
MAGNOLIA-5012 Add possibility into AuditLogging to monitor only specific workspace
- Closed
-
MAGNOLIA-4992 ContentDecorator can be lost if workspace is use
- Closed
-
MAGNOLIA-5022 Move auditing related code into info.magnolia.audit package
- Closed
- mentioned in
-
Wiki Page Loading...