Plone Upgrade Guide
Instructions and tips for upgrading to a newer Plone version.
- Introduction
- Preparations
- Upgrading Plone
- Upgrade add-on products
- Troubleshooting
- Version-specific migration procedures and tips
- General advice for upgrading pre-2.5 releases to the latest release
- Upgrading from Plone 1.0 to 2.0
- Upgrading from Plone 2.0 to 2.1
- Upgrading from Plone 2.1 to 2.5
- Upgrading Plone 2.5 to 3.0
- Upgrading a Plone 2.5 site to 3.0
- Updating add-on products for Plone 3.0
- General product development and migration tips for Plone 3.0
- CMFCore.permissions import syntax change
- Transaction module is no longer implicitly in Archetypes
- get_transaction module rename
- ContentFactoryMetadata deprecation
- Update your workflows to use GenericSetup profiles
- Searching users/groups via the Membership tool is deprecated
- Portlets have a new infrastructure
- main_template now uses Zope 3 viewlets
- Plone 3 does not create member folders by default
- Using a tableless layout
- Document Actions now use Zope 3 viewlets
- Products installing workflows may need to add permissions
- Indexes declared in Archetypes schemata need to be moved to GenericSetup
- The "Sharing" tab is now a global action
- Multi page schemas
- Enable inline editing (aka. QuickEdit)
- Updating 2.5.3 to 3.0.3
- Upgrading from 3.x to 3.2
- General advice on updating from a non-buildout to buildout-based installation
All content on one page (useful for printing, presentation mode etc.)
Troubleshooting LinguaPlone
Speaking of LinguaPlone, I came across a bug where when clicking "Manage translations" I got an error about ascii codec not being able to convert a character. This has been fixed in LinguaPlone 2.1 (yet unreleased), which, however, requires Plone 3.1 (unless you are competent at resolving dependencies in Plone Products). I therefore used Plone 3.1-rc1 with LinguaPlone from svn and it works fine.