How to schedule updates to content (homepage)

Next topic

Author	Message
Ciaran McGrath	Wednesday 17 October 2007 3:18:51 am Hi, I've searched and searched this site and the web in general but can't seem to find any info on how we can make changes to our homepage on a scheduled basis. Our site changes several times a day 7 days a week and we would like to be able to stack up the updates to the homepage so they run automatically over the weekend or when people are out of the office. I've seen a couple of extensions to do this but with such limited documentation I'm reluctant to install them on a production site. Is this functionality built into Ez anywhere?
Matthew Carroll	Wednesday 17 October 2007 9:28:58 pm It's built in functionality. You need to create a publishing workflow using "wait until date". http://ez.no/doc/ez_publish/technical_manual/3_10/reference/workflow_events/wait_until_date Good luck Matthew http://carroll.org.uk
Ciaran McGrath	Thursday 18 October 2007 4:08:43 am Hi Matthew, Thanks for your reply. Would I be right in saying this works only for one content change? i.e. we couldn't queue up a number of updates to our homepage and have them publish when appropriate. For example our editors usually stack up the saturday and sunday articles on a friday evening and they automatically appear on the homepage when published. Regards Ciaran.

Author

Message

Wednesday 17 October 2007 3:18:51 am

Hi,

I've searched and searched this site and the web in general but can't seem to find any info on how we can make changes to our homepage on a scheduled basis.

Our site changes several times a day 7 days a week and we would like to be able to stack up the updates to the homepage so they run automatically over the weekend or when people are out of the office.

I've seen a couple of extensions to do this but with such limited documentation I'm reluctant to install them on a production site.

Is this functionality built into Ez anywhere?

Matthew Carroll

Wednesday 17 October 2007 9:28:58 pm

It's built in functionality. You need to create a publishing workflow using "wait until date".

http://ez.no/doc/ez_publish/technical_manual/3_10/reference/workflow_events/wait_until_date

Good luck
Matthew

http://carroll.org.uk

Ciaran McGrath

Thursday 18 October 2007 4:08:43 am

Hi Matthew,

Thanks for your reply.

Would I be right in saying this works only for one content change?

i.e. we couldn't queue up a number of updates to our homepage and have them publish when appropriate. For example our editors usually stack up the saturday and sunday articles on a friday evening and they automatically appear on the homepage when published.

Regards
Ciaran.

eZ debug

Timing:	Jan 31 2025 01:24:25
Script start
Timing:	Jan 31 2025 01:24:25
Module start 'layout'
Timing:	Jan 31 2025 01:24:25
Module start 'content'
Timing:	Jan 31 2025 01:24:25
Module end 'content'
Timing:	Jan 31 2025 01:24:25
Script end

Main resources:

Total runtime	0.0234 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	588.2578	151.2266
Module start 'layout'	0.0055	0.0038	739.4844	220.7188
Module start 'content'	0.0092	0.0128	960.2031	997.8047
Module end 'content'	0.0220	0.0014	1,958.0078	29.9922
Script end	0.0234		1,988.0000

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	11.7140	14	0.0002
Check MTime	0.0011	4.7730	14	0.0001
Mysql Total
Database connection	0.0008	3.5701	1	0.0008
Mysqli_queries	0.0023	9.9325	3	0.0008
Looping result	0.0000	0.0559	1	0.0000
Template Total	0.0010	4.4	1	0.0010
Template load	0.0008	3.4501	1	0.0008
Template processing	0.0002	0.8877	1	0.0002
Override
Cache load	0.0006	2.4862	1	0.0006
General
dbfile	0.0017	7.4514	8	0.0002
String conversion	0.0000	0.0305	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs