[wpsolr]

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

Indeed, if you migrated to WPSOLR 23.1, you are required to reindex all your data due to a structural change in category filters.

[wpsolr]

3 years, 4 months ago in reply to: Cron error #34241

1. Which WPSOLR version is it?
2. Do you see errors in your debug.log?

[wpsolr]

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

Nice talk.

Summary: WooCommerce with 200K products. The POC will be built with a Vespa docker instance, with a goal to validate the scalability during indexing on a 30 CPUs hardware. If all goes well, a cluster deployment will be investigated. The POC will test the deployment of xgboost ranking, and eventually Vespa will be used also for recommendations.

Here is the beta release including Vespa:
https://www.dropbox.com/s/1uva1f4x0btl7ln/wpsolr-pro-vespa-beta-1.zip?dl=1

Here is a sample docker:

services:
  node1:
    hostname: node1.vespanet
    image: ${WPSOLR_IMAGE_NAME}:vespa
    command: configserver,services
    healthcheck:
      test: curl https://localhost:19071/state/v1/health
      timeout: 10s
      retries: 3
      start_period: 40s
    ports:
      - 8080:8080
      - 19071:19071
    environment:
      VESPA_CONFIGSERVERS: node1.vespanet
      VESPA_CONFIGSERVER_JVMARGS: "-Xms32M -Xmx128M"
      VESPA_CONFIGPROXY_JVMARGS: "-Xms32M -Xmx32M"
    networks:
      - wpsolr-external-network-created-with-docker-network-create

In WPSOLR, you can setup the urls as:
– Admin cluster: https://node1.vespanet:19071
– Stateless cluster: https://node1.vespanet:8080

[wpsolr]

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

I just sent you a chat invite via Gmail.

[wpsolr]

3 years, 4 months ago in reply to: Errors in the plugin #34201

It looks like a connection issue with Elasticsearch.

[wpsolr]

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

Dynamic summary https://github.com/vespa-engine/vespa/issues/26693 is fixed already.

Arrays sorting https://github.com/vespa-engine/vespa/issues/26681 is the main showstopper now.

But as I understand, you do not need sorting, as you wish to sort by a custom xgboost ranking.

If you’re interested, we could discuss the opportunity of a pre-release.

[wpsolr]

3 years, 4 months ago in reply to: Can’t Deactivate/Reactivate License #34026

The activation on b*d.com has been removed.

[wpsolr]

3 years, 4 months ago in reply to: Disable duplicate calls to WP_Post::get_instance #33829

To fill the posts content before give them back to the theme for rendering with the post loop.

[wpsolr]

3 years, 4 months ago in reply to: Load Facets and Sort By Widget on Custom Page #33811

WPSOLR replaces the WP main query on archive pages. Home page is not an archive, and your WP_Query is not the main query.

It could eventually work if you selected your home page settings as “Posts loop” instead of “Page” in the customizer.

[wpsolr]

3 years, 4 months ago in reply to: Disable duplicate calls to WP_Post::get_instance #33810

Your customization will be erased when you’ll update WPSOLR.

You could instead update your theme’s archive templates to prevent displaying the thumbnails.

[wpsolr]

3 years, 4 months ago in reply to: Disable WPSolr default css and js for Facets #33805

Perhaps set a low priority like 99 in the action parameters that calls the deregister function.

[wpsolr]

3 years, 4 months ago in reply to: Disable duplicate calls to WP_Post::get_instance #33803

There is nothing in settings to do that.

[wpsolr]

3 years, 4 months ago in reply to: Disable WPSolr default css and js for Facets #33708

Perhaps your dequeue code is called before WPSOLR’s enqueue code?

[wpsolr]

3 years, 4 months ago in reply to: Disable duplicate calls to WP_Post::get_instance #33706

There is no hook to bypass this code.

[wpsolr]

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

Did you upgrade to WPSOLR 23.1?