The question as in the title. In changes for 2.2.3 I found: - Resolved known condition in the Catalog where objects are not guaranteed to be unindexed before indexing happens again. Now objects are guaranteed to be unindexed correctly first. This should resolve all outstanding KeyErrors with Catalog, although currently broken Catalogs will require a reindex to resolve them. Has anyone verified whether this in fact corrects the infamous ZCatalog key errors when one tried to reindex site proxied with Apache? Regards -- http://www.mk.w.pl / Marcin.Kasperski | Dokumentację kodu warto wygenerować: @softax.com.pl | http://www.mk.w.pl/narzedzia/narzedzia_gendoc @bigfoot.com \
Marcin Kasperski wrote:
The question as in the title. In changes for 2.2.3 I found:
- Resolved known condition in the Catalog where objects are not guaranteed to be unindexed before indexing happens again. Now objects are guaranteed to be unindexed correctly first. This should resolve all outstanding KeyErrors with Catalog, although currently broken Catalogs will require a reindex to resolve them.
Has anyone verified whether this in fact corrects the infamous ZCatalog key errors when one tried to reindex site proxied with Apache?
Regards
Zope.org has been updated to 2.2.4 and we're still getting key errors. However, the current suspicion is that one of our products isn't playing nice with the catalog. More information when we get it. Thanks, ethan mindlace fremen Zopatista Community Liason.
It works fine for me. I dont know if that proves anything except I cant find the problem again. -- Andy McKay, Developer. ActiveState. ----- Original Message ----- From: "ethan mindlace fremen" <mindlace@digicool.com> To: "Marcin Kasperski" <Marcin.Kasperski@softax.com.pl> Cc: "Zope List Submission" <zope@zope.org> Sent: Wednesday, November 29, 2000 12:29 PM Subject: Re: [Zope] Does 2.2.4 solve Proxy+ZCatalog bugs?
Marcin Kasperski wrote:
The question as in the title. In changes for 2.2.3 I found:
- Resolved known condition in the Catalog where objects are not guaranteed to be unindexed before indexing happens again. Now objects are guaranteed to be unindexed correctly first. This should resolve all outstanding KeyErrors with Catalog, although currently broken Catalogs will require a reindex to resolve them.
Has anyone verified whether this in fact corrects the infamous ZCatalog key errors when one tried to reindex site proxied with Apache?
Regards
Zope.org has been updated to 2.2.4 and we're still getting key errors. However, the current suspicion is that one of our products isn't playing nice with the catalog. More information when we get it.
Thanks,
ethan mindlace fremen Zopatista Community Liason.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
participants (3)
-
Andy McKay -
ethan mindlace fremen -
Marcin Kasperski