Upgrade Cyn.in 2.1 to 3.1.3

Prepare a new version of Cyn.in

Obviously you first need to get the newest version of Cyn.in up and running locally. Following Cynapse’s guide on buildout (link removed) helps you do it without much pain. When you have the environment ready, start up Zope and try if your Cyn.in installation works on a plain Plone instance.

Upgrade Data.fs

When you have confirmed that Cyn.in works it’s time to upgrade the actual data.

• Shutdown Zope and remove everything in var/filestorage/ folder.
• Copy Data.fs from your old Cyn.in installation into var/filestorage/ folder.
• Start Zope.
• Go to http://localhost:8080/<plone_instance_id>/portal_migration and migrate Plone content to the latest Plone version
• Go to http://localhost:8080/<plone_instance_id>/portal_quickinstaller and reinstall ubify.site_policy.

The reinstall will fail at this point. We had to perform the following (ugly) patches for reinstall to work:

• In file src/ubify.policy/ubify/policy/migration/onetimeinstall.py comment out line 114:

- logger.info("Unable to assign collection portlet for smartview : %s" % (item["id"],))
+ # logger.info("Unable to assign collection portlet for smartview : %s" % (item["id"],))
+ pass

• In file eggs/Products.CMFQuickInstallerTool-2.1.7-py2.4.egg/Products/CMFQuickInstallerTool/QuickInstallerTool.py comment out lines 550 and 592:

- msg=str(res)
+ # msg=str(res)

- res += str(r)+'\n'
+ # res += str(r)+'\n'
+ pass

That’s it. After a successful reinstall of ubify.policy we were able to use our old data in a new version of Cyn.in. Only a matter of deploying the new version along with migrated Data.fs to the server and we were able to start using it. Hooray!