[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27609

No need to reindex if you want to try quickly with “Out of stock visibility” off.

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27606

I understand.

I will build you a fix ASAP: https://trello.com/c/qT4BvMVa/172-fix-admin-orders-not-shown-when-stock-management-is-active

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27604

The error in logs is during indexing (probably the post in error you mentioned).
Regarding the Algolia query, it seems to be a bug: a condition on product stocks is added to queries not related to products.

Can you uncheck “Out of stock visibility” in “WooCommerce -> Settings -> Products -> Inventory” and test again?

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27601

Your settings look fine. You should see the post types in your backend.
Can you activate the search engine logs in screen 2.1 and check the Algolia query?
Can you also activate the WP debug.log and check for errors?

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27598

Can you show me here a screenshot of your WPSOLR screens 2.1 and 2.2 ?

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27597

Can you verify in your Algolia account that the data is in the index? (order, product, coupon)

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27595

i synced all the data but nothing shows on admin dashboard in orders and not in coupons

What do you mean?

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27569

You can also create suggestions that will appear as autocomplete in the standard backend search bars.
You will then have autocompletion on backend product search bar, order search bar, post/page search bar, or coupon search bar.

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27567

No, one index is enough. Just select the option “Replace admin archives”, and the post types you want to index (“order”, “coupon” …), in screen 2.2.
Also add for each post type all the custom fields you want to search in. For instance, the order’s customer name and customer invoice address.

• This reply was modified 5 years, 1 month ago by wpsolr.

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27564

Yes, you can use WPSOLR with Algolia for WooCommerce backend order search.

• This reply was modified 5 years, 1 month ago by wpsolr.

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27562

I just say that the Elasticsearch official distribution does not provide a Hebrew analyser.

You can find a discussion on this subject: https://discuss.elastic.co/t/analyzing-hebrew-string/183850

[wpsolr]

5 years, 1 month ago in reply to: hebrew language not present #27559

Elasticsearch does not provide a Hebrew analyser by default.
Algolia does provide one.

[wpsolr]

5 years, 1 month ago in reply to: License does not work on new install #27553

I removed the old activation on your subscription. You can activate your site now.
I also removed your new temporarily trial subscription.

[wpsolr]

5 years, 1 month ago in reply to: Toolset Views Search not working after integration #27551

WPSOLR widgets work on archive pages. So, ?s= in your case.

[wpsolr]

5 years, 1 month ago in reply to: Toolset Views Search not working after integration #27548

Toolset search being an archive, you can use WPSOLR facets widget to replace Toolset search filters (Toolset search filters will not work).