Multi-level version control for various ver. significance

Previous topic

General

Next topic

Author	Message
Piotrek Karaś	Wednesday 30 April 2008 11:50:52 pm Hi, Has anyone had any experience in implementing multi-level version control for eZ Publish? Basically, what I'm thinking of is a situation, where two (or more), more-or-less independent version tracks are used in order to tell some management actions from the other, and to be able to make decisions based on that distinction. The most "classical" example: edit version vs. key version (edit version being just for content polishing, corrections etc. vs. key version being the "document version", as in "the next official version of the document"). There could be many edit versions between key versions and only key versions will be considered for publication or any other logic for that matter. One think that comes to my mind would be to map current version control as "key version" in the example above, while providing additional "direct edit" interfaces that allow editing of a document version without actually changing the version number... This is not too elegant, though, and I expect trouble ;) If anyone has ever needed something like that for eZ Publish, I'd be greateful if you could share some experiences and solution details. Cheers, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Piotrek Karaś

Wednesday 30 April 2008 11:50:52 pm

Hi,

Has anyone had any experience in implementing multi-level version control for eZ Publish?

Basically, what I'm thinking of is a situation, where two (or more), more-or-less independent version tracks are used in order to tell some management actions from the other, and to be able to make decisions based on that distinction. The most "classical" example: edit version vs. key version (edit version being just for content polishing, corrections etc. vs. key version being the "document version", as in "the next official version of the document"). There could be many edit versions between key versions and only key versions will be considered for publication or any other logic for that matter.

One think that comes to my mind would be to map current version control as "key version" in the example above, while providing additional "direct edit" interfaces that allow editing of a document version without actually changing the version number... This is not too elegant, though, and I expect trouble ;)

If anyone has ever needed something like that for eZ Publish, I'd be greateful if you could share some experiences and solution details.

Cheers,
Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

eZ debug

Timing:	Jan 18 2025 21:18:10
Script start
Timing:	Jan 18 2025 21:18:10
Module start 'layout'
Timing:	Jan 18 2025 21:18:10
Module start 'content'
Timing:	Jan 18 2025 21:18:11
Module end 'content'
Timing:	Jan 18 2025 21:18:11
Script end

Main resources:

Total runtime	0.7720 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0075	589.2969	152.6563
Module start 'layout'	0.0075	0.0040	741.9531	39.5078
Module start 'content'	0.0115	0.7586	781.4609	470.1328
Module end 'content'	0.7701	0.0018	1,251.5938	8.1094
Script end	0.7719		1,259.7031

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4502	16	0.0002
Check MTime	0.0014	0.1789	16	0.0001
Mysql Total
Database connection	0.0006	0.0799	1	0.0006
Mysqli_queries	0.7318	94.7994	46	0.0159
Looping result	0.0004	0.0522	44	0.0000
Template Total	0.7371	95.5	2	0.3685
Template load	0.0022	0.2896	2	0.0011
Template processing	0.7348	95.1884	2	0.3674
Template load and register function	0.0001	0.0165	1	0.0001
states
state_id_array	0.0018	0.2312	1	0.0018
state_identifier_array	0.0016	0.2121	2	0.0008
Override
Cache load	0.0018	0.2327	11	0.0002
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0942	1	0.0007
Fetch class attribute name	0.0006	0.0772	2	0.0003
XML
Image XML parsing	0.0005	0.0586	1	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0005	2	0.0000
General
dbfile	0.0006	0.0840	17	0.0000
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
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	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/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.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: 6

Time used to render debug report: 0.0001 secs