> > I'm guessing the DTML method TestCase is acquired from it, before the
> > namespace
> > is searched for the meta_data, which is a little screwy :-(
>
> Odd, I thought you were reffering to another bug that I fixed, thanks to
> your report :-) hehehe, apparantly that wasn't the actual bug you w
On 1/26/01 11:56 AM, "Chris Withers" <[EMAIL PROTECTED]> wrote:
> Chris Withers wrote:
>>
>> Okay, tracked down what's happening, can't understand why :-(
>
> Some data points before I rush off...
>
> - ZDebug doesn't like 2.3 very much :-S
> - Python Scripts rock ;-)
>
> However, from what Z
On 1/26/01 11:41 AM, "Chris McDonough" <[EMAIL PROTECTED]> wrote:
> I've put the fieldindex bug in the collector.
This is now fixed... It was a bizarre logic problem, but I could reproduce
it easily :-) Thanks for finding this.
Chris
--
| Christopher Petrilli
| [EMAIL PROTECTED]
___
Chris Withers wrote:
>
> Okay, tracked down what's happening, can't understand why :-(
Some data points before I rush off...
- ZDebug doesn't like 2.3 very much :-S
- Python Scripts rock ;-)
However, from what ZDebug did show, it seems that the object the catalog has
found ends up on the top o
This is fixed in CVS. ChrisP works fast. :-)
- Original Message -
From: "Chris Withers" <[EMAIL PROTECTED]>
To: "Chris McDonough" <[EMAIL PROTECTED]>
Sent: Friday, January 26, 2001 11:23 AM
Subject: Re: [Zope-dev] ZCatalog FieldIndex bug in Zope 2
Brian Lloyd wrote:
>
> > PS: Tabular reporting ZSearch Interfaces generated from Catalogs
> > have quite
> > badly b0rKen results forms, in that, for some reason, the search
> > form ends up in
> > a column of the results table, very confusing...
>
> Huh? I cannot reproduce this at all (or even
I've put the fieldindex bug in the collector.
- Original Message -
From: "Chris Withers" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, January 26, 2001 10:38 AM
Subject: [Zope-dev] ZCatalog FieldIndex bug in Zope 2.3.0b3
> Hi,
>
> FieldIndex's don't work
> PS: Tabular reporting ZSearch Interfaces generated from Catalogs
> have quite
> badly b0rKen results forms, in that, for some reason, the search
> form ends up in
> a column of the results table, very confusing...
Huh? I cannot reproduce this at all (or even see how it could
happen, looking