[Zope] TextIndexNG QueryParser Difficulties

[Andreas Jung]

As a workaround you should try the following:

TextIndexNG.py around line 840:

replace self._v_catalog = self.getPhysicalRoot().....
with

  self._v_catalog = getattr(self, self.catalog_path)

This should work in case when caller.getPhysicalPath() returns
a wrong result. In this case be use acquisition instead of
traversal to get the catalog instance.

-aj

--On Donnerstag, 17. April 2003 18:20 Uhr +0200 Oliver Bleutgen 
<myzope@gmx.net> wrote:

> Andreas Jung wrote:
>> This problem *should* be fixed in 1.09. But you need to recreate the
>> index. Btw. this problem is only of cosmetic nature since the core
>> functionality remains untouched.
>> This method is for testing purposes only.
>
> Just FYI, I have installed TextIndexNG (which is very nice) in a
> basically clean zope and have exactly the same problem. The only
> "speciality" is that this is in a PortalCatalog, not a ZCatalog.
>
> The error occurs in this line:
> self._v_catalog =
> self.getPhysicalRoot().unrestrictedTraverse(self.catalog_path)
>
> and an external method returning
> Indexes['content_ng'].catalog_path for an textindexNG
>
> gives me just
> 'portal_catalog', which is obviously not the real physical path to the
> catalog.
>
>
> HTH,
> oliver
>
>
>
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )