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

eZ debug

Timing:	Jan 31 2025 03:43:16
Script start
Timing:	Jan 31 2025 03:43:16
Module start 'layout'
Timing:	Jan 31 2025 03:43:16
Module start 'content'
Timing:	Jan 31 2025 03:43:16
Module end 'content'
Timing:	Jan 31 2025 03:43:16
Script end

Main resources:

Total runtime	0.0198 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0045	588.2656	151.2266
Module start 'layout'	0.0045	0.0033	739.4922	220.7188
Module start 'content'	0.0077	0.0108	960.2109	997.7422
Module end 'content'	0.0185	0.0012	1,957.9531	33.9922
Script end	0.0197		1,991.9453

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	11.8762	14	0.0002
Check MTime	0.0010	5.1013	14	0.0001
Mysql Total
Database connection	0.0009	4.4044	1	0.0009
Mysqli_queries	0.0018	8.9813	3	0.0006
Looping result	0.0000	0.0506	1	0.0000
Template Total	0.0009	4.3	1	0.0009
Template load	0.0007	3.3326	1	0.0007
Template processing	0.0002	0.9863	1	0.0002
Override
Cache load	0.0005	2.3415	1	0.0005
General
dbfile	0.0011	5.3955	8	0.0001
String conversion	0.0000	0.0289	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs