Swatches No Results "We can't find products matching the selection."

[nikonratm]

Choosing a color swatch on the front-end gives a page "We can't find products matching the selection."

I actually have a local install of my current M2 site which works perfectly. The databases are pretty much identical except for the URL and possibly some other small things but I just exported it from the remote site to the local one yesterday. No errors are thrown and when I look in the back-end of the remote site I can filter results by color and they work just fine.

I've tried the obvious stuff, re-indexing, etc. Any other ideas???! Any easy way to go about debugging this?

Running 2.1.3

Thanks!

[nikonratm]

Also, doesnt the fact that the front-end lists shows of the colors as filterable options in the first place mean that it should be 'detecting' that the products have those colors??!

How do I go about figuring out why it still returns no products??

[nikonratm · Accepted solution]

Sigh, seems related to an Elasticsearch plugin I'm using: https://www.wyomind.com/magento2/elastic-search-magento.html

[sherrie]

Glad you were able to find the issue @nikonratm, hope you are able to find a solution that works with your goals here.

[amenkimide]

Can you tell me what was the issue exactly and how you solved it?

Thanks,

Alex

[GiritTech]

---

@nikonratm wrote:

Sigh, seems related to an Elasticsearch plugin I'm using: https://www.wyomind.com/magento2/elastic-search-magento.html

Did you solve it?

[nikonratm]

I ended up going to the module developer for help, they didn’t tell me much about what specifically they changed but their reply said that they modified the file: app/code/Wyomind/Elasticsearch/Model/QueryBuilder

I’m not sure if this was a true bug and perhaps it was fixed in subsequent versions or if it was something specific to my installation. I can do a diff on the file if it would help people

[GiritTech]

---

@nikonratm wrote:
I ended up going to the module developer for help, they didn’t tell me much about what specifically they changed but their reply said that they modified the file: app/code/Wyomind/Elasticsearch/Model/QueryBuilder

I’m not sure if this was a true bug and perhaps it was fixed in subsequent versions or if it was something specific to my installation. I can do a diff on the file if it would help people

---

So after discussing with Wyomind & trying some stuff, the solution (for my case) was to update the extension to the latest version & then set the attribute to be searchable ("Use in search") & then reindexing Elasticsearch.