StringIndexOutOfBounds exception in LuceneQueryBuilder#addLocaleTerm when requestedLanguageOnly value is 'false'

[simonp]

Reported by brian.ohare@…:

I'm getting StringIndexOutOfBounds exception in LuceneQueryBuilder#addLocaleTerm when requestedLanguageOnly value is 'false'. Not sure if I've configured the database settings correctly as code seems to check for prefix 'only_' or 'prefer'. Exception occurs in 'prefer' check, so perhaps should be more stringent checking there? This breaks search for me on 2.8.x RC2.

[simonp]

Brian,

Is this on the latest build of RC2? I committed a patch that changed some of this logic yesterday (Dec 11). I'll check it out in the latest build shortly.

Simon

[simonp]

....and so there is no confusion here - the author of the patch was Jesse Eichar (I backported it to 2.8.x RC2) - so feel free to step in Jesse....

[simonp]

Can't reproduce it in the latest RC2 built - checked all the options and they seem to work as I would expect (at least I can see the locale query and language detection stuff doing what I would expect for each option).

[bjohare]

Hi Simon,

Yes its the latest build of RC2. It's not against a clean install of the database though which may be the issue. Is there some sql I can to run to update the multilingual settings?

cheers,

Brian.

[jesseeichar]

The migration scripts should contain the sql you need. Take a look at them.

The migration task only runs if the previous version is 2.6 or earlier so they probably didn't run automatically for you. Take a look at them and manually execute the needed sql.

[bjohare]

Thanks Jesse will try that.