[opencms-dev] upgrade 4.x to 5.0 (was: mail opencms)

[Alexander Kandzior]

Chris,

in case directory translation does not work four your site (it does in
most cases) the "old way" is probably the safest.

* DB-Export from OpenCms in a *.zip 
  Make sure you also have added the /content/bodys folder of 4.6.
* After the export is finished, unzip the export zipfile.
* You will have the exported files and folder structure on 
  your disk now.
* Now do a global search / replace in this files, replacing 
  the old paths with the new ones - for more details on what 
  paths have changed look into the "opencms.properties"
  where the directoy translation rules are defined.
* You can but need not change the entries in the "manifest.xml"
  as the directory translation will do this atutomatically when the
files
  are imported again.
* After you have done a search / replace on your files, you zip 
  them again in the same strucutre as bevor and import them.

Some more tips for rather specialized issues:

* OpenCms 4.x did not correctly specify the encoding of XML files. 
  The 5.0 import will try to correct that automatically. 
  This applies to XML files that start only with 
  <?xml version="1.0"> instead of e.g.
  <?xml version="1.0" encoding="ISO-8859-1"?> (or "UTF-8" or something).
  If your templates do not specify the encoding and the import 
  does not correct that problem for you, you must add this manually.
  Probably best way to do it is with external search & replace as
  described above. Insert "ISO-8859-1" or whatever encoding OpenCms
  5.0 will be installed with for the best performance of templates.
* If you have created modules with the OpenCms module mechanism, 
  these need to be exported - imported with the module mechanism,
  not with the DB export / import as certain configurations from  
  registry.xml are exported with the module mechanism only.
* Also, if you have created modules with the "old" mechaninsm
  (ie. not of type "simple module") these might require special 
  consideration when it comes to the former "language" now 
  "locale" directory.
* If you have created your own Java classes for OpenCms, these
  need to be re-compiled against the 5.0 API. No changes should be
  required, only re-compilation.
* Also, if you have written classes for OpenCms these need now be 
  located in the standard /classes or /lib folders of the web
application,
  not longer in the /occlasses or /oclib folder.

Overall, the directory translation and XML replacement 
should do the trick for most upgrades automatically.

Best Regards,
Alex.

Alexander Kandzior
Alkacon Software - The OpenCms Experts
http://www.alkacon.com




> -----Original Message-----
> From: owner-opencms-dev at www.opencms.org 
> [mailto:owner-opencms-dev at www.opencms.org] On Behalf Of 
> Christoph Kukulies
> Sent: Friday, February 07, 2003 2:46 PM
> To: opencms-dev at opencms.com
> Cc: kuku at accms33.physik.rwth-aachen.de
> Subject: [opencms-dev] mail opencms
> 
> 
> Subject: migrating a site from 4.6 to 5.0 - woes and woes 
> (After repairing a subscription problem - my email had moved 
> and previous posts obviously didn't make it to the list - I'm 
> posting this now a third time, you will see it probably the 
> first time :-)
> 
> Anyway, a colleague who has built a site under 4.06 (a team 
> of co-workers have compiled about 800 pages and files into 
> it) wanted to move everything to 5.0-rc2 and experienced 
> terrible pitfalls.
> 
> What is the correct proceeding in migrating a 4.6 site to 
> 5.0? He imported exported everything from 4.6 and imported into 5.0.
> 
> There were major changes in the path structuring bewteen 4.6 
> and 5.0 he said, but he could get aroung by a aliasing or 
> directory translation scheme that seemed to work, although 
> also there were some glitches resulting in icons not 
> appearing and suddenly being there (after manually correcting 
> the path )
> 
> What now obviously seems the weirdest point to my colleague 
> is that when he is using the Wysiwyg editor under NT there 
> begin to appear <template/> and <edittemplate/> tags.  This 
> seems to be causing a mess between the old bodies and the new 
> ones (which are under system/ now).
> 
> What is the correct way to proceed now?
> 
> Somehow the old 4.6 generates bodies don't play together with 
> the new ones.
> 
> Can anyone help, please?
> 
> 
> --
> Chris Christoph P. U. Kukulies kukulies at rwth-aachen.de
>