Version-specific migration procedures and tips
Version-specific migration procedures and tips#
In addition to the general procedure described in the previous chapters, the chapters in this part of the documentation provide version-specific procedures and tips. If your migration does not involve a version pair specified here, then you may follow the general procedures alone.
- Upgrading Plone 4.x to 5.0
- Upgrade a custom add-on to Plone 5.0
- Upgrading Plone 5 within 5.x.x series
- Upgrading Plone 5.0 to 5.1
- Upgrade a custom add-on to Plone 5.1
- Upgrading Plone 5.1 to 5.2
- Migrating Plone 5.2 to Python 3
- Migrate a ZODB from Python 2.7 to Python 3
- Database upgrade procedure
- Why do I have to migrate my database?
- How
zodbupdate
solves the problem - Prepare your buildout for migrating the database to Python 3
- Verify the integrity of the database in Python 2
- Migrate database using
zodbupdate
- Test migration
- Troubleshooting
- Eliminating downtime
- Further reading
- Upgrading Plone 5.2 to 6.0
- Removed
portal_quickinstaller
- Dexterity site root
- Volto
- Archetypes
- Some deprecated views have been removed
- No more
temp_folder
ortempstorage
- Changed templates to Bootstrap 5 markup
- Zope 5
- Modernize Plone Classic UI theme (Barceloneta)
- Python
plone.api.relation
- Mockup and resource registry redone
- Relations control panel
- Deprecated Unicode property types
autoinclude
collective.dexteritytextindexer
mergedplone.base
package- Support for modern image scales
- Image pre-scaling
- Responsive image support
- Store image scale info in catalog metadata
- New version of TinyMCE
- Viewlets
- Boolean fields
- Removed
- Upgrade Plone 6.0 to 6.1
- Migrating from Plone Classic UI to Volto