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