Hey Bubblers,
we have just published a radically improved version of our Algolia Search plugin, and that’s why we have renamed it into Algolia Search v. 2.0
Main update is that it now returns whole objects rather than separate fields and so it’s much easier to configure and use it now.
We added better error handling and improved documentation both inside the plugin and as an external documentation.
The new update comes as a new element within the same plugin, so all the existing users can either continue using the setup they already have or migrate to the new configuration.
plugin page is still the same Algolia Search V2.0 Plugin for Bubble | Zeroqode
and you can find the links to the docs, demo page and the Bubble’s plugin page there.
Thanks for asking and sorry for such a delay. Let us provide some insights to help you all in here.
@RonyjM, yes – it is possible to use it in a Reusable Element. It is just required to make sure everything is configured properly as per docs, and perhaps you can just try to copy all elements as in our demo setup, into a Reusable Element, then give it a try.
However, if you are placing the plugin element and the searchbox into a Reusable Element, but the retrieved results are displayed in your page, this setup is not going to work unless you save the input’s value into a state of your Reusable Element, then retrieve data from Algolia based on this state.
Hi zerocode and thaks for this plugin. Now that there is an official bubble algolia integration, is this plugin still relevant ? Why ? Thanks for clarifying
Is there a way to make the Algolia Search V2.0 respect Privacy settings, or will it always retrieve all results from the searched data type (like the bubble native implementation)?
Action Add Object. Now, you can add an object to the index, automatically assigning it an object ID.
if you need the object id to match the one in the bubble id, add the field objectID with bubble unique id value to the object.
One more feature that displays data in your app when the checkbox “Only search” is unchecked. Otherwise, the data will be displayed only when you do a search for an item. You can find this option in the plugin element.
If I understand your question right, it is possible to limit the access to displayed data for each user by defining a filtering rule inside the plugin tab.
A solution for your use case is that in the Algolia dashboard define a filtering rule. And inside the plugin, you can set this filter either static or dynamic. In this way, it will select which information should be displayed to your user depending on his status.
Looking into the plugin and was wondering if there was a way to auto-update the Algolia records whenever the Bubble DB gets updated? I know the native integration states it can do this but would prefer to use your plugin (and not upgrade to the Pro tier).
We’ll be doing a bunch of CSV uploads to the Bubble DB and I’m trying to workout how that data gets transferred to Algolia? i.e do we have to update it manually in both Bubble and Algolia, run a workflow, etc…
