Is there a "publish-to-date" function?

Next topic

Author	Message
Fredrik Melsom Klausen	Wednesday 08 September 2004 2:45:54 pm I need the possibility to set an article to be automatically published/visible on a given date, and to be automatically unpublished/invisible on a given later date. Is this something that is possible to set in the admin interface? I have looked around quite a bit without finding a solution. If it's not, is there any other way? Help would be greatly appreciated :-) Fredrik
Ole Morten Halvorsen	Thursday 09 September 2004 1:18:11 am Fredrik, Future publishing is a standard feature in eZ publish. You need to add a datetime attribute to your class(es), create a new workflow with a Wait until date event and add this workflow to a trigger. Make sure you run the runcronjobs.php as a cronjob aswell. Currently we dont have an unpublish feature, but we are working on it for 3.5. Have a look at the spec here: http://www.ez.no/community/specs/hide_unpublish Ole M. Senior Software Engineer - Vision with Technology http://www.visionwt.com http://www.omh.cc http://www.twitter.com/omh eZ Certified Developer http://ez.no/certification/verify/358441 http://ez.no/certification/verify/272578
Marco Zinn	Sunday 21 November 2004 12:57:01 pm On order to add to the community knowledge: This worked fine for me (for timed publishing). Using a 3.4.4. installation, i created a copy of the article class, added a "datetime" attribute for this. Then i create a new workflow with the "wait until date" event, selected my new class and that new attribute. After saving the class, i assigned this new workflow to the "before publish" trigger. That did the job! Remember, that you need to set up a cronjob for the workflow to "advance". See http://ez.no/ez_publish/documentation/installation/the_cronjob_script for cronjob information. Marco http://www.hyperroad-design.com

Author

Message

Wednesday 08 September 2004 2:45:54 pm

I need the possibility to set an article to be automatically published/visible on a given date, and to be automatically unpublished/invisible on a given later date. Is this something that is possible to set in the admin interface? I have looked around quite a bit without finding a solution. If it's not, is there any other way? Help would be greatly appreciated :-)
Fredrik

Ole Morten Halvorsen

Thursday 09 September 2004 1:18:11 am

Fredrik,

Future publishing is a standard feature in eZ publish. You need to add a datetime attribute to your class(es), create a new workflow with a Wait until date event and add this workflow to a trigger. Make sure you run the runcronjobs.php as a cronjob aswell.

Currently we dont have an unpublish feature, but we are working on it for 3.5. Have a look at the spec here: http://www.ez.no/community/specs/hide_unpublish

Ole M.

Senior Software Engineer - Vision with Technology

http://www.visionwt.com
http://www.omh.cc
http://www.twitter.com/omh

eZ Certified Developer
http://ez.no/certification/verify/358441
http://ez.no/certification/verify/272578

Marco Zinn

Sunday 21 November 2004 12:57:01 pm

On order to add to the community knowledge:
This worked fine for me (for timed publishing). Using a 3.4.4. installation, i created a copy of the article class, added a "datetime" attribute for this.
Then i create a new workflow with the "wait until date" event, selected my new class and that new attribute. After saving the class, i assigned this new workflow to the "before publish" trigger.
That did the job! Remember, that you need to set up a cronjob for the workflow to "advance".
See http://ez.no/ez_publish/documentation/installation/the_cronjob_script for cronjob information.

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 19 2025 06:16:54
Script start
Timing:	Jan 19 2025 06:16:54
Module start 'layout'
Timing:	Jan 19 2025 06:16:54
Module start 'content'
Timing:	Jan 19 2025 06:16:55
Module end 'content'
Timing:	Jan 19 2025 06:16:55
Script end

Main resources:

Total runtime	1.5062 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0065	589.1563	152.6250
Module start 'layout'	0.0065	0.0030	741.7813	39.4609
Module start 'content'	0.0095	1.4951	781.2422	567.4688
Module end 'content'	1.5046	0.0015	1,348.7109	12.1563
Script end	1.5061		1,360.8672

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.2204	16	0.0002
Check MTime	0.0013	0.0883	16	0.0001
Mysql Total
Database connection	0.0012	0.0787	1	0.0012
Mysqli_queries	1.4517	96.3835	59	0.0246
Looping result	0.0008	0.0504	57	0.0000
Template Total	1.4551	96.6	2	0.7275
Template load	0.0020	0.1333	2	0.0010
Template processing	1.4530	96.4733	2	0.7265
Template load and register function	0.0002	0.0161	1	0.0002
states
state_id_array	0.0027	0.1799	1	0.0027
state_identifier_array	0.0054	0.3552	2	0.0027
Override
Cache load	0.0016	0.1087	17	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0010	0.0692	3	0.0003
Fetch class attribute name	0.0015	0.1006	4	0.0004
XML
Image XML parsing	0.0012	0.0781	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0007	4	0.0000
General
dbfile	0.0014	0.0911	16	0.0001
String conversion	0.0000	0.0006	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 11 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs