Document Actions
3.
General procedure
Up one level
When upgrading to a newer release of Plone, it is important to run the content migration procedure, since internal structures in Plone might have changed since the last version. This is the general procedure for upgrading.
Before you start upgrading anything, make sure you have a backup.
The basic manual procedure is detailed below. If you are using the installers, you can skip the part about moving away directories and replacing them with the new ones (step 3-4) - it should be handled by the installer for you.
- Back up your entire Plone directory
- Shut down your Plone server instance
- Remove the Product directories you want to replace (ie. the ones in the package you downloaded)
- Put in the new Product directories
- Start Plone again - your site may be inaccessible until we have performed the next steps - don't panic :)
- Go to http://yoursite/manage (aka. the ZMI) and click
portal_migrations - Make sure you are on the
Upgradetab (in older versions, this tab is calledMigrate) — it will state something like:Instance version: 2.5.3
File system version: 3.1.1 - This means that you have to run the upgrade procedure to be updated to 3.1.1.
- Click the
Upgradebutton.If you want to see what steps the upgrade would go through without making the actual changes, you can check the
Dry Runoption - this will do the exact same steps as a normal upgrade/migration will do, but not write anything to the database. - The site will now be updated, this may take a while, depending on which versions you upgrade from/to. For example, the upgrade from Plone 2.0 to Plone 2.1 involves conversion and re-cataloging of all content in your site, so if you have a big site, this may take a while. Be patient.
For those of you who wonder why we don't do this automatically, the reason is that we don't want to change your data without you knowing it, and you should have the opportunity to back up the data before doing this, etc.
For advanced/enterprise users: It is normally possible to upgrade in-place (at least between minor versions) without any site downtime if you run ZEO and multiple load-balanced instances. See the ZEO documentation for more information if you need this.
