#96 — Migrating Plone 2.5 to 3.0 fails due to CacheSetup

I have a web site with Plone 2.5 and accompanying CacheSetup 1.0. I want to upgrade to Plone 3.0. So I put the Plone 3.0 files in the right spot and add CacheSetup and friends from https://svn.plone.org/[…]/plone-3.0

First question: is that the right bundle to take for use with Plone 3.0? If not, then my remarks below need to be taken with a large grain of salt. :)

Starting the Plone migration gives this error:

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Shared.DC.Scripts.Bindings, line 313, in __call__
  Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
  Module Products.PageTemplates.PageTemplateFile, line 129, in _exec
  Module Products.CacheSetup.patch_cmf, line 74, in PT_pt_render
  Module Products.Archetypes.ClassGen, line 56, in generatedAccessor
  Module Products.Archetypes.Schema, line 233, in __getitem__
KeyError: 'enabled'

So the field 'enabled' was apparently not in the 1.0 schema and Plone/Zope does not know that field yet. Going to the quick installer in hopes of fixing it fails as it gives the same error. I went ahead and fixed it by adding this to CacheSetup/content/cache_tool.py:

    def getEnabled(self):
        self.getField('enabled') or False

With this change I can run the migration from Plone 2.5 to 3.0 and view the quick installer.
I think that change cannot cause any problems, but it is best to report it here anyway.

And: basically the same errors are thrown for activePolicyId and proxyPurgeConfig, which means that reinstalling of CacheSetup fails. I suspect these could be fixed by similar changes.

Have other people tried this migration and come up with better results?

I will be on vacation shortly so any further changes will have to come from someone else. Besides, I hardly know CacheFu and friends so I am surprised I came this far. :)