Hi Salman, Because there are changes in content structure and in Magnolia API you have to migrate both.
The content migration can be done using Magnolia Packager which is part of Magnolia Enterprise Edition. If you do not have Magnolia EE, you can dig the Magnolia sources, identify the changes and write a converter or buy a Packager migration license for EUR 58 at http://mgnl.org where you can find some hints on the template migration as well. Ralf -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 15. November 2006 10:59 An: [email protected] Betreff: [magnolia-user] Upgrading to 3.0 rc4 from 2.1.5 Dear All, I have asked this before, but there was no reply, would please anybody help with this. I want to preserve all the contents of the site and custom templates which have been developed so far. Cheers, --Salman ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
