Different version of the same object.

Next topic

Author	Message
Quoc Huy Nguyen Dinh	Tuesday 28 September 2010 2:29:17 am Eidos Methode allows one to create multiple versions of the same article: print version, SMS version, web version, email campaign version... for example. This would be interesting that eZ Publish incorporates this feature. Currently a way to accheive this would be to create those versions as if they were language. One could create "print", "sms", "web" as custom languages and then setup a siteaccess for each. But it would be better if eZ have a separate feature for this.
André R.	Tuesday 28 September 2010 7:40:24 am One way this is normally done in eZ Publish is to re use same content to multiple channels without having to maintain several versions. To archive this you'll have to think ahead of course, xml blocks like any content in eZ Publish separates design from content as much as possible so can be used many places. But for sms you might be better of by using a text block and add some javascript to an override of that edit template of the text block to make sure text is bellow 160 charters. So basically several attributes for different channels on the same object, but generally so they can be reused. For instance if you limit the sms text to 140 you can use it on twitter as well, and so on. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Quoc Huy Nguyen Dinh	Tuesday 28 September 2010 7:56:35 am Hi Andre Thanks for your reply. I know you could modify a content class and add one attribute per channel but using a system like the languages of eZ, you could then assign different workflows to each of the channel and assign a different editor to each of the channel editing on the same article.

Author

Message

Tuesday 28 September 2010 2:29:17 am

Eidos Methode allows one to create multiple versions of the same article: print version, SMS version, web version, email campaign version... for example.

This would be interesting that eZ Publish incorporates this feature. Currently a way to accheive this would be to create those versions as if they were language. One could create "print", "sms", "web" as custom languages and then setup a siteaccess for each.

But it would be better if eZ have a separate feature for this.

André R.

Tuesday 28 September 2010 7:40:24 am

One way this is normally done in eZ Publish is to re use same content to multiple channels without having to maintain several versions. To archive this you'll have to think ahead of course, xml blocks like any content in eZ Publish separates design from content as much as possible so can be used many places. But for sms you might be better of by using a text block and add some javascript to an override of that edit template of the text block to make sure text is bellow 160 charters. So basically several attributes for different channels on the same object, but generally so they can be reused. For instance if you limit the sms text to 140 you can use it on twitter as well, and so on.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Quoc Huy Nguyen Dinh

Tuesday 28 September 2010 7:56:35 am

Hi Andre

Thanks for your reply.

I know you could modify a content class and add one attribute per channel but using a system like the languages of eZ, you could then assign different workflows to each of the channel and assign a different editor to each of the channel editing on the same article.

eZ debug

Timing:	Jan 18 2025 03:09:12
Script start
Timing:	Jan 18 2025 03:09:12
Module start 'layout'
Timing:	Jan 18 2025 03:09:12
Module start 'content'
Timing:	Jan 18 2025 03:09:13
Module end 'content'
Timing:	Jan 18 2025 03:09:13
Script end

Main resources:

Total runtime	0.5188 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.0057	589.1641	152.6406
Module start 'layout'	0.0057	0.0035	741.8047	39.4688
Module start 'content'	0.0092	0.5081	781.2734	547.6016
Module end 'content'	0.5173	0.0015	1,328.8750	12.1563
Script end	0.5188		1,341.0313

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.5875	16	0.0002
Check MTime	0.0013	0.2471	16	0.0001
Mysql Total
Database connection	0.0008	0.1509	1	0.0008
Mysqli_queries	0.4693	90.4637	57	0.0082
Looping result	0.0005	0.0933	55	0.0000
Template Total	0.4870	93.9	2	0.2435
Template load	0.0022	0.4219	2	0.0011
Template processing	0.4848	93.4477	2	0.2424
Template load and register function	0.0001	0.0196	1	0.0001
states
state_id_array	0.0013	0.2492	1	0.0013
state_identifier_array	0.0010	0.1974	2	0.0005
Override
Cache load	0.0018	0.3492	15	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.1647	2	0.0004
Fetch class attribute name	0.0011	0.2126	5	0.0002
XML
Image XML parsing	0.0011	0.2172	2	0.0006
class_abstraction
Instantiating content class attribute	0.0000	0.0019	6	0.0000
General
dbfile	0.0020	0.3919	25	0.0001
String conversion	0.0000	0.0017	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
3	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: 11 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs