[wpsolr]

1 year, 9 months ago in reply to: Saving wp solr plugin settings issue #52624

Strange. A workaround: unselect post type “Variations”, then save. It should reset the fields. Then reposition fields as you’d like, then save.

[wpsolr]

1 year, 9 months ago in reply to: Saving wp solr plugin settings issue #52618

Do you see errors in the js console? Or in WP_DEBUG logs ?

[wpsolr]

1 year, 10 months ago in reply to: Exclude a Taxonomy Term from the index #52556

To exclude post types from the index based on some criteria, you can modify the SQL that retrieves posts to be indexed.

[wpsolr]

1 year, 10 months ago in reply to: Exclude a Taxonomy Term from the index #52553

A checkbox “Hide” is available on each facet item in screen 2.4. Click first on button “Override each facet label” on your field “status”.

You will need to reindex all your data.

[wpsolr]

1 year, 10 months ago in reply to: WPSOLR error messages when updating plugins #52291

Those warnings are generated by recent versions of PHP. They used to be there, but not considered as warnings by older versions of PHP.

I’ll update WPSOLR to get rid of them on next releases.

[wpsolr]

1 year, 10 months ago in reply to: Problem with update messages. #52251

Indeed you can on our download page. But you’ll have to wait for the release of 24.1. For now, you can download 24.0

[wpsolr]

1 year, 10 months ago in reply to: Problem with update messages. #52249

This error comes from the WP REST API. I cannot imagine how it can be related to WPSOLR.

[wpsolr]

1 year, 10 months ago in reply to: Problem with update messages. #52246

However, it shows the new available version 24.0 when I already have 24.0 installed

This is a bug indeed, fixed in next release 24.1

{“code”:”wp_die”,”message”:”Briefly unavailable for scheduled maintenance. Check back in a minute.”,”data”:{“status”:503},”additional_errors”:[]}

Do you see it now? I checked on my side, all looks fine.

[wpsolr]

1 year, 11 months ago in reply to: Problem activating the Boosts #46486

Multi_match with boosts and cross_fields could be your solution, but is not implemented.

[wpsolr]

1 year, 11 months ago in reply to: Problem activating the Boosts #46484

No need to reindex. Unless you select “Copy to a text field” on a field, for instance on a taxonomy or custom field.

[wpsolr]

1 year, 11 months ago in reply to: Problem activating the Boosts #46482

With Elasticsearch, you can use the advanced scoring add-on.

It will get you recent and relevant results.

[wpsolr]

1 year, 11 months ago in reply to: Problem activating the Boosts #46480

Please try without a sort. Sort should be “Relevancy”.

The 3 fields you chose do not show “Copy to a text field”, because they are already using the analyser.

[wpsolr]

1 year, 11 months ago in reply to: Problem activating the Boosts #46478

Which plugin and version do you use?

[wpsolr]

1 year, 11 months ago in reply to: Problem activating the Boosts #46464

The field “content” contains all the data. You could add it, with a low boost value.

Or you can select the boost option “Copy to a text field” for all the fields which are not processed by the analyser of your index settings (like “English”) by default.
For instance, all taxonomy fields are not analysed, which make them irrelevant to most searches which are not exact.

Notice that when you change the option to “Copy to a text field”, you will need to reindex all your data.

[wpsolr]

1 year, 12 months ago in reply to: We have 2.8 Million Products in WordPress, but WPSolr recognizes only 370,000 #46442

I’ve been in touch with the developer of tecCommerce, plugin for the TecDoc catalogue (The world’s leading automotive spare parts catalogue) integration, and we managed to build a POC to integrate both plugins, by adding the tecCommerce category filter to WPSolr’s OpenSearch query dynamically.

Even better, it will work with all other WPSolr’s search engines: Solr, Elasticsearch, OpenSearch, Weaviate AI, Vespa AI, Algolia, Google Retail.

Please let me know when it is available and installed!