How do I upgrade to a newer release of Plone?

I ran the installer, but found I needed to do two things to truly upgrade the older Plone install.

1. run /Applications/Plone2/Tools/upgrade_2.0.5 for each site

2. edit the zope.conf for each site and change::

   %define ZOPE /Applications/Plone2/Library/Software/Zope270/Zope
  
   to::
   
   %define ZOPE /Applications/Plone2/Library/Software/Zope273/Zope

you need to edit the bin/runzope of each Site and set it to Zope273 ... this is only if you are upgrading from one of those older versions that used Zope270

Item 1 above: Does one merely export the Plone instance? Copy out the Data.fs file? Make a complete copy of the \Plone 2 folder structure?
Items 3 & 4: How does this work for the Windows installer? Do you install on top of a current Plone structure or create a fresh one? If a fresh one, what do you need to copy back from your old folder?

Thanks! Dan

Not works for 2.0.x to 2.1. I can not find ANY documentation about migrations from "OLD" Plone 2.0.x to 2.1... I can hardly believe that you that are so proud of your product and don't provide a CLEAR guide "before" the release of 2.1

I don't know even if you are going to read this, but is the least I can do.

Regards

We're just dumb users, not plone/zope experts, who would like to upgrade from 2.0.5 to 2.1. Running on Windows. I can't make much sense out of the generic migration instructions at the top of this thread, and I'm finding numerous user comments (here and elsewhere) about problems with this migration.

Is there a definitive guide to performing this migration someplace and I'm just not finding it? Any help would be appreciated.

-dave

We're just dumb users, not plone/zope experts, who would like to upgrade from 2.0.5 to 2.1. Running on Windows. I can't make much sense out of the generic migration instructions at the top of this thread, and I'm finding numerous user comments (here and elsewhere) about problems with this migration.

Is there a definitive guide to performing this migration someplace and I'm just not finding it? Any help would be appreciated.
-dave

Hi. I'm trying to upgrade to plone 2.1 from 2.0.4, using stock debian packages of both Zope and Plone.

In Debian sarge/stable, Zope 2.6.4 and Plone 2.0.4 go together, coming as standard Debian packages. In order to get Plone 2.1, one must switch to getting Debian's testing packages instead of stable ones. Then one gets the coupling of zope 2.8 and plone 2.1. But the Data.fs from zope 2.6.4 is completely unusable in zope 2.8! When starting the Zope 2.8 instance using the old Data.fs, python pegs the CPU forever (after 2 hours it was still chugging) and zope allows no connections to the ZMI. Normally it would take about 10 seconds to start allowing connections to the ZMI.

To get around this, I tried making a clean Zope 2.8 instance, after first exporting the Plone site as a .zexp file (under the old system), and importing it into 2.8. In this way I was hoping to press this magical "Upgrade" button mentioned above. The import failed! Similarily, importing so much as one html document/page from Plone 2.0.4 (using a .zexp file) also fails, since the internal formatting has changed for documents/pages going from 2.0.4 to 2.1.

So be warned, 2.0.4 -> 2.1 seems like a small change in version of Plone, but it's huge considering the need by many users for a newer version of Zope which can leave you with an unusable Data.fs. If you need to also upgrade Zope in addition to Plone, prepare for a profoundly brutal migration. The instructions above assume you do not need to upgrade Zope, only Plone.

My current approach is to export all html files using the FTP server, then I'll use a couple of python scripts to change all the internal Plone 2.0.4-style headers to be Plone 2.1-compatible, then FTP them back into the new instance.

Attention:
If you get double actions (siteactions, global_tabs, etc.) Relations 0.4b1 may be the reason.
As I removed the actionhandler of relations from portal_action everything was fine (and single ;) ).