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

Support archive

Low search, search across multisite not working.

Jacob Nijgh 8 Aug 2017 16:01 problem, active

We enabled the multisite manager in EE to setup a multilanguage website, we have a dutch and english version running. Both have the same channel "job" and corresponding fields setup. And both have a search collection for channel Job setup. The custom fields in the job channel have the setting "included in search" enabled.

We are using a basic ajax script to request a embed which in turn runs the low_search:results. This tag uses the required "site=" param like so: site="siteA|siteB" however i dont get any results from siteB on a specific custom field search like so for example: "embeds/overview_jobportal?search:job_dutch_required=no_dutch". We only recieve results from "siteA" if i only put "siteB" in the site= param we do get results from "siteB" what am i doing wrong?

Thanks,
Jacob

Replies

  1. Low 8 Aug 2017 19:39

    If I understand correctly, you're trying to target 2 different fields (the job_dutch_required field in siteA and siteB) using a single Field Search parameter, is that right? If so, I'm afraid that's not possible at the moment. The Field Search filter can only target a single field, even if the field name matches multiple fields across multiple sites.

    Not 100% sure, but I think that's how the native search:field_name="" parameter works on the channel:entries tag, too. Edit to add: if EE does do this natively, I'll see what I can do to add it in LS, too.

    Low 8 Aug 2017 19:59

    Asked EllisLab and they confirmed that EE does do this natively. It's not a quick fix to add to LS, though.

  2. Jacob Nijgh 9 Aug 2017 09:23

    Bummer, thanks for the quick reply that was indeed the case. So were now thinking to change the field to a category so we can work with it, as a workaround. We also looked at some hooks(trying adding data to the result) but no luck there, any thoughts on possible workarounds?

  3. Low 9 Aug 2017 12:45

    You might be able to work around it by disabling the Field Search filter, so it gets picked up by the native EE tag. If you're not using the Field Search filter elsewhere, that might be an option.