Overriding the pubdate and delayed publication

Next topic

Author	Message
Stephen Paschall	Monday 11 December 2006 12:42:15 pm We'd love to deploy eZPublish as our primary CMS, but we need two things: 1.) As quite a bit of the content we post is archival, we need to be able to easily override the publication date in the administrative interface. 2.) As a news organization, we need to be able to embargo content until a scheduled date and time, and eZ does not appear to have any native support for delayed publication at this time. I'm really surprised eZPub v3 doesn't have ready support for these features, as eZPub 2.x most certainly did. I'm sure versioning makes it quite a bit more complex a problem, but surely it can be done. I'd love to be able to write an extension to solve the problem, but I simply don't know the system well enough to do so yet. Suggestions?
Jeroen Sangers	Tuesday 12 December 2006 2:39:27 am 1. If I understand you correctly, you want to set the publication date on archived objects and I assume that you are importing your current site into eZ Publish. If that is the case, you might want to consider doing an automated import using the API instead of copy/pasting everything in the admin interface. 2. This is very easy to do. First, you will have to add a date/time field to your object for storing the embargo date. Then, define a new workflow of the 'Event/Wait until date' type linked to the new field and modify the 'Content/Publish/Before' trigger to start the deferred publishing workflow.

Author

Message

Monday 11 December 2006 12:42:15 pm

We'd love to deploy eZPublish as our primary CMS, but we need two things:

1.) As quite a bit of the content we post is archival, we need to be able to easily override the publication date in the administrative interface.

2.) As a news organization, we need to be able to embargo content until a scheduled date and time, and eZ does not appear to have any native support for delayed publication at this time.

I'm really surprised eZPub v3 doesn't have ready support for these features, as eZPub 2.x most certainly did. I'm sure versioning makes it quite a bit more complex a problem, but surely it can be done.

I'd love to be able to write an extension to solve the problem, but I simply don't know the system well enough to do so yet.

Suggestions?

Jeroen Sangers

Tuesday 12 December 2006 2:39:27 am

1. If I understand you correctly, you want to set the publication date on archived objects and I assume that you are importing your current site into eZ Publish. If that is the case, you might want to consider doing an automated import using the API instead of copy/pasting everything in the admin interface.

2. This is very easy to do. First, you will have to add a date/time field to your object for storing the embargo date. Then, define a new workflow of the 'Event/Wait until date' type linked to the new field and modify the 'Content/Publish/Before' trigger to start the deferred publishing workflow.

eZ debug

Timing:	Jan 18 2025 11:07:27
Script start
Timing:	Jan 18 2025 11:07:27
Module start 'layout'
Timing:	Jan 18 2025 11:07:27
Module start 'content'
Timing:	Jan 18 2025 11:07:28
Module end 'content'
Timing:	Jan 18 2025 11:07:28
Script end

Main resources:

Total runtime	0.4739 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0063	589.1641	152.6406
Module start 'layout'	0.0063	0.0034	741.8047	39.4766
Module start 'content'	0.0097	0.4625	781.2813	491.8750
Module end 'content'	0.4723	0.0016	1,273.1563	8.1250
Script end	0.4738		1,281.2813

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.7441	16	0.0002
Check MTime	0.0015	0.3183	16	0.0001
Mysql Total
Database connection	0.0009	0.1901	1	0.0009
Mysqli_queries	0.4269	90.0805	54	0.0079
Looping result	0.0005	0.1076	52	0.0000
Template Total	0.4344	91.7	2	0.2172
Template load	0.0027	0.5789	2	0.0014
Template processing	0.4317	91.0931	2	0.2158
Template load and register function	0.0002	0.0395	1	0.0002
states
state_id_array	0.0014	0.2970	1	0.0014
state_identifier_array	0.0008	0.1712	2	0.0004
Override
Cache load	0.0023	0.4825	13	0.0002
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1674	2	0.0004
Fetch class attribute name	0.0014	0.3003	3	0.0005
XML
Image XML parsing	0.0006	0.1262	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0017	3	0.0000
General
dbfile	0.0009	0.1800	16	0.0001
String conversion	0.0000	0.0015	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	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: 7 Number of unique templates used: 5

Time used to render debug report: 0.0003 secs