Upgrading and Moving
Moving
- Migrate collections with custom criteria from plone 2.5 to plone 3.x
- Archetypes with fully functioning indices in 2.5 can not be migrated automatically to plone 3.x without losing this attribute. Thus, Smart Folders in 2.5 using the custom criteria from an archetype will loose their functionality after the migration to plone 3.x. This How-To shows how to - manually - repair this.
- Migrate Custom AT Types with Products.contentmigration
- How to migrate the custom archetype types that you have created using Products.contentmigration. Appropriate for changing field names, package names, or types from one to another.
Upgrading
- Cleaning p4a from your instance
- Fixing Workflow States (a real-life example)
- When workflows get confused, content items get reset to the default state. If you have a backup or a QA server, you can restore the correct workflow states.
- How to force all your old content into the new 'normalized-id-format'
- Sometimes, when you migrate an old website, you might want to forcefully rename your old objects
- Migrate collections with custom criteria from plone 2.5 to plone 3.x
- Archetypes with fully functioning indices in 2.5 can not be migrated automatically to plone 3.x without losing this attribute. Thus, Smart Folders in 2.5 using the custom criteria from an archetype will loose their functionality after the migration to plone 3.x. This How-To shows how to - manually - repair this.
Get Help