Audit trail for object creation and modification

Next topic

Author	Message
zurgutt -	Thursday 10 September 2009 9:06:29 am Strangely eZ publish audit trail functions include content delete and content move but omit object creation and modification. Where would be good place in kernel to include eZAudit::writeAudit functions for those? Certified eZ developer looking for projects. zurgutt at gg.ee
Łukasz Serwatka	Friday 11 September 2009 12:55:54 am Hi, One way can be a single wrokflow event after-publish where you basically check the version number. If version == 1 then you can assume object was just created if is version higher then 1 then object was modified. Should be very simple. Other then that you would need hack the kernel which is maintenance pain. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
zurgutt -	Monday 14 September 2009 2:57:57 am I meant kernel hack, just one line to add if i knew where. The inner workings of kernel are hard to figure out. Can you advice? Anyhow, shouldn't this be in kernel by default? Strange that most frequent operations are left out of audit. Kernel hack often is quicker, easier and more reliable than creating the whole extension/workflow bahoopla. Maintenance is not necessarily that big a pain, can even be automated - always during upgrade diff from untouched original version, apply diff to new version. Certified eZ developer looking for projects. zurgutt at gg.ee

Author

Message

Thursday 10 September 2009 9:06:29 am

Strangely eZ publish audit trail functions include content delete and content move but omit object creation and modification.

Where would be good place in kernel to include eZAudit::writeAudit functions for those?

Certified eZ developer looking for projects.
zurgutt at gg.ee

Łukasz Serwatka

Friday 11 September 2009 12:55:54 am

Hi,

One way can be a single wrokflow event after-publish where you basically check the version number. If version == 1 then you can assume object was just created if is version higher then 1 then object was modified. Should be very simple. Other then that you would need hack the kernel which is maintenance pain.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

zurgutt -

Monday 14 September 2009 2:57:57 am

I meant kernel hack, just one line to add if i knew where. The inner workings of kernel are hard to figure out. Can you advice?

Anyhow, shouldn't this be in kernel by default? Strange that most frequent operations are left out of audit.

Kernel hack often is quicker, easier and more reliable than creating the whole extension/workflow bahoopla. Maintenance is not necessarily that big a pain, can even be automated - always during upgrade diff from untouched original version, apply diff to new version.

Certified eZ developer looking for projects.
zurgutt at gg.ee