* 2007-02-23 11:15, wrote: > hi, Hi! > In the next 4 hours I repeatedly tried to use the migration tool of Plone > to update my Plone site. It turned out that the new version of > exUserFolder 0.50 is completely different , so I removed from the > instance and manually put my old (patched) 0.20 into it ; and it turns > out that I18NLayer is incompatible with Plone 2.5 (so I deleted all my > I18NLayer files from the instance - of course, this is unacceptable for a > "real" upgrade, but at a certain point I was also curious to see if I > could ever get to a working instance!). These are all problems related to upstream upgrade paths and there is nothing which we (as Debian Zope Team) could do. From my experience, upgrade paths in Plone 2.0 -> 2.5 are quite painful as a lot of background code changed. > --- my failed "semi upgrade" > > I created another instance w/o Etch products > # dzhandle -z 2.9 make-instance -m manual dida_oldplone > I copied all my data and personal products ; and I also > copied all Plone 2.0 products from Sarge into > /var/var/lib/zope2.9/instance/dida_oldplone/Products > So my goal was to just upgrade zope2.7 -> zope2.9 , > and be able to run my portal in Etch (and leave > the Plone update to a later moment). > It failed in a worse way: when I try to access any > folder in management mode , I get > 2007-02-23T09:50:50 ERROR Zope.SiteErrorLog http://localhost:9673/Control_Panel/Products/manage_main > Traceback (innermost last): > Module ZPublisher.Publish, line 115, in publish > Module ZPublisher.mapply, line 88, in mapply > Module ZPublisher.Publish, line 41, in call_object > Module Shared.DC.Scripts.Bindings, line 311, in __call__ > Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec > Module App.special_dtml, line 176, in _exec > Module DocumentTemplate.DT_Let, line 76, in render > Module DocumentTemplate.DT_Util, line 196, in eval > - __traceback_info__: REQUEST > Module <string>, line 0, in ? > NameError: name 'getDefaultSorting' is not defined Same as before, with a note that this is a known problem: try to remove ExternalEditor from your products folder, it should fix the portal. Cheers, -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _____________________________________________________________________ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
Attachment:
signature.asc
Description: Digital signature