On Sun, Nov 02, 2008 at 02:01:12PM +0000, Tim Hicks spake thusly: > 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
Should I just have to add a line to Products/Quills/__init__.py like this:
sys.modules['Products.Quills.BloggerAPI'] = BloggerAPI
and then provide implementation of it with only pass in the body in
this directory:
Products/Quills/deprecated
?
I will give that a try....
Ok, I started this email a couple days ago and have had it sitting
around waiting to be finished... Now I've had a chance to play with
this some more. So I did the above and also added a BloggerAPI.py in
the Quills/deprecated directory containing the empty BloggerAPI class
definition as you described above. I got this error when importing it
in the ZMI:
AttributeError: class BloggerAPI has no attribute '__new__'
So I coded up a
def __new__(self):
pass
method in my BloggerAPI class but then I got:
TypeError: unbound method __new__() must be called with BloggerAPI
instance as first argument (got classobj instance instead)
So I googled for what __new_ is supposed to do since it looks like a
private method and sure enough it's normally inherited from object and
should already be there but isn't for some reason. So I pondered this
for a while and decided to try making BloggerAPI.py such that it would
inherit from something which would get it the attributes it needed so
I looked around and chose SimpleItem rather arbitrarily:
from OFS.SimpleItem import SimpleItem
class BloggerAPI(SimpleItem):
pass
and voila! It successfully imported! Then I uninstalled and
reinstalled Quills-1.7.0b2 and it successfully migrated! At last!
So now I'm working on migrating the rest of my content (trivial
webpages, images, etc.) and will soon have everything working on the
new server. Thanks for your help!
> 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 :).
I am really trying hard to become a plone developer and have read
"Definitive Guide to Plone" (didn't get much out of it, mostly way
over my head) and I'm working on Professional Plone Development (in
fact I'm quite lost already, need to start over) and I just signed up
to be notifed when "Practical Plone" comes out. Hopefully that is more
my speed. But I've been working on this for the last 4 years or so and
I'm still a noob so I wouldn't hope for too much from me. I'm slowly
but surely making baby steps forward so who knows... I do have a
number of projects (paying projects, even) waiting for me to get up to
speed on plone. It seems that there is plenty of demand for plone web
apps.
As far as I can tell the basic functionality of Quills works just
fine. What sorts of new things are you really working on implementing
or improving? A major source of confusion for me is that there are so
many different versions of Quills out there and they are all labeled
beta or unreleased. I was recently told to check out the scrawl blog
product but it isn't clear to me that it will be any better than
Quills and I really need to get better at coding for Plone before I
could ever migrate to something else anyway as I would have to write
my own Quills->something else migration script. As far as I can tell
Quills is still the leading and most functional blog so I'll be
sticking with it for a while.
--
Tracy Reed
http://tracyreed.org
pgpxIDLJOcONa.pgp
Description: PGP signature
_______________________________________________ quills-dev mailing list [email protected] http://lists.etria.com/cgi-bin/mailman/listinfo/quills-dev
