in that case there is no backwards compatibility with the previous versions :-( 
In other words, if magnolia 4.x will come out, you need to buy the commercial 
version otherwise all the work you've done in 3.x and so on! 

George

On Wed, May 24, 2006 at 07:08:23PM +0900, Nicolas Modrzyk wrote:
> Hi George,
> 
> Unless the magnolia people have changed that strategy, yes that's  
> what it means.
> But I think, while using magnolia all through version 2 and version  
> 3, it's a nice way of showing support.
> 
> Regards,
> 
> Nicolas,
> 
> On May 24, 2006, at 7:05 PM, FTP wrote:
> 
> >does this mean that if you have content in 2.1.x, you export the  
> >xml structure, you can't import that xml into a 3.x installation  
> >without the commercial converter?
> >
> >Thanks
> >
> >George
> >
> >On Wed, May 24, 2006 at 08:58:15AM +0900, Nicolas Modrzyk wrote:
> >>Hi Hartmut,
> >>
> >>Sorry to say you can't just activate your content from 2.x to 3.x.
> >>You need the commercial converter for that.
> >>
> >>Or, if you have some time, you can look at the binary structure of
> >>the nodes and write a converter yourself. (This is pretty much what
> >>I've done ...)
> >>
> >>Regards,
> >>
> >>Nicolas,
> >>
> >>
> >>On May 24, 2006, at 1:43 AM, Hartmut Kern wrote:
> >>
> >>>Hey list,
> >>>
> >>>a question about the version 3.0-b1.
> >>>
> >>>I tried to activate content from the 2.1x version to 3.0-b1. Then a
> >>>pop-up inline - window (a javascript window) tells me:
> >>>
> >>>"Can't activate: Message received form subscriber: Repository or
> >>>workspace name not sent, unable to activate"
> >>>
> >>>So, this doesn't work (any suggestions?). I exported the Website
> >>>Content and all I needed from the Configuration part (templates,
> >>>paragraphs, etc.) Now the Website I am working on in the moment
> >>>appears as it should (the layout part). But the content is not
> >>>visible. If I click on Edit, I get the message:
> >>>
> >>>Error
> >>>
> >>>Missing configuration for . Check node /modules/templating/ 
> >>>Paragraphs/
> >>>
> >>>info.magnolia.cms.beans.config.ConfigurationException: Missing
> >>>configuration for . Check node /modules/templating/Paragraphs/
> >>>   at info.magnolia.module.admininterface.DialogMVCServlet.getHandler
> >>>(DialogMVCServlet.java:92)
> >>>   at info.magnolia.cms.servlets.MVCServlet.doPost(MVCServlet.java:96)
> >>>   at info.magnolia.cms.servlets.MVCServlet.doGet(MVCServlet.java:48)
> >>>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
> >>>
> >>>.....
> >>>
> >>>
> >>>What happened there?
> >>>
> >>>I looked a little more in details and I've seen, that there are
> >>>some changes all over the Config - Part. There are missing some
> >>>nodes, the Paragraphs node is written in small caps, etc.
> >>>
> >>>My question:
> >>>Are there changes, producing this error - message, or did I
> >>>exported / imported in a wrong manner. May be you are working on
> >>>this topic.
> >>>How can I migrate content, templates from version 2 to 3?
> >>>
> >>>Thanks
> >>>Hartmut
> >>>
> >>>----------------------------------------------------------------
> >>>for list details see
> >>>http://www.magnolia.info/en/magnolia/developer.html
> >>>----------------------------------------------------------------
> >>
> >>
> >>----------------------------------------------------------------
> >>for list details see
> >>http://www.magnolia.info/en/magnolia/developer.html
> >>----------------------------------------------------------------
> >
> >----------------------------------------------------------------
> >for list details see
> >http://www.magnolia.info/en/magnolia/developer.html
> >----------------------------------------------------------------
> 
> 
> ----------------------------------------------------------------
> for list details see
> http://www.magnolia.info/en/magnolia/developer.html
> ----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to