Thursday 01 May 2003 3:25:38 am
Actually I've been thinkinig alot about this since I need lifecycle functionality. What needs to be implemented is a lifecycle workflow which one can attach to every content object (and section / ++ / ?? ). What you would then do is to attach a 10-day... or a 20-day .. or indefinate .. or 1000 day lifecycle to the object (could be an article .. or an image .. or..) .. and after that lifecycle ends the object is archived and perhaps the user who created the object could get a notification (this should also be available in a tab to manage archived content) .. to decide if he wanted to edit the object again and attach a new lifecycle enabling the content object to be published again. This should be quite easy .. provided the workflows/events/trigger stuff done in Ez has been implemented in a fair fashion. Any ideas?? Bård: could you share the cron script you run to do this?? Just to have a look at it?? I really would like to see this.. Thanks in advance!
Kindest, Jørgen Skogstad
|