Tracy Reed wrote: > nOn Mon, Oct 27, 2008 at 02:14:58PM +0000, Tim Hicks spake thusly: >> Ack! Sorry, this upgrade/migration business appears to be a bit of a mess. > > Indeed. > >> It also used to be part of Quills. (Not sure if it was actually the >> same code, or just the same module name.) > > Maybe I'm not doing this correctly but how am I ever supposed to be > able to import this blog if none of the modern quills implementations > have SimpleBlog which the object I am importing refers to? My > understanding is that I should be able to install Quills, import my > blog.zexp from my old Plone instance, maybe have to reinstall Quills > to make the migration happen. But right now I'm getting stuck on the > basic pickled object import part. Not sure this has anything at all to > do with the actual migration code in Quills.
Hmm, ok, I see what you mean. I think the migration code has probably only been used on in-place ZODBs. That is, the Quills objects (created under earlier versions of Quills) already exist in the ZODB, but are broken because modules/classes defining those objects are no longer there. We then step through the objects and remove/update the broken objects. I can see that doing a ZODB import of Quills objects would fail in this case as the ZODB would complain about those missing modules/classes. The solution to this latter problem would seem to be to create aliases for the missing code. We already do this for other classes. See at the bottom of <http://dev.plone.org/collective/browser/Products.Quills/trunk/Products/Quills/__init__.py>, for example. Can you try aliasing a dummy class for BloggerAPI (or whatever the problem class(es) are for you) there and then doing the migration? You shouldn't even need anything beyond: class BloggerAPI: pass ... I think. After all, you only need the class so that its instances can be deleted. Looking at the code, just going direct to 1.7 should be fine once you've done the aliasing, btw. >> Can you try going to Quills 1.6 first? > > Would this have anything to do with solving my import problem? > >> If you feel motivated - and it seems like you have some reason :) - then >> you might want to take a look at the migration code in 1.7 and update it >> based on the migration code in 1.5 and 1.6 so that it can handle the >> sort of path you are taking. > > So far I'm not even able to import so migration code isn't a factor. > >> Sorry again, > > No problem, I know this is all beta and unstable software. :) Although > I am really hoping Plone will arrive at some solid and quality blog > software eventually so I don't have to go through this pain on a > regular basis. With as mature as Plone is already I am quite surprised > it doesn't yet exist. Yeah, I agree. We could do with a couple more contributors to get things to a more stable state. Would be glad to have you on board :). Tim _______________________________________________ quills-dev mailing list [email protected] http://lists.etria.com/cgi-bin/mailman/listinfo/quills-dev
