Version-specific migration procedures and tips
Up one level
All content on one page (useful for printing, presentation mode etc.)
- 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
- Plone Tableless theme no longer exists
- 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 Plone 2.1 to 2.5"... something to do!!!
If the site has some group assigned local roles after the migration you MUST lauch the script in CMFPlone/Extension/stripGRUFLocalRolePrefix.py
See http://dev.plone.org/plone/ticket/5817/