Publish on date?

Next topic

Author	Message
Marco Zinn	Saturday 20 November 2004 5:16:59 am Hi, in ez2, you could publish/unpublish articles by date. I'm looking for a way to _publish_ articles, based on a date. This will be an "online christmas calender", where we want to publish one article each day at midnight ;) Last year, this was done in ez2 and worked fine. Is there a way to do this in ez 3.4? The only things, that i found, were "publish/unpublish" triggers in the workflow section (won't help me) and the "unpublish" workflow, which may be a base code for creating a publish cronjob. The "not yet published" articles could be drafts, which will be published at one (common) partent folder, or they may be published at some other (not accessible) node and moved to the "public" node. Any comment is welcome, as 01.12 is coming near ;) Marco http://www.hyperroad-design.com
Bruce Morrison	Saturday 20 November 2004 11:46:15 pm Seems to be a embargo (publish on date) feature http://ez.no/community/forum/general/is_there_a_publish_to_date_function And an unpublish feature http://ez.no/community/forum/general/unpublish_event_in_ez_3_3_missing You would just have to run the cronjon at midnight Hope this helps Cheers Bruce My Blog: http://www.stuffandcontent.com/ Follow me on twitter: http://twitter.com/brucemorrison Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
Marco Zinn	Sunday 21 November 2004 12:58:50 pm Thanks, Bruce. The first link helped me to get it working. Btw, you can run your cronjob every hour, as the "wait until date" event seems to work perfectly, even with "datetime" attributes. So, you can have articles publish at almost any time, as long as your cronjob is called frequently enough ;) Marco http://www.hyperroad-design.com

Author

Message

Saturday 20 November 2004 5:16:59 am

Hi,
in ez2, you could publish/unpublish articles by date.
I'm looking for a way to _publish_ articles, based on a date. This will be an "online christmas calender", where we want to publish one article each day at midnight ;) Last year, this was done in ez2 and worked fine.

Is there a way to do this in ez 3.4? The only things, that i found, were "publish/unpublish" triggers in the workflow section (won't help me) and the "unpublish" workflow, which may be a base code for creating a publish cronjob.

The "not yet published" articles could be drafts, which will be published at one (common) partent folder, or they may be published at some other (not accessible) node and moved to the "public" node.

Any comment is welcome, as 01.12 is coming near ;)

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

Bruce Morrison

Saturday 20 November 2004 11:46:15 pm

Seems to be a embargo (publish on date) feature
http://ez.no/community/forum/general/is_there_a_publish_to_date_function

And an unpublish feature
http://ez.no/community/forum/general/unpublish_event_in_ez_3_3_missing

You would just have to run the cronjon at midnight

Hope this helps
Cheers
Bruce

My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish

Marco Zinn

Sunday 21 November 2004 12:58:50 pm

Thanks, Bruce. The first link helped me to get it working.
Btw, you can run your cronjob every hour, as the "wait until date" event seems to work perfectly, even with "datetime" attributes.
So, you can have articles publish at almost any time, as long as your cronjob is called frequently enough ;)

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

eZ debug

Timing:	Jan 18 2025 19:05:32
Script start
Timing:	Jan 18 2025 19:05:32
Module start 'layout'
Timing:	Jan 18 2025 19:05:32
Module start 'content'
Timing:	Jan 18 2025 19:05:33
Module end 'content'
Timing:	Jan 18 2025 19:05:33
Script end

Main resources:

Total runtime	0.5810 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	588.9141	152.6094
Module start 'layout'	0.0065	0.0055	741.5234	39.3984
Module start 'content'	0.0120	0.5671	780.9219	547.2344
Module end 'content'	0.5791	0.0018	1,328.1563	12.1953
Script end	0.5809		1,340.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.5926	16	0.0002
Check MTime	0.0016	0.2740	16	0.0001
Mysql Total
Database connection	0.0013	0.2243	1	0.0013
Mysqli_queries	0.5237	90.1426	57	0.0092
Looping result	0.0016	0.2809	55	0.0000
Template Total	0.5258	90.5	2	0.2629
Template load	0.0024	0.4057	2	0.0012
Template processing	0.5235	90.1001	2	0.2617
Template load and register function	0.0001	0.0210	1	0.0001
states
state_id_array	0.0030	0.5207	1	0.0030
state_identifier_array	0.0010	0.1721	2	0.0005
Override
Cache load	0.0020	0.3455	25	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1270	2	0.0004
Fetch class attribute name	0.0012	0.2038	5	0.0002
XML
Image XML parsing	0.0011	0.1929	2	0.0006
class_abstraction
Instantiating content class attribute	0.0000	0.0021	6	0.0000
General
dbfile	0.0021	0.3605	22	0.0001
String conversion	0.0000	0.0018	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/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 18 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs