|
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
|
