Hey @zelus_pudding
Any chance to add the typesense JOINs feature to Omnisearch in a near future ?
Hi @zelus_pudding - facing a strange error when trying to sync a table. Here are the screenshots of the error and of the Bubble logs:
Hey Rodrig, my apologies for the delay - just got back from holiday abroad. I imagine you may have resolved this issue or moved on? What I will say given the little context I know is that perhaps your app required a password for runmode. That may have been the issue where disabling that would allow the sync to complete (the plugin needs the app to be publicly available to determine your table’s data structure/option sets).
Hi,
This is my first entry in the bubble forums, so apologies in advance if I’m breaking any etiquette.
I’ve emailed the creator of this plugin directly, but I thought I would maybe give it a go here too? Maybe someone else has seen this issue and can help?
I’m implementing the Omnisearch plugin with Typesense as the backend, and really pleased with the early results. I’m able to sync my data types and do blazing fast queries using the visual element.
My problem comes though when trying to use the actions for keeping my index in sync, i.e. create / update / delete search record. I’m getting the error shown below. Very very infrequently they seem to work when deleting search records though.
I’ve tried on the app workflows and also in the background workflows, and I’ve tried with several data types, and experimented with all fields sync vs one or just a few fields synced.
Any ideas? I’m using a custom domain (orgoniser.com) and the free tier of Typesense, but I doubt any of that might be the issue. I’ve already purchased the license for Omnisearch, so that should be ruled out too.
The error I’m getting is:
SyntaxError: Unexpected token < in JSON at position 0
at JSON.parse ()
at o.json (eval at build_function (/var/task/util/util_harness.js:37:12), :20:5099)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Promise.all (index 0)
at async nl (eval at build_function (/var/task/util/util_harness.js:37:12), :22:6070)
at async eval (eval at build_function (/var/task/util/util_harness.js:37:12), :22:11162)
at async /var/task/plugin_api_v4_alpha.js:198:29
at async harness (/var/task/harness.js:115:15)
at async /var/task/harness.js:152:64
at async withGlobalHandlers (/var/task/harness.js:66:10)
Thanks!
Gonzalo
I am seeing and have confirmed reports that Omnisearch is failing to load search results on page load (we see that our demos are busted as well). Nothing has materially changed with Omnisearch to prompt this failure mode so Bubble must have released an update to how plugins load / work or something very unique is happening. I am looking into releasing a solution as soon as possible.
UPDATE: Omnisearch has been updated to version 2.1.2. This morning, Omnisearch began to fail to load search results for users on page load. The reason for this failure is that Bubble appears to have released a plugin/page update that fixed a long standing issue with Bubble plugin initialization. Historically, on page load, the code that runs in the update section of a plugin can run multiple times on page load. This can adversely affect a plugin’s operation if it was designed expecting / needing to only be run once (or zero times) on page load.
In response, Bubble developers have had to implement our own tricks to ensure the update section runs an expected number of times on page load. In Omnisearch’s case, we baked in a patch to get the update section to run only once on page load. When Bubble released their update today, our patch made it so the update section didn’t run at all, thus resulting in users seeing empty search results on page load.
We’re happy to see Bubble make this release (I’m assuming it was a targeted fix for the issue described above) and to be able to release a fix for our plugin quickly. As the issue does affect all Omnisearch versions prior to 2.1.2, we do recommend everyone update to the latest version. Updating from version 2.1.0 does not require resyncing indices however updating from much older versions does require resyncing indices.