Product manage_traceback caching old old data?
I've got a product I'm developing, but I'm finding that interactive debugging of it is being foiled by Zope's Product interface's manage_traceback method. It's caching the very first error that occured - and after I shutdown zope and restart it (having fixed the error) it still gives the same traceback. It's possible that the problem is simply the "Products" listing is at fault - it's still showing the product as "broken", even though else where in Zope I can now add products fine. Any ideas? This is with Zope 1.10.2, under ZServer.
ignore me, I'm a doofus. I just realised that I need to delete the broken product from the Control Panel Products list, and then things are happy(er). Anthony
Anthony Baxter wrote I've got a product I'm developing, but I'm finding that interactive debugging of it is being foiled by Zope's Product interface's manage_traceback method.
It's caching the very first error that occured - and after I shutdown zope and restart it (having fixed the error) it still gives the same traceback.
It's possible that the problem is simply the "Products" listing is at fault - it's still showing the product as "broken", even though else where in Zope I can now add products fine.
Any ideas? This is with Zope 1.10.2, under ZServer.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://www.zope.org/mailman/listinfo/zope-dev
(For non-developer, user-level issues, use the companion list, zope@zope.org, http://www.zope.org/mailman/listinfo/zope )
-- Anthony Baxter <anthony@interlink.com.au> It's never to late to have a happy childhood.
participants (1)
-
Anthony Baxter