{\rtf1\ansi\ansicpg1252\fromtext \deff0{\fonttbl
{\f0\fswiss Arial;}
{\f1\fmodern Courier New;}
{\f2\fnil\fcharset2 Symbol;}
{\f3\fmodern\fcharset0 Courier New;}}
{\colortbl\red0\green0\blue0;\red0\green0\blue255;}
\uc1\pard\plain\deftab360 \f0\fs20 I have successfully used Content.addVersion() to add versions to the JCR (which I can see if I do a dump of the version history).\par
\par
However whenever I try to restore to an older version, it simply creates a new version with the same data as the current version (and not with the old version).\par
\par
Anyone had any luck with this?\par
\par
Note - I am attempting to version the Data Module, not the Website.\par
\par
Cheers\par
Kat\par
\par
\par
-----Original Message-----\par
From: [email protected] on behalf of Ralf Hirning\par
Sent: Tue 10/02/2009 20:27\par
To: Magnolia User-List\par
Subject: Re: [magnolia-user] versioning in the data module\par
\par
\par
Hi,\par
\par
Quoting Allan: "This would hopefully make jackrabbit version data \par
content on check-in."\par
\par
This will never happen as JCR supports author based versioning only. \par
Means that you can create versions, checkout versions, etc. But you have \par
to create the versions on your own. Magnolia provides a method\par
Content.addVersion() for that. Content.getVersionHistory() provides \par
access to the available versions.\par
\par
Ralf\par
\par
\par
Katherine Thomson schrieb:\par
> Hi Allan,\par
>\par
> We are looking into this too. Did you get anywhere with it?\par
>\par
> I've successfully added mixin:versionable to our nodeType definition but I'm not sure how to get the onParentVersion to be set correctly. Can you help?\par
>\par
> Cheers\par
> Katherine\par
>\par
> -----Original Message-----\par
> From: [email protected] [mailto:[email protected]] On Behalf Of Allan Boyd\par
> Sent: 06 February 2009 09:26\par
> To: Magnolia User-List\par
> Subject: [magnolia-user] versioning in the data module\par
>\par
> Hi,\par
>\par
> Has anyone tried to make the data module versionable? \par
>\par
> I guess the place to start would be to modify the data type definitions to include mixin:versionable and set required onParentVersion values. This would hopefully make jackrabbit version data content on check-in. If this is correct then I wonder how easy it is to use the version command and dialog used in the website module to access version history and revert previous version etc?\par
>\par
> I would be interested to hear from anyone who has done this kind of thing or has similar thoughts on the subject.\par
>\par
> Thanks,\par
> Allan.\par
>\par
>\par
>\par
>\par
> ----------------------------------------------------------------\par
> For list details see\par
> http://www.magnolia-cms.com/home/community/mailing-lists.html\par
> To unsubscribe, E-mail to: <[email protected]>\par
> ----------------------------------------------------------------\par
>\par
>\par
>\par
> ----------------------------------------------------------------\par
> For list details see\par
> http://www.magnolia-cms.com/home/community/mailing-lists.html\par
> To unsubscribe, E-mail to: <[email protected]>\par
> ----------------------------------------------------------------\par
>\par
>\par
> \par
\par
----------------------------------------------------------------\par
For list details see\par
http://www.magnolia-cms.com/home/community/mailing-lists.html\par
To unsubscribe, E-mail to: <[email protected]>\par
----------------------------------------------------------------\par
\par
\par
}
