[wpsolr]

4 years ago in reply to: How to use the Views extension #31153

For now, it is not possible.

[wpsolr]

4 years ago in reply to: How to use the Views extension #31151

Right now WPSOLR views are not for displaying search results. Showing results is still the responsibility of themes, and only on archives.

[wpsolr]

4 years ago in reply to: Filter not clearing : Issues with factes with same names #31149

Indeed, two terms in the taxonomy with the same name are prohibited. I advice to change the redundant names and reindex all the related post types.

[wpsolr]

4 years ago in reply to: How to use the Views extension #31145

WPSOLR View are in their early release. For now they can be used to configure 2 search engines and use them on different sections of a site.

For instance, a view for all searches with Elasticsearch, and a view for Question Answering with Weaviate.

[wpsolr]

4 years ago in reply to: Exclude posts status private from index #31142

Only published statuses are indexed. Unless you selected “Index all status” on screen 2.2

[wpsolr]

4 years ago in reply to: Tagging and Count mismatch issue #31139

With WPSOLR, taxonomy hierarchies show a facet count only to leaves (terms without children). Therefore, parents do not show facet counts. There is no way to change that behaviour.

[wpsolr]

4 years ago in reply to: Stop facets from refreshing unless other facet is selected #31136

I understand, but this is not possible. This part is coded in very complex javascripts, out of reach of the WP hooks.

[wpsolr]

4 years ago in reply to: Stop facets from refreshing unless other facet is selected #31134

This is not possible.

Facets are refreshed instantly on purpose to guarantee that there are always some results displayed.

Let say you have 2 results, post1 with facetA, and post2 with facetB.
Clicking on facetA will show post1 and hide facetB.
If you could click on facetA and facetB, then refresh, you would get no results at all. Which is the worst case scenario for any visitor.

[wpsolr]

4 years ago in reply to: deleted items still showing in suggestions #31131

Did you check the option “Index all status” in screen 2.2? In that case uncheck it, empty your index, and reindex all your posts.

This would not delete the posts in the index, but they would anyway be filtered out on the front-end.

This option is meant to not remove post types that must be displayed in the back-end, even with status not published like orders.

[wpsolr]

4 years ago in reply to: deleted items still showing in suggestions #31129

You could follow the steps mentioned above to find out why your documents are not deleted from the index.

Or you could update your posts by code with a status different from ‘published’, which should remove it from the index (check that your “real-time indexing” option on screen 2.2 is checked).

Or you could empty and fully reindex your index with a cron during the night by using our cron add-on.

[wpsolr]

4 years ago in reply to: Developing country discount #31127

We have only one pricing, which includes all add-ons, search engines, and soon recommendation engines. We provide discounts on license seats volumes only.
WPSOLR can index, search, filter, and aggregate on WooCommerce custom fields/attributes/taxonomies indeed. With Elasticsearch, Solr, SolrCloud, Algolia, and Weaviate.

[wpsolr]

4 years ago in reply to: WordPress with API-Data: Crawler possible? #31125

When the API is called, storing its result in a post type?

[wpsolr]

4 years ago in reply to: WordPress with API-Data: Crawler possible? #31123

WPSOLR does not provide a crawler, it indexes post types.

[wpsolr]

4 years ago in reply to: Pagination not working with custom search slug #31108

/store/ is not a WooCommerce url that I know of. Is it from your theme?

[wpsolr]

4 years ago in reply to: Facets count not matching with total posts found #31105

The plugin does not show conts on parents hierarchies, only on children.

Check out on https://demo-woocommerce-flatsome-cloudways.wpsolr.com/shop/ for instance.