All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

Ignore Words not working?

MattV 30 Oct 2012 20:31 problem, complete

This is my first time using Low Search. I've got 2.1.0 installed. And the Stop Words and Ignore Words don't seem to be working as I expect. (It's quite possible that I've misunderstood how they are supposed to work.)

If I search for something like The Board of Advisors using either the "any" or "all" search modes, the search results highlight the word "the" (but not "of"). It continues to do this, even after I've added "the" and "of" to the Ignore Words list in the extension settings.

Am I right in thinking that this isn't the proper behavior? Or do I misunderstand how this is all supposed to work?

Replies

  1. Low 30 Oct 2012 20:44

    The Stop Words are only there to trigger a fallback search method in MySQL. Only if you can alter them in MySQL itself, you can change them in the add-on settings. Best leave those to the default if you cannot.

    The Ignore Words defined are filtered out of the search terms as though they were never entered. They shouldn't be highlighted in the search results. If they are, then I'll need to investigate further. It's a fairly new feature in Low Search, so a bug is possible.

  2. MattV 30 Oct 2012 20:49

    Thanks for the quick reply!

    I haven't touched the Stop Words, so I'll continue to leave those alone.

    I think I figured out what's going on. It appears that the Ignore Words are case-sensitive. The trigger was that I capitalized "The" in my initial search. When I search for The Board Of Advisors, it highlights both "the" and "of" (both capitalized and lowercase). When I search for the Board of Advisors, it works as expected, highlighting neither.

    I tried adding both "The" and "the" to the Ignore Words list, but it filtered out the capitalized version.

  3. Low 30 Oct 2012 21:00

    Ah right. Looks like filtering the ignore words from the keywords for highlighting is indeed case sensitive. That'll be a small bug and I'll get that fixed.

  4. MattV 30 Oct 2012 21:17

    Excellent! I appreciate the quick responses.

  5. Low 5 Nov 2012 15:56

    Should be fixed in v2.1.1