bug in Zope 2.11.2 and Silva support for 2.11.3

Andy Altepeter <[email protected]> Thu, 23 Jul 2009 21:56:03 -0500
Newsgroups gmane.comp.web.zope.silva.devel
Message-ID <[email protected]>
So after upgrading to Silva 2.1 last week we had an issue with any Zope 
DateTime object that was in the database prior to the upgrade.  This issue 
was resolved in Zope 2.11.3.  We promptly updated our buildout and redeployed 
into production.

Little did we know that Zope 2.11.3 breaks ParsedXML and XMLWidgets in some 
very fundamental and significant ways.  I don't have any tracebacks at this 
time, but the errors seemed to indicate with certain core features of 
ParsedXML documents, working with the DOM and accessing node.childNodes in 
particular, now creates non acquisition-wrapped objects, or improperly 
acquisition-wrapped objects.  

The two big errors we say were AttributeError: 'getAttribute' (a node with 
does not have the getAttribute method), and excessive recursion errors when 
computing the absolute url of a node or ParsedXML document.

I updated the base.cfg profiles in both the Silva 2.1 and trunk buildouts to 
use Zope 2.11.3.  This should be reverted, but I wanted to give you the 
opportunity to try it for yourself before I do.  

The excessive recursion errors happen when you try to access the forms-based 
editor. (just clicking the "Forms editor..." link is sufficient to raise the 
error)

Our compromise was to revert back to 2.11.2 and copy the lib/python/DateTime 
directory from the 2.11.3 build into the zope2 (2.11.2) part.

Any ideas?  I spent many hours troubleshooting this with WingIDE's debugger 
already, but this one is beyond me.

Regards,
Andy