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

Support archive

loose_ends not working

Philip Prinz 5 Mar 2013 20:41 problem, complete

Hi,

I am trying to get the loose ends working. But somehow it does not work.
I set it to loose_ends="yes".
When I search for historic I should get results with historical, right? But that does not work. Are there conditions for loose ends to work properly?

I am on Low Search 2.2.1 and EE 2.5.2

Thanks

Replies

  1. Low 5 Mar 2013 21:02

    It should work like that, yes. If you search for 'historical', do you get the entry?

  2. Philip Prinz 5 Mar 2013 21:07

    Yes when searching for "historical" I get a lot of entries. But I get none of them when searching for "historic".

  3. Low 5 Mar 2013 21:11

    Okay, what does your form tag look like? Also, can you turn on the output profiler and look up the SQL query when you search for 'historic'? It will contain a MATCH ... AGAINST statement.

  4. Philip Prinz 5 Mar 2013 21:16

    This is the query:

    SELECT entry_id, collection_id, MATCH(index_text) AGAINST('historic') AS score
    FROM ('exp_low_search_indexes')
    WHERE 'collection_id' IN ('1')
    AND 'site_id' IN (1)
    AND MATCH(index_text) AGAINST('"historic"' IN BOOLEAN MODE)
    ORDER BY 'score' desc

    And this my form tag:
    {exp:low_search:form collection="projects_collection" search_mode="all" loose_ends="yes" result_page="explore/search"}

  5. Low 5 Mar 2013 21:22

    can you also post the encoded query string from the URI?

  6. Philip Prinz 5 Mar 2013 21:24

    Here it is:

    eyJyZXN1bHRfcGFnZSI6ImV4cGxvcmVcL3NlYXJjaCIsImNvbGxlY3Rpb24iOiJwcm9qZWN0c19jb2xsZWN0aW9uIiwic2VhcmNoX21vZGUiOiJhbGwiLCJsb29zZV9lbmRzIjoieWVzIiwia2V5d29yZHMiOiJoaXN0b3JpYyJ9

  7. Low 5 Mar 2013 21:26

    Aaand your opening Results tag?

  8. Philip Prinz 5 Mar 2013 21:31

    Ha! Got it.
    There was search_mode="exact" in the opening results tag.
    I am sorry. I should have found that on my own!

    Thanks for you help.

  9. Low 5 Mar 2013 21:31

    That's what I thought. :) Glad it's fixed now.