RE: [fw-formats] Unitialized string offset

Hi George,

The problem is not in the DictionaryLoader. It's in the SegmentWriter
(http://framework.zend.com/issues/browse/ZF-4365).

It's already fixed for ZF 1.6.2, but you have to rebuild your indices.
(Adding new documents with a followed index optimization also solves
problem).

With best regards,
Alexander Veremyev.

> -----Original Message-----
> From: gherson [mailto:gherson@snet.net]
> Sent: Saturday, November 01, 2008 12:04 AM
> To: fw-formats@lists.zend.com
> Subject: Re: [fw-formats] Unitialized string offset
>
>
>
> gherson wrote:
> >
> > What should my error_reporting() be set to when using ZSL? E_ERROR?
> >
> Yes. Avoid "Uninitialized string offset: 389 on line 116 in file
>
C:\xampplite\php\zf\Zend\Search\Lucene\Index\DictionaryLoader.php"-type
> (search-stopping) errors in Zend Framework 1.6 by either
> 1. Adding
> $pos = min(strlen($data)-1, $pos); // new
> above all instances of
> $nbyte = ord($data[$pos++]);
> in Zend\Search\Lucene\Index\DictionaryLoader.php (Zend: do this
please)
>
> or
>
> 2. Quash E_NOTICE errors:
> error_reporting(E_ALL ^ E_NOTICE);
>
> fyi,
> George
>
> --
> View this message in context:
http://www.nabble.com/Unitialized-string-
> offset-tp19414579p20273990.html
> Sent from the Zend MFS mailing list archive at Nabble.com.