alesstracker21

Hi Michael…truth is, it didnt work and I didnt want to keep on bothering you…I was still getting the non product results in the list.
It feels it would be much easier to be able to simply replace which index its using for general search. Straight up let me make only a wp_posts_product index and only target that. Because the way it is it forces me to index eveeerything, just to have to find a workaround to delete those undesired items anyway.

After a while I also realized that AJAX wasnt working either…
It returns 0 items, the response goes like:
{“count_posts”:0,”total_posts”:0,”page”:2,”num_pages”:1,”orderby”:”post__in”},”query_ids”:null}

So it seems I might to just have to import their API client and do it manually…

It seems I’m not the first user having issues with Elementor and the way the plugin displays messages, I saw a couple older ones that weren’t solved. It’s a huge problem because Elementor is huge and more and more people are using it.

It would be nice to have a toggle for people that use Elementor that disable such Success or Failure messages, and to let us use shortcodes or other options to handle that ourselves.

We do are interested in using the Pro Addon long term if it works, but right now I am in a development stage and need to check if it really could be a useful solution for us or we need to look elsewhere, and sadly I am not allowed by the company to make payments until I am sure.
So, I will index wp_searchable_posts, if the code snippet you mention for products only is available we would greatly appreciate it so we can try it for the time being at the dev stage, and if we can get it to work, I am sure to get back at you guys with the possibility of going Pro, I have read the other SEO and product tools you have available and they do seem very important.

Thanks a lot!

Thanks…yes…I only want it to pool from products both from the search page and from autocomplete.

I am just asking if I need to pick All Posts and then filter only products because you mention the plugin will only take wp_searchable_posts for WP_Query. I only have one index in Algolia and that is wp_posts_product.

Here are some captures of how it all looks like from my point of view.
https://ericksonstock.net/wp-content/uploads/2023/11/algoliahelp.png

The plugin does keep on saying I need to index All Posts.
It sounds counterproductive because I don’t want to search through All Posts, just Products.

Once again, thanks for the continued support!
I did the test you mentioned and now know for sure my search page isn’t using Algolia whatsoever, even though the “Use Algolia with the native WordPress search template” setting is activated.

So, to make sure I understand, it’s my last doubt… if I wanted to use Algolia for it (search page, not autocomplete), I would have to use All Posts (searchabe_posts), correct?
So, to set it up to only return products, would I have to just mark “All Posts”, push settings, index that, and only then ON the Algolia dashboard, have it only consider the products?

I am just a bit lost on what would be the step by step process to have it only consider products if I am selecting All Posts.

I have also analized the code you mentioned (class-algolia-search.php) and it seems to me it doesn’t explicitly specify the use of the wp_searchable_posts index to intercept WordPress search queries (WP_Query). It doesn’t specify which Algolia index it’s querying. This decision is likely made in a different part of the plugin, perhaps?

• This reply was modified 1 year, 3 months ago by alesstracker21.
• This reply was modified 1 year, 3 months ago by alesstracker21.

Wow, what an extensive answer, thanks a lot!

I had chosen a custom index name prefix in the plugin: wp_algolia_
And then hit “Push Settings”. Having only selected Products on the autocomplete, indeed.
So our relevant index in Algolia was called wp_algolia_posts_product with 56k records.
I just set it back to the default one and pushed again (wp_posts_product), it’s still not working…
I had done it through the UI, however, if it is necessary so that our custom search page can also pull the results from Algolia, we can switch to code.

It’s our search results page that isn’t using the Algolia query for some reason:
https://ericksonstock.net/?s=children+on+house

I have enabled define( ‘WP_DEBUG’, true );

You mention that the “Use Algolia with the native WordPress search template” setting should intercept the query being made and then give different results than the default WordPress ones, right?
Is there any way I can check exactly what query is being processed when searching on the website?
We are using a plugin to display the images that is configured to load them using AJAX and it has an option that says:
Posts source: Current query posts
There might be a chance that whatever method it’s being used to intercept the query is not being taken into consideration when displaying our search results….

We also plan it to take into account product tags first, and then other taxonomies afterwards, because they are being used as keywords. Also to have it not take into account common conjunctions (like on/at/in/of/a/over/and so on), but I suppose that can all be done through the Algolia dashboard…

Thanks for the help on the autocomplete question too! I’ll look into the markup for the autocomplete template, I don’t have any more questions on that regard.

Thanks! I will.