I migrated from 3.3.5 to 4.0.2, but one of my add-on products (FCKEditor) didn't make it. When I attempted to re-index in the Plone 4.0.2 instance, I got the following error:
TransformException: Invalid transform : ITransform is not implemented by Products.FCKeditor.transforms.fck_ruid_to_url.fck_ruid_to_url I'm guessing here, but I think FCKEditor didn't make it because it was not 'extended' for Plone 4x. The 'standard' migration procedure, as described in Updating a custom Plone 3 buildout for Plone 4 — Plone CMS: Open Source Content Management, (http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/buildout-3-4) has a buildout 'extension' step which modified each add-on product. However, the document is so difficult to follow that I ended up using 'General advice on updating from a non-buildout to buildout-based installation — Plone CMS: Open Source Content Management' (http://plone.org/documentation/manual/upgrade-guide/general-advice-on-updating-from-a-non-buildout-to-buildout-based-installation) This procedure does NOT include an 'extension' step - just move Data.fs, re-index, and start up. If anyone has encountered this type of error I would appreciate your advice. Otherwise, I would be grateful if anyone could point out a clearer explanation of the buildout 'extension' procedure. TIA JR On Sun, 2011-01-16 at 11:14 -0600, John Reese wrote: > I have a standalone Plone 3.3.5 site that I need to migrate to > standalone 4.0.1. The current site has few add-on products. I am trying > to follow the Plone.org documentation at: > > http://plone.org/documentation/manual/upgrade-guide/ > > Starting with section, Upgrading Plone 3x to 4x: > > http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0 > > This guide certainly doesn't state what the author thought was obvious. > I'm trying to trace back these assumptions so that I can work with this > document. > > I'm trying to do the upgrade on a test server. I built 3.3.5, put in the > add-ons, and performed the first step of upgrade stated by the > documentation - modification of buildout.cfg inside Plone 3.3.5. (I > think the document is referring to the 3.3.5 buildout.cfg - it's not > clear.) > > The next step has me completely lost. According to the document, I > should now be Updating Add-on Products for Plone 4: Detecting Plone 4. > WAIT! I modified buildout.cfg in 3.3.5 but I haven't run the > bin/buildout command yet! None of the changes have taken effect! Why did > I modify buildout.cfg in the first place? > > And what's this about Plone 4? I haven't installed it yet. (Actually, I > have it on a separate server, but not on the test server.) Should it be > present on my test server as a side-by-side install of Plone? The > document doesn't say. > > And what is this weird statement in Detecting Plone 4: > > Here is an example how to detect Plone 4 during imports. Then > you can use PLONE_VERSION variable for making different code > paths. > > try: > # Plone 4 and higher > import plone.app.upgrade > PLONE_VERSION = 4 > except ImportError: > PLONE_VERSION = 3 > > Looks like a script, but what script? In Plone 3x or 4x? And why am I doing > this instead of preparing the 3x data for export? > > At this point I'm triangulating so many unstated steps that decided to ask > for your help rather than proceed. How do you really upgrade Plone? > > John Reese > _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
