Cleaning up
This process wasn’t without manual work, unfortunately. But, it certainly took care of 95% of the pain of copying content across! Here’s an overview of the manual work I had to do:
- Set default pages of folders. This could have probably been carried out by a script but I didn’t write one because I only had a 20 folders to fix. In Plone 2.5, I believe the default view was when you set a page to be called ‘index_html’ (happy for corrections), but AFAIK, there weren’t options to set a certain page as the view.
- Set site settings. This involved going through all control panels to pick and manually port settings, but because of so many changes from Plone 2.5 to 4, there’s probably not an obvious migration path anyway.
- Convert legacy portlets. These settings do get copied across, but you’ll need to go to the ‘Manage portlets’ link on your main homepage and click the ‘Convert’ button. At time of writing (Plone 4.0.2) this migration is actually broken (ticket logged already!) but you can just as easily migrate manually — look in the ZMI properties at the site root for your portlet listings.
- Fix some workflow states. My old site used a non-default workflow, so workflow states needed correcting. Thankfully, I was able to push most content around just using the Types control panel.
And the rest of the actions I did were simply boilerplate for setting up a Plone 4 site (theme installation, etc).
This isn’t the most straightforward path, but it did work and get my content across. Hopefully moving to Plone 5 and above won’t be too much of a problem.
