Allow designated users to remove other user's drafts

Next topic

Author	Message
James Robertson	Wednesday 31 August 2005 4:31:29 pm Within some of the eZ publish sites we administer, some users (accidentally) create draft objects which then remain in the system for a long time. It would be nice to be able to allow other users (ie. Admin.) to be able to delete their (very old) draft objects. Or possibly have an automated system for this, whereby draft object that are older than say a month are deleted. This should be applied especially if there are no chnages between the draft object and the version it was based on.
Kristof Coomans	Thursday 01 September 2005 12:49:19 am Currently it is not possible to know on which version a draft was based. Creating a new draft copies the content of the published version, but another draft can be published afterwards. It would be usefull to add a new field to the ezcontentobject_version table which contains the version it was based on. A cronjob could then loop over the drafts, check all the version's attributes on differences in data_int, data_float and data_text, and the version's related objects. If there are no differences, the draft can be removed. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org

Author

Message

Wednesday 31 August 2005 4:31:29 pm

Within some of the eZ publish sites we administer, some users (accidentally) create draft objects which then remain in the system for a long time. It would be nice to be able to allow other users (ie. Admin.) to be able to delete their (very old) draft objects.

Or possibly have an automated system for this, whereby draft object that are older than say a month are deleted. This should be applied especially if there are no chnages between the draft object and the version it was based on.

Kristof Coomans

Thursday 01 September 2005 12:49:19 am

Currently it is not possible to know on which version a draft was based. Creating a new draft copies the content of the published version, but another draft can be published afterwards.

It would be usefull to add a new field to the ezcontentobject_version table which contains the version it was based on. A cronjob could then loop over the drafts, check all the version's attributes on differences in data_int, data_float and data_text, and the version's related objects. If there are no differences, the draft can be removed.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

eZ debug

Timing:	Jan 31 2025 00:40:12
Script start
Timing:	Jan 31 2025 00:40:12
Module start 'layout'
Timing:	Jan 31 2025 00:40:12
Module start 'content'
Timing:	Jan 31 2025 00:40:12
Module end 'content'
Timing:	Jan 31 2025 00:40:12
Script end

Main resources:

Total runtime	0.0202 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.0044	588.3750	151.2422
Module start 'layout'	0.0044	0.0034	739.6172	220.7344
Module start 'content'	0.0077	0.0109	960.3516	997.7266
Module end 'content'	0.0187	0.0015	1,958.0781	29.9922
Script end	0.0202		1,988.0703

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	12.7125	14	0.0002
Check MTime	0.0011	5.3967	14	0.0001
Mysql Total
Database connection	0.0006	2.9412	1	0.0006
Mysqli_queries	0.0019	9.3611	3	0.0006
Looping result	0.0000	0.0401	1	0.0000
Template Total	0.0011	5.5	1	0.0011
Template load	0.0009	4.2909	1	0.0009
Template processing	0.0002	1.2272	1	0.0002
Override
Cache load	0.0006	2.9872	1	0.0006
General
dbfile	0.0003	1.3250	8	0.0000
String conversion	0.0000	0.0259	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