Would love to see the ability to return data about multiple facets and have that data exposed as a state on the element.
Hey @bansalmohit,
Appreciate your message and my apologies for the delayed response during the weekend.
We’re in the process of checking with the team to determine the cause behind the larger number of results you’re seeing for the Woocommerce value. We’ll keep you posted on any findings. Our assumption is that the results include every instance where this term appears.
Regarding your second query, you can find more details on the topic and instructions on how to set it up here: Link to Documentation
Once we receive a response from the development team, we’ll promptly update you. Thanks for your understanding and for using the Algolia Plugin! 
Hello @jared.gibb,
Thanks for reaching out and sharing your request.
We’re in the process of verifying this with our development team. We’ll be sure to provide you with updates as soon as we have more information on the matter.
If you have any further inquiries, please don’t hesitate to let us know.
Best regards,
Zeroqode Support Team.
1 Like
wanted to check back in here
i’ve followed your docs to do a facet search but seem to still be doing something wrong
the video is talk at first, then i walk through my facet that im searching for being ‘searchable’ and an actual facet, then i show how a query returns values in the algolia element itself but when the same basic query is thrown for a facet search, nothing is returned
Hi @marcus3,
Thank you for your video message and for using the Algolia plugin.
The details have been shared with our development team for examination. As soon as there are any updates, we will promptly provide you with further information.
Thank you for your understanding.
Best regards,
Zeroqode Support Team.
any updates on this?
Hi @bansalmohit,
Here are some updates from the team regarding your question.
-
To display the exact number of items “Woocommerce” try to set the “typo tolerance” to false, this will search only for this word.
-
Search for Facet Value action needs to be upgraded within the plugin. We will notify you once the plugin action is upgraded.
Thank you for your patience and cooperation. 
Hello @jared.gibb,
Currently, it is not possible, but after the plugin update, we will include this option.
We will promptly notify you once it is released.
Thank you for your understanding.
Have a great weekend ahead.
Regards,
Zeroqode Support Team.
Hey @marcus3,
Thank you for your message.
The dev team is still looking into your request.
As soon as we have any relevant updates, we will notify you immediately.
Thank you for understanding. 
Regards,
Zeroqode Support Team.
Hey @ZeroqodeSupport ,
since v3.44.0 the search doesnt trigger with less than 4 characters in my setting. Was there a change in the behaviour?
Hey @stefan.pointecker,
Thank you for your message and for bringing this to our attention.
The dev team is currently working on a Plugin update and will also address your inquiry.
After the plugin update, the search will trigger with 2 characters.
Thank you and we will notify you once the new version is released.
Best regards,
Zeroqdoe Support Team.
1 Like
Hey everyone,
We have some great news. 
Glad to announce that we’ve upgraded the Algolia Search V2.0 Plugin to V4 and since Version 3.47.0 all plugin actions were adapted to the new V4.
@bansalmohit All these inquiries should be easy to achieve within the last plugin update, please give a try and let us know if you have additional questions.
Hey @jared.gibb, after some research we’ve come to the point that even Algolia does not recommend using such a thing “It’s recommended that you use the filters parameter instead of facetFilters since filters has a more straightforward, SQL-like syntax, and supports both filters and facets.”
Documentation: facetFilters API parameter | Algolia
Hi @marcus3,
Please update the plugin to the latest version. Now you should be able to achieve the desired results. 
Should you need any further information, please let us know.
Thanks again for your patience and cooperation.
All the best,
Zeroqode Support Team.
Hi - Throws a JS error - consistently for me. Doesn’t seem to impact searching - just filling up our monitoring with noise. 
Hello @lindsay_knowcode
Thank you for reaching out to us!
Could you please provide more details about the action that led to this error or what you were doing when it occurred? This information would be valuable in helping us understand the root cause of the error and provide you with a more accurate solution.
We appreciate your cooperation and look forward to assisting you further
Have a productive Monday 
Hello,
I just upgraded to the newest plugin and now I am getting this error.
Workflow error - Plugin action Add objects (backend) error: TypeError: context.async is not a function at eval (eval at build_function (/var/task/util/util_harness.js:38:12), :14:31) at eval (eval at build_function (/var/task/util/util_harness.js:38:12), :42:8) at /var/task/plugin_api_v4_alpha.js:198:35 at harness (/var/task/harness.js:115:21) at /var/task/harness.js:154:70 at withGlobalHandlers (/var/task/harness.js:66:41) at Runtime.myHandler [as handler] (/var/task/harness.js:154:16) at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1173:29)
I am using 3.49.0
I was on 3.34.0
Could someone take a took?
Hello
We have tested our demo page, which you can visit here: https://zeroqode-demo-11.bubbleapps.io/algolia_easy_search
Specifically, the error TypeError: context.async is not a function suggests that the code of the plugin is attempting to call an async method on the context object, which either isn’t defined or doesn’t support this function.
To better assist you, could you please provide us with the following:
-Screenshots/Video of your configuration.
-Workflows associated with your plugin
-Any additional details you believe are important for us to replicate and understand your use case.
Thank you for your understanding and cooperation.
Looking forward to your response.
Best Regards,
Zeroqode Support Team
Hello,
Here is a screen recording on my workflows and how they work on the version 3.34.0 but not on the version 3.49.0.
I don’t believe I am using Howler js.
Hi @rosshelton,
Thank you for getting back and for the shared video too. 
According to changelogs on version 3.34, it was an added action to add objects on the backend, all further changes didn’t involve any change or modifications to this action.
It might be due to recent Bubble updates.
We will forward all these details to our dev team and get back to you with a response as quickly as possible, in the meantime please roll back to the version that suits better for your needs while we check.
Thank you for your understanding and cooperation.
Best regards,
Zeroqode Support Team.
I appreciate the help!
Thanks! I await what you find out.
1 Like
Does the Algolia Search V2.0 plugin allow for case insensitive searching?
I am about to update my bubble plan to professional just to get this plugin if it solves the case insensitive issue. Just want to confirm before I do so, thanks.
Hi @emmett,
Thank you for your message and sorry for the delayed reply over the weekend.
Happy New Year to you. 
Yes, the Algolia plugin does allow for case-insensitive searching. This feature is particularly beneficial as it ensures that search results are returned regardless of whether the search query is in upper case, lower case, or a mix of both. This makes the search experience more user-friendly and efficient.
For instance, you can check our plugin page and try searching for a plugin by name, either way, you type the plugin name, you will get the same results:
To successfully integrate the Algolia plugin into your app, please carefully check the supporting documentation and demo editor page.
Let us know if you have other plugin-related questions.
Regards,
Zeroqde Support Team.
No worries at all about the delay, I really appreciate this well thought out reply.
This is huge. I am shocked that there is no easier way to implement case insensitive searching without the use of advanced filtering or duplicating database fields, but I am very thankful for this integration workaround.
Thanks again and happy new year.
1 Like