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

Support archive

Low Search not filtering by Low Events

StevenLangbroek 8 Sep 2013 17:37 question, complete

I have a search-form which is working (giving me proper search results based on category, title, playa-relationship), just not filtering on date. The field-code looks like this:

When I enter from 28-09-2013 and to 30-09-2013, it'll still show an event that's set on 26 to 27-09-2013. Do I have something wrong here? The dates show up in the query-string properly and on the search-results page (where I show the form again) the dates get put into the field...

Any thoughts what's going on here?

Replies

  1. Low 8 Sep 2013 17:43

    What's the template debugger output for such a search results page?

  2. StevenLangbroek 8 Sep 2013 17:47

    I think these are the relevant bits:

    (0.104165 / 9.31MB) Low Events: Setting search params {"event_date:date_from":"29-09-2013","event_date:date_to":"30-09-2013"}

  3. Low 8 Sep 2013 17:51

    Is the search form HTML still this: https://gist.github.com/StevenLangbro... ?

  4. StevenLangbroek 8 Sep 2013 17:53

    Oh haha apparently GetSat removed my HTML from the post above. I've updated the gist to reflect the current situation.

  5. StevenLangbroek 8 Sep 2013 17:54

    I'm on Low Search 2.4.0 and Low Events 1.1.5 by the way.

  6. Low 8 Sep 2013 17:54

    And have you read my comment on that Gist?

  7. StevenLangbroek 8 Sep 2013 17:56

    Oh hadn't seen that (clicked Edit without refreshing). I can't filter dates for a specific field? Just globally for low events?

  8. Low 8 Sep 2013 17:59

    Having selected the collection or channel will target the events field enough. Or do you have multiple LE-fields in a single channel?

  9. StevenLangbroek 8 Sep 2013 18:02

    Luckily no, using expiration_date for an aspect that doesn't need to be searched. Thanks for the assist. What confused me was that it was outputting the value properly in the field, it just didn't limit the results.

  10. Low 8 Sep 2013 18:04

    Put an input field with name="hello_world" value="foo" in your LS form, and you'll have the variable {low_search_hello_world} with value "foo" at your disposal. But it doesn't actually do anything. Same with this name="low_search:field_name:param" won't do anything, but will set {low_search:field_name:param} as a variable.

    So it's working now?

  11. StevenLangbroek 8 Sep 2013 18:18

    Ah ok. Maybe that's interesting debug-info to put somewhere in the docs as a sort of side-note, it totally threw me off.

    It's working now, thanks alot!