[ZCM] [ZC] 1457/ 5 Resolve "ZCTextIndex: QueryError and ParseError not available for import"

Collector: Zope Bugs, Features, and Patches ... zope-coders-admin at zope.org
Fri Sep 24 21:11:15 EDT 2004


Issue #1457 Update (Resolve) "ZCTextIndex: QueryError and ParseError not available for import"
 Status Resolved, Zope/bug medium
To followup, visit:
  http://zope.org/Collectors/Zope/1457

==============================================================
= Resolve - Entry #5 by chrisw on Sep 24, 2004 9:11 pm

 Status: Accepted => Resolved

This is now fixed in CVS and SVn and will land in 2.7.3 and 2.8.
________________________________________
= Accept - Entry #4 by chrisw on Aug 5, 2004 1:13 pm

 Status: Pending => Accepted

 Supporters added: chrisw

I'll sort this come next bug day.
________________________________________
= Comment - Entry #3 by Caseman on Aug 5, 2004 10:22 am

That looks good to me.
________________________________________
= Comment - Entry #2 by chrisw on Aug 5, 2004 8:11 am

The following works for me, is it the right thing to do?

# Make QueryErrors and ParseError public
ModuleSecurityInfo('Products').declarePublic('ZCTextIndex')
ModuleSecurityInfo('Products.ZCTextIndex').declarePublic('ParseTree')
ModuleSecurityInfo('Products.ZCTextIndex.ParseTree').declarePublic('QueryError')
ModuleSecurityInfo('Products.ZCTextIndex.ParseTree').declarePublic('ParseError')
________________________________________
= Request - Entry #1 by chrisw on Aug 5, 2004 7:37 am

Products.ZCTextIndex.ParseTree.QueryError
Products.ZCTextIndex.ParseTree.ParseError

...neither are importable in "safe" code, so you can't gracefully and safe(w.r.t. conflict errors)ly handle people putting things ZCTextIndex doesn't understand in search boxes.

There should be security assertions that allow these to be imported.
==============================================================



More information about the Zope-Collector-Monitor mailing list