User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: it looks for valid keyword even if query is searching for 'substring' i have keywords jignesh jignesh_gandhi i cannot enter 'esh' for searching these two keywords. if i enter 'esh' as a keyword itselves,, the query works fine. this is a bug, where if you are looking at 'substring' in 'keywords' it should not search if keywords exists or not. Reproducible: Always Steps to Reproduce: 1. create keywords jignesh and jignesh_gandhi 2. in the query page search for keywords "case sensitive substring" like "esh" 3. it will give error "invalid keyword esh" 4. create keyword esh 5. now the same search will work Actual Results: keyword search for case sensitive / insensitive substring is screwed up. Expected Results: if we select 'substring' if should not 'check' if that 'substring' exists as a keyword.
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
joel, any idea? This bug has version 2.12. Is this bug still valid?
I can reproduce using 2.21.1+
This works for me, at least on trunk (which will become 4.2) thanks to some refactoring that I did.