[wpsolr]

3 years, 5 months ago in reply to: Manually Send WC Product ids to Index #33077

You can see the query that gathers posts to index by selecting the “Debug mode” checkbox during indexing.

[wpsolr]

3 years, 5 months ago in reply to: Slow keyword search #33076

All seems correct.

The query time should be small, either with Solr or Elasticsearch. Only Query monitor could tell us.

Can you try with smaller parameter of facet items (1600 => 50) in screen 2.1?

[wpsolr]

3 years, 5 months ago in reply to: Slow keyword search #33073

Please paste here screenshots of screen 2.1 and 2.2

Did you configure facets (settings and widget) and can you see them on your search and category pages?

[wpsolr]

3 years, 5 months ago in reply to: Slow keyword search #33071

It looks like WPSOLR is not powering the search.

Did you activate the search archive in screen 2.1?

You can use Query monitor to verify.

[wpsolr]

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

The minimum price of $99/month is for up to 40k products.

I missed the Recombee’s usage rate on items inside a plan !

So if i understand correctly using the product catalog that wp-solr creates, and sending the events separately i might be able to create a ( less than ideal ) recommender system.

I think a recommender cannot be just “ok”, it must be great. Its goal is to improve the conversion rate by a few tiny percents, which can only be achieved at great costs. Does it worth it?

For Vespa, you’d need to train a model.

For Weaviate, the Ref2Vec module would require to send events as users with relationships to products.

[wpsolr]

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

I forgot: you’ll need the classic editor to see the WPSOLR notifications.

[wpsolr]

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

It should be fine.

You can also unset it when no lat,long parameters appear in the url.

[wpsolr]

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

You can use this hook:

use wpsolr\core\classes\WPSOLR_Events;

add_filter( WPSOLR_Events::WPSOLR_FILTER_SORT_FIELDS, 'wpsolr_filter_sort_fields', 10, 1 );

public function wpsolr_filter_sort_fields($default_sort_fields) {
   return $default_sort_fields; // array of field names
}

[wpsolr]

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

Just save a product, and it will be indexed. The success/error message will be displayed on the page.

[wpsolr]

3 years, 5 months ago in reply to: Getting error on indexing #33057

You can find them here: /forums/forum/licenses-and-billing/wpsolr-releases/

[wpsolr]

3 years, 5 months ago in reply to: Getting error on indexing #33055

There is a fix for this issue of malformed term hierarchies in recent versions of WPSOLR. Do you use the latest WPSOLR 23.0?
(current line 149 is a now a comment)

[wpsolr]

3 years, 5 months ago in reply to: Getting error on indexing #33053

It looks like some taxonomy terms are malformed. You can add some code in /wp-includes/taxonomy.php:4572 to write debug information in debug.log and find out what is the issue.

[wpsolr]

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

(Issue open at Weaviate: https://github.com/weaviate/weaviate/issues/2909)

[wpsolr]

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

either SaaS recommender solutions get very expensive

How many recommendations per month do you forecast?
For 250k products, Recombee’s standard plan starts at $99/month for 100K API calls/month. After that, it’s around $1/1000 calls/month. I’m not sure it can be beaten with any kind of self-hosted open-source RecSys !

Likewise gorse was using a huge amount of memory and cpu in redis/mongodb to calculate the relative products. It took a full 3 days to calculate all products and start again.

Do you use a GPU for the training? Also, Gorse is a one-machine for training, which can lead to bottlenecks.
In general, the training cost of recommenders is underestimated. Unless you choose scalable systems like TorchRec, built with parallel training.

Do you think it will be possible using wp-solr + vespa/weaviate if i send the events manually?

None provides the model training pipeline.
Look at this Vespa’s recommender tutorial for instance.
Weaviate provides the RefToVec module to build a recommender I guess.

[wpsolr]

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

I collect events with server side tag manager, and send them to the recommender system, with a custom tag i made in tag manager.

Algolia provides a similar solution to collect GA events. But it is so complicated for ordinary WooCommerce sites, and so not flexible, that It cannot be considered for a plugin integration.