Lifecycle : Expiration of articles that have been inserted into the system.. howto..

Next topic

Author	Message
Jørgen Skogstad	Sunday 27 April 2003 6:16:03 am Kindest .. I think I have heard someone say that you can apply lifecycle(s) to the EzPublish v3 system. What I am looking for is that my site does not show articles older than 30 (or any other given numer) days .. How can this be achieved?? Wasn't there a cronjob that needed to be applied in the system... and the data is not deleted from the database I hope. I will have to retain all data, but not show things that are older than one or several dates. This should also be able to set within each article. .. how can this be achieved?? Would love to get some feedback! Kindest, Jørgen Skogstad
Scot Wilcoxon	Sunday 27 April 2003 9:31:21 pm I don't know if there is anything built in, but the SQL to test the age and turn off the "ispublished" flag in table ezcontentobject is simple. I don't know what values the "status" field accepts. But turning off "ispublished" may make it a little difficult to identify what are drafts which aren't approved for publication yet.
Tony Wood	Monday 28 April 2003 12:31:23 am Try using the workflow system, it has a publish and unpublish feature. Hopefully eZ will write an HOWTO. Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future
Jørgen Skogstad	Wednesday 30 April 2003 2:23:02 pm Ah! Good point .. not tried that yet. Perhaps one then could apply a 10-day workflow with an unpublish at the end .. of sorts .. if that's what you wanted with this article .. and with others .. 20-day .. 40-day .. 100-day.. etc?? You tried this?? This should be documented by Ez. These are vital parts of any cms system .. and this is really .. well; essential. The guys should document these things.. and provide howto's .. Kindest, Jørgen Skogstad
Tony Wood	Thursday 01 May 2003 2:40:01 am >>unpublish Not yet, although its on my R&D list... :) Your right there a load of things you learn through putting the time in. Most users post this new learning to contributions page. Tony Wood : twitter.com/tonywood Vision with Technology Experts in eZ Publish consulting & development Power to the Editor! Free eZ Training : http://www.VisionWT.com/training eZ Future Podcast : http://www.VisionWT.com/eZ-Future
Jørgen Skogstad	Thursday 01 May 2003 3:06:19 am I know! Heh .. trying to figure these things out.. I have to try to migrate 10 sites under the one Ez install (v3) .. and some of those site have to have a lifecycle attached to certain article types! Hehe .. this should be pretty easy to do if one had at least all documented features! ;) .. I also remember reading about some types of shell scripts to "unpublish" articles from crontab, but never seen any details on this.. If you get some thinigs done with this lifecycle thing please yell out man ... hehe .. I will sure as /&"# do likewise! Keep it up! Kindest, jØRGEn!:.

eZ debug

Timing:	Jan 30 2025 21:42:22
Script start
Timing:	Jan 30 2025 21:42:22
Module start 'layout'
Timing:	Jan 30 2025 21:42:22
Module start 'content'
Timing:	Jan 30 2025 21:42:23
Module end 'content'
Timing:	Jan 30 2025 21:42:23
Script end

Main resources:

Total runtime	1.3055 sec
Peak memory usage	8,192.0000 KB
Database Queries	68

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	588.6250	151.2734
Module start 'layout'	0.0054	0.0041	739.8984	220.7656
Module start 'content'	0.0095	1.2950	960.6641	4,525.8828
Module end 'content'	1.3045	0.0009	5,486.5469	15.7500
Script end	1.3055		5,502.2969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0038	0.2897	16	0.0002
Check MTime	0.0014	0.1067	16	0.0001
Mysql Total
Database connection	0.0007	0.0573	1	0.0007
Mysqli_queries	1.2016	92.0415	68	0.0177
Looping result	0.0008	0.0588	66	0.0000
Template Total	1.2365	94.7	2	0.6182
Template load	0.0021	0.1634	2	0.0011
Template processing	1.2343	94.5503	2	0.6172
Template load and register function	0.0013	0.1030	1	0.0013
states
state_id_array	0.0022	0.1710	1	0.0022
state_identifier_array	0.0030	0.2270	2	0.0015
Override
Cache load	0.0019	0.1442	39	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0017	0.1318	3	0.0006
Fetch class attribute name	0.0022	0.1720	8	0.0003
XML
Image XML parsing	0.0011	0.0867	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0020	11	0.0000
General
dbfile	0.0019	0.1461	22	0.0001
String conversion	0.0000	0.0007	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
5	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
9	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
5	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 27 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs