Oops; I think I sent this reply (initially) only to Christian. I'm
sharing it now with the group. I still don't know what's going on. I
finally got it working (it appears) for us by writing my own evolver
that forced removal of all old Utility Registrations and also forced
removing the Dependencie
Jeff Shell wrote:
> On 11/3/06, Christian Theune <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> what about calling the evolve() scripts from your generation? That would
>> be reasonable IMHO.
>
> I'm trying to do that now. And now it seems that evolve3 (for
> zope.app) is failing because it wants to us
On 11/3/06, Christian Theune <[EMAIL PROTECTED]> wrote:
Hi,
what about calling the evolve() scripts from your generation? That would
be reasonable IMHO.
I'm trying to do that now. And now it seems that evolve3 (for
zope.app) is failing because it wants to use the new Registrations
system to do
Hi,
what about calling the evolve() scripts from your generation? That would
be reasonable IMHO.
Christian
--
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting
I'm working on moving an old customer to our updated CMS. Their
current site is running on Zope 3.1, with our new work being done on
Zope 3.3.
I've gone through their project, removing deprecation warnings, and
watched the code work against a fresh / clean ZODB. But when I moved
one of the old de
