[wpsolr]

3 years, 5 months ago in reply to: Recommendations ETA? #33046

Why is 250K products a problem?

Vespa is a general big-data engine, including a vector search with a lot of configuration abilities with a full ranking language. We’re currently integrating their vector database. But they also have recommendation features:

Vespa.ai is used as the search and recommendation backend at multiple Yahoo e-commerce sites in Asia, like tw.buy.yahoo.com.
https://blog.vespa.ai/e-commerce-search-and-recommendation-with-vespaai/

But building a real sysrec is a whole new topic. I considered Gorse also, but was not sure anyone could use it without an extensive investment in time and skills.

[wpsolr]

3 years, 5 months ago in reply to: Recommendations ETA? #33044

No ETA, no.

The work on recommendations for Recombee, Algolia, Amazon Personalize and Google Retail are half done. Mostly the catalog integration.

But the real problem is sending user events, and in vast quantities.

For instance, with Google Retail recommendations, 2 million events are required in the last 3 month.

With that, new laws like the European GDPR require more and more privacy. Some countries even declared Google Analytics illegal.

And on top of that, each recommender API has its own way of collecting events (AWS S3, API, Cloud storage …), each with different event types.

Last point, events/recommendations must be configurable enough to adapt to WooCommerce and other plugins. For instance, collecting orders require PHP hooks, while add to basket events require js hooks.

[wpsolr]

3 years, 5 months ago in reply to: Recommendations ETA? #33040

What kind of recommendations are you interested in?

[wpsolr]

3 years, 5 months ago in reply to: Addon for WP Gridbuilder? #33038

I’m a big fan of wpgridbuilder myself, and use it on all my projects!

I’ve thought of an add-on, but one of the main feature of wpgridbuilder is the filters. Which WPSOLR also provides as facets.

wpgridbuilder users want to keep their filters I’m sure. As WPSOLR users do.

[wpsolr]

3 years, 5 months ago in reply to: Weaviate clip encoder #33037

I understand.

You should ask Weaviate support, as they should be interested in this kind of feedback.

Please copy here your Weaviate’s issue link, so I can be notified and eventually participate !

[wpsolr]

3 years, 5 months ago in reply to: Indexing Error while trying to re-indexing articles #33032

This kind of message is often due to lack of resources on Elasticsearch’s server.

For instance, disk: https://stackoverflow.com/questions/50609417/elasticsearch-error-cluster-block-exception-forbidden-12-index-read-only-all

[wpsolr]

3 years, 5 months ago in reply to: Weaviate clip encoder #33031

Yes indeed.

You can follow the Weaviate’s CLIP documentation.

We also built a WooCommerce demo with Weaviate’s CLIP module.

[wpsolr]

3 years, 5 months ago in reply to: Sort by location not working – Fatal Error #33017

Some CSS or javascript?

[wpsolr]

3 years, 5 months ago in reply to: Sort by location not working – Fatal Error #33008

Usually, the search url is not open from a hyperlink, but from an outside search form (home page, or top header).

If you use option “Attach the geo localization js to your own search form(s)” to include those search forms too, the form will add the lat,long parameters to the search url automatically.

[wpsolr]

3 years, 5 months ago in reply to: Sort by location not working – Fatal Error #33006

You can use the option “Attach the geo localization js to your own search form(s)” to declare all search forms wich open the search url, including the top search form or the home search form.
The js script will add the lat,long parameters automatically to the search url and solve the geo sort issue.

[wpsolr]

3 years, 6 months ago in reply to: Sort by location not working – Fatal Error #33004

Your site must be secured (https) to enable the js script to get your location and add it to the url.
The user’s authorisation must also be activated in the WPSOLR Geolocation add-on.

[wpsolr]

3 years, 6 months ago in reply to: Sort by location not working – Fatal Error #33001

It looks like the second sort does not work with Elasticsearch first geolocation sort.

Remove the second sort in your “2.5 Sort” settings, all your previous debug code, and all should be working fine, including the widget sort (I just tested).

[wpsolr]

3 years, 6 months ago in reply to: Sort by location not working – Fatal Error #32996

Can you check in file wpsolr-pro/wpsolr/core/classes/engines/elasticsearch_php/class-wpsolr-searchelasticsearchclient.php, in function search_engine_client_add_sort_geolocation_distance, why the “if blocks” prevent the code adding the sort:

$sort_item = [
  '_geo_distance' => [
  $field_name     => [ 'lat' => $geo_latitude, 'lon' => $geo_longitude ],
  'order'         => $sort_item[ $field_name ]['order'],
  'unit'          => 'km',
  'mode'          => 'min',
  'distance_type' => 'plane',
  ],
];

[wpsolr]

3 years, 6 months ago in reply to: Sort by location not working – Fatal Error #32993

Can you try with the same search url as mine?

[wpsolr]

3 years, 6 months ago in reply to: Sort by location not working – Fatal Error #32991

Your examples show an ACF field “geolocation_acf”, but also a field “geolocation”. Please setup “geolocation_acf” everywhere: screen 2.2, and sorts screen.