Hey, I noticed you are also looking at using Typesense as an option. Connecting to Typesense via the Bubble API connector is a workable option! That said, just want to let you know that connecting to Typesense via Omnisearch will give several advantages, like:
Preserving privacy rules (Bubble connector wonât do this).
Out of the box index synchronization per environment (any time you change related bubble tables, youâll have to re-initialize your Bubble connector connection to Typesense).
Faster search as you type (the dedicated visual element weâve provided searches your Typesense cluster as you type instead of with the standard Bubble input delay)
Advanced search filter authoring.
Definitely give the Bubble API connector a try but please know you can give Typesense a spin via Omnisearch while we work on fixing the Algolia bug you encountered earlier - our demo shows that the Typesense portion of the plugin is working without issue and I can help you get setup with that! Just let me know!
Thank you, that would be great, @zelus_pudding . It would be helpful if you could assist me with setting up Typesense or provide more detailed instructions on how I can set it up on my end through your plugin.
Sure thing! Have you had a chance to go through our getting started guide? It sounds like youâve already installed our sync-admin template and have been able to sync records to Algolia so to setup Typesense would follow the same steps except youâd click âSync Typesenseâ on our admin template.
If youâve gone as far as syncing your records to Typesense and setting up the Omnisearch visual element and are getting an error, could tell me what that is? Or what youâre struggling with?
Thanks @zelus_pudding - I have synced the records to Typesense and set up the Omnisearch element, but when typing to initiate a search - it displays the following error:
Hey Paul, thank you for trying us out! Iâm thinking one of two things is happening;
youâre either trying to sync a bubble table from our demo sync template, or
youâve copied our sync template into your Bubble app but have not removed the admin checks (as directed here).
If itâs the former, the reason youâre getting that issue is because weâve locked our demo so that folks canât resync our db (the data youâd be syncing would affect the presentation of our main demo).
If itâs the latter, please remove the admin checks on your sync page in your application by following the full instructions provided in our second âArcadeâ here. After that, you can lock down the sync admin page however you normally would (i.e. by redirecting users on page load if they are not an admin).
Please let me know how it goes! Happy to answer other questions
**Edit: I now see you mentioned youâre trying to sync your own tables.
Hey Mikolaj,
Thank you for reaching out! We do have plans for additional improvements but Iâm curious what it is you would like to see Omnisearch do that it doesnât already. As it is, we do quite a lot. What do you need?
Something missing that we want to add is the JOIN (across multiple indices) capability that Typesense now makes possible. Algolia is considering such a feature and weâre thinking through how to implement. Before that, however, weâd like to add the âRecommendâ feature that makes it possible to make personalized search recommendations / âCustomers who bought this product also bought thisâŚâ type of experiences. Firm timelines for developing these are given to users who sponsor feature development - in which case it can usually be done in one to three weeks.
Plugin maintenance and bug fixes are performed as quickly as possible.
Hey Paul, sorry to hear about the frustrating issue. Can you tell me a little more about what youâre seeing? Is this to say that the index is made in Typesense but doesnât completely finish syncing? Can you include the error your getting via email? Iâd also want to be sure that youâre using the latest version. Can you confirm thatâs the case? Looking forward to getting this fixed for ya
Great question drixxon. Iâve held off on reaching out to beta users in regards to making the switch as there hasnât been a major reason to, yet. That said, as Omnisearch gets more updates, it will become necessary to switch over. Iâm putting together a short step by step guide for users to make the switch (Iâve come up with a way to do this that shouldnât take more than 10 minutes for folks to implement). Details to come. Thank you!
Hey Ian, sorry to hear about your issue. There is no material difference (currently) between SciousSearch and Omnisearch that would prohibit you from syncing correctly. In fact our demos are all set to use Omnisearch now and they sync just fine. What version of SciousSearch were you on? I strongly recommend updating to the latest version or switching over to Omnisearch.
