Cataloging/ignoring objects that generate errors on indexing
Hello, I'm trying to update my catalog, and much to my surprise, it ain't working ! Some objects require form parameters and so on, raise errors when none are provided. So now when I ask the catalog (In this case a CMF one, but the fact it's CMF shouldn't really matter, right?) to index everything it can find, it raises an error when it lands on such objects. Now this has never happened ot me before, and I'd always assumed that objects that raised errors while being index simply didn't get indexed, hence my suprise. I was actually counting on such doucments NOT getting indexed BECAUSE they raise errors. Admitedly, I'm doing something somewhat out of the ordinary. I have a CMF Document that actually renders/interprets TAL (Basically a CMF Document ZPT). SearchableText() runs a CookedBody that does the ZPT rendering ... Of course NOT using CookedBody at indexing might be an option, but I'm not sure of the consequences ... Some documents that have simple tal:replace/tal:content type instructions in them I DO want to have Cooked before indexing ... Anybody have any good ways or suggestions on how to get around this ? Any help would be much appreciated! Thanks, Jean-François Doyon Internet Service Development and Systems Support GeoAccess Division Canadian Center for Remote Sensing Natural Resources Canada http://atlas.gc.ca Phone: (613) 992-4902 Fax: (613) 947-2410
Can you supply a traceback? I've always been under the same impression as you.... On Fri, 2003-09-26 at 12:15, Jean-Francois.Doyon@CCRS.NRCan.gc.ca wrote:
Hello,
I'm trying to update my catalog, and much to my surprise, it ain't working !
Some objects require form parameters and so on, raise errors when none are provided. So now when I ask the catalog (In this case a CMF one, but the fact it's CMF shouldn't really matter, right?) to index everything it can find, it raises an error when it lands on such objects.
Now this has never happened ot me before, and I'd always assumed that objects that raised errors while being index simply didn't get indexed, hence my suprise. I was actually counting on such doucments NOT getting indexed BECAUSE they raise errors.
Admitedly, I'm doing something somewhat out of the ordinary. I have a CMF Document that actually renders/interprets TAL (Basically a CMF Document ZPT). SearchableText() runs a CookedBody that does the ZPT rendering ... Of course NOT using CookedBody at indexing might be an option, but I'm not sure of the consequences ... Some documents that have simple tal:replace/tal:content type instructions in them I DO want to have Cooked before indexing ...
Anybody have any good ways or suggestions on how to get around this ?
Any help would be much appreciated!
Thanks,
Jean-François Doyon Internet Service Development and Systems Support GeoAccess Division Canadian Center for Remote Sensing Natural Resources Canada http://atlas.gc.ca Phone: (613) 992-4902 Fax: (613) 947-2410
_______________________________________________ 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 ) -- Chris McDonough <chrism@zope.com> Zope Corporation
Jean-Francois.Doyon@CCRS.NRCan.gc.ca wrote at 2003-9-26 12:15 -0400:
... Some objects require form parameters and so on, raise errors when none are provided. So now when I ask the catalog (In this case a CMF one, but the fact it's CMF shouldn't really matter, right?) to index everything it can find, it raises an error when it lands on such objects.
Chris already requested the traceback. It will tell you where the exception has been raised and based on that you (or we) can determine what happens. I would like to mention my "ManagableIndex" which gives you far reaching control over how objects are indexed. <http://www.dieter.handshake.de/pyprojects/zope> Dieter
participants (3)
-
Chris McDonough -
Dieter Maurer -
Jean-Francois.Doyon＠CCRS.NRCan.gc.ca