Many thanks to Nick for a thoughtful reply. As it turned out a PloneCal folder (empty!) was the culprit. I discovered it by exporting each Plone instance from 2.14 and importing into Plone 2.53 in turn, and one of them generated the same '_real' error as the migration attempt had. Then I imported content folders from that one instance, and again got the error on one folder. Then took a guess that PloneCal in that folder was the cause, and after confirming it with yet another import, deleted the folder from Plone 2.14, and a normal migration could proceed. A bit tedious, but it revealed the defective content.
Dan Nick Davis-3 wrote: > > Dan Thomas wrote: >> >> After migration attempt I get the error KeyError: '_real' >> It also appears in the ZMI left-hand column! >> > > To make progress here's some ideas: > > Before attempting portal_migration, make sure nothing is broken in ZMI. > > Are all 3rd-party products in the new site compatible with Plone 2.5.3? > Get the new versions if required, before attempting migration. > > Before attempting portal_migration make sure you don't have "rogue > customisations" floating around. Any customised versions of old versions > of templates,scripts etc can cause problems, so you have to compare > everything you've customised and re-apply customisations where > necessary. This kind of audit is essential when migrating. > > As for "cleaning the Data.fs", well you could first do a catalog clear > and rebuild from ZMI->portal_catalog->Advanced. This wouldn't hurt, and > while it takes a while to run, helps in certain circumstances. > > -- View this message in context: http://www.nabble.com/Problem-upgrading-from-2.14-to-2.53%3A-KeyError%3A-_Real-tf4149114s15482.html#a12011023 Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
