[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33639

You should see a “WPSOLR queries” menu in Query monitor, showing your search engine queries.

If not, please check Query Monitor add-on

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33601

The WPSOLR query is missing.

[wpsolr]

3 years, 4 months ago in reply to: Vespa Integration? #33549

The integration is 95% done, but a few issues remain that need to be fixed by the Vespa team.

You can check the showstoppers on the roadmap: https://github.com/vespa-engine/vespa/issues/26694

What would be your use case that would require Vespa over Weaviate for instance?

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33507

What does look like the query? You can spy it with the Query Monitor add-on.

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33446

Here is our demo with WPSOLR 23.0, WordPress 6.2.2, and WooCommerce 7.7.0 : https://demo-woocommerce-flatsome-cloudways.wpsolr.com/shop/

Let me know if you find a similar issue.

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33444

Which WPSOLR release is it?

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33431

Does the url change when you select a category filter?

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33429

And in the Ajax results, are the results correct?

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33427

In the js console, what does return the ajax call?

[wpsolr]

3 years, 4 months ago in reply to: updating to wordpress 6.2.1 and woocommerce 7.7.0 one filter stopped working #33420

Can you describe “one of my filters stopped working (product category filter)”?

[wpsolr]

3 years, 4 months ago in reply to: Can HTML Content be Indexed from custom fields? #33351

The default search concatenates all indexed fields before removing HTML and php tags with strip_tags().

You can instead configure “2.3 Boosts” search, which does not filter searched contents.

[wpsolr]

3 years, 4 months ago in reply to: Index Sale Price along with Regular Price #33316

Can you see them in your database?

[wpsolr]

3 years, 5 months ago in reply to: Index Sale Price along with Regular Price #33263

Select _regular_price and _sale_price on screen 2.2 instead of _price?

[wpsolr]

3 years, 5 months ago in reply to: in section 2.2 I can’t overide labels for CPT’s #33261

Thanks for the feedback!

[wpsolr]

3 years, 5 months ago in reply to: Do you offer a service to set up Woocommerce and Solr #33255

Please notice that our setup pricing can be found on the pricing page

For a site in English, with an automatic live translation (GDTranslate), a keyword search with Solr, Elasticsearch, OpenSearch, or Algolia, would not be possible. Especially if you need to reach more countries and languages.

You would rather use a vector search like Weaviate, which was successful for WooCommerce clients in a context of multi-lingual queries for a mono-language WordPress.

The vector search will also bring semantic search and automatic check-spelling, with faceting, in 100+ languages.

The vector search and keyword search will be equally fast and scalable. But the overall speed will depend on WordPress mostly: a fast search with a slow WordPress will remain slow, but the search will use less server resources even in periods of high traffic.