System Tracking of managing contents

Author Message

Ugo Giacalone

Tuesday 27 October 2009 4:58:52 am

It could be useful to have a system tracking content editing in Ez.

Using versions we can know many information about editing of content, but we don't have information about deleting, moving or adding location contents.

In table "ezcontentobject_trash" are information about node, but there isn't data about the deleting request (user and data of deleting).

We suggest to create a table in database where to track all edit events of user with these information:

- user_id
- date of event
- kind of event (edit, delete, move, add location,...)
- Content data (node_id, contentobject_id, parent_node_id, main_node_id,...)

For big sites with many editors have a system tracking is very important.

Peter Keung

Tuesday 27 October 2009 5:45:25 am

The audit trailing system might meet your needs:

http://ez.no/doc/ez_publish/technical_manual/4_x/features/audit_trailing

http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada

Ugo Giacalone

Wednesday 28 October 2009 6:38:01 am

Perfect. Thanks.

Ugo Giacalone

Wednesday 28 October 2009 9:59:19 am

Somebony know if it's possible to set an time interval for storing of log files?

Gaetano Giunta

Saturday 23 January 2010 3:13:06 am

Not that I know of - but there are 2 'magical' global variables you can define in config.php to alter the max size of log files before they are rotated and the number of rotated files that are kept.

Look up in an issue in the issue tracker for the exact names of those 2 vars... ;)

Principal Consultant International Business
Member of the Community Project Board

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 30 2025 16:28:54
Script start
Timing: Jan 30 2025 16:28:54
Module start 'layout'
Timing: Jan 30 2025 16:28:54
Module start 'content'
Timing: Jan 30 2025 16:28:54
Module end 'content'
Timing: Jan 30 2025 16:28:54
Script end

Main resources:

Total runtime0.0297 sec
Peak memory usage6,144.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0060 588.2500151.2266
Module start 'layout' 0.00600.0051 739.4766220.7031
Module start 'content' 0.01110.0169 960.17971,001.7891
Module end 'content' 0.02800.0017 1,961.968833.9922
Script end 0.0297  1,995.9609 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00268.8563140.0002
Check MTime0.00103.4960140.0001
Mysql Total
Database connection0.00072.292110.0007
Mysqli_queries0.004013.353930.0013
Looping result0.00000.061010.0000
Template Total0.00124.010.0012
Template load0.00103.312210.0010
Template processing0.00020.687010.0002
Override
Cache load0.00072.252010.0007
General
dbfile0.003210.704780.0004
String conversion0.00000.031340.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs