Is it possible use this to set a custom state? I downloaded the other algolia plugin but now want to use this one due to issues with the other one. with teh other one I exported the data from Bubble and uploaded CSV to Algolia. Linked API. Getting great results in a repeating group. Repeating group displaying fields 1 - 5 have added a check box in each cell but now having trouble saving the field1 value
How do you select an item from your list of results to add to a custom state? I exported the data from Bubble and uploaded CSV to Algolia. Linked API. Getting great results in a repeating group. Repeating group displaying fields 1 - 5 have added a check box in each cell but now having trouble saving the field1 value
While we’re not entirely clear on your specific use case or requirements, you can configure the result of Algolia searches to be stored in a custom state. Below, we’ve included some screenshots showing how we set this up on our end.
Thanks for the reply, However your suggestion adds the results of the search to a set state I only want to add some of the results from a an RG example the item with the checked box
Yes, you can still store the information in a custom state. When you want to save a simple text from the RG, ensure the custom state is of the Text type (probably this is the reason you get an error when setting up “Parent group’s text”. A crucial note here is that “Parent group’s text” will only fetch information from “field1” or the one you have added in the Repeating Group
Additionally, you can use dynamic data such as “AlgoliaSimpleSearch’s Result’s fieldX:item #Current Cell’s index”, where X represents the field you wish to store. This method will capture the information of the current cell based on the specific field you’re interested in saving.
Please continue to experiment and discover the setup that best meets your needs
I hope you’re well and appreciate your patience as we worked on a solution .
I’m excited to share that in the latest update of the Algolia Search plugin - version 3.61.0 - we’ve introduced a new setting called “Filter Unique Items.”
This feature allows you to specify a field within you Algolia Index for which you want to receive only unique items. The plugin will then ensure that only unique items are returned in the plugin element, enabling you to display items as you previously indicated.
It’s important to note that Algolia differentiates between text/numbers encapsulated in quotation marks and plain numbers. Therefore, an entry with 123 and another with “123” are considered distinct and both will be returned.
To access this new feature, please update the plugin by navigating to the “plugins” tab in your Bubble editor, selecting the plugin, and choosing the latest version from the dropdown menu.
We’d love to hear your feedback after implementing this update in your application. Let us know if everything is functioning as expected or if you encounter any issues!
@ZeroqodeSupport
I have a search page where a user may use it to search for results multiple times. After the initial search that returns a result, when the next search has no result, there is no way for me to know. The plugin’s result doesn’t get refreshed with blank result. If a search has no result, the plugin still has the result from the last search that has the result, which can be many searches ago. I am not able to show the user a message that there is not result for the search. What can I do?
Steps to reproduce
On a search page, search for something, e.g. iphone, that returns result.
Do a search again on something that has no result, e.g. abcde
The plugin’s result still contain the result from the 1st search (iphone).
On Algolia, you can see that my configuration can show 0 result.
We’ll discuss with the developers how to handle scenarios where the plugin returns no results, allowing you to display a message on your page that there are no existing records in your index. We will provide you with more information as soon as it becomes available.
If you have any questions in the meantime, please don’t hesitate to contact us .
We’ve reviewed the details you’ve shared and noticed that the “Query” value is empty in your app (image). Could you please try setting it to “input’s value” (image) to see if that resolves your issue?
Additionally, if this does not solve the problem, could you try enlarging your element and then, in the preview, use the Inspect tool to click on it and check if any data are retrieved in the element(image)? If no data are found, please recheck all the filters you have set up and verify your Algolia settings.
Thank you once again, and we look forward to your reply.
We wanted to follow up on our previous communication regarding the issue you were experiencing with the “Query” value in your app. Have you had a chance to set it to “input’s value” and check if that resolves the issue?
Additionally, if you tried enlarging the element and using the Inspect tool, were you able to retrieve any data? If there are still challenges, it may be helpful to review all set filters and double-check your Algolia settings as previously suggested.
Your feedback is important to us to ensure everything is functioning smoothly. Please let us know how it went or if there’s anything else we can assist you with.
Thank you for your time, and we look forward to hearing from you soon.
Great to hear that the advice proved helpful and solved your inquiry. Please feel free to reach us again when you need some help or assistance. It will be a pleasure to cooperate.
If you’re enjoying our plugins, we’d love for you to rate them. Simply go to the Plugins tab in the Bubble editor, search for the plugin by name, and award it the stars you think it deserves. Your support would mean a great deal to us!
Furthermore, if you’re willing to share your entire experience with Zeroqode, we invite you to do so at: https://zeroqode.com/review. Your feedback is incredibly valuable to us and the Bubble community, as it motivates us to continue developing outstanding products and maintaining excellent customer service.
Thank you again, and I wish you an amazing day ahead. If there’s anything more you need or questions you have, please don’t hesitate to contact us.
I use your plugin and am usually a big fan. However, I have a problem when I try to delete an entry from my Algolia index via a backend workflow. The entry is simply not deleted and when I look in Algolia’s API logs, I find a 400 response that reads as follows:
{
“message”: “Not enough rights to delete an object near line:1 column:93”,
“status”: 400
}
Actually, I should have configured my keys correctly in the plugin, as both the search and the addition of entries work without any problems. Do you have any idea what I am doing wrong or what the error code means?
Thanks so much for reaching out to us and for your kind words
Please send us a screenshot of how you configured the workflow and action, so we can visualize your settings and possibly spot something incorrect. Also, could you tell us how you are sending the object IDs to the backend workflow and confirm that you are sending the correct IDs to this action?
Could you add the action with the same configuration on the frontend and try to trigger it? There should be no such error with insufficient rights as the key added in the plugin settings has enough credentials for deleting. Please confirm that you inserted the key visible in the screenshot!
I have set up a database trigger that is activated every time a certain change is made. In this case, the database item “Chapter” is to be deleted from my Algolia index. To do this, I pass both the index and the ObjectID in the backend workflow. The identifier of the index is stored in an option set. Depending on whether a database item from the dev or live environment is changed, either the dev or live index is addressed in Algolia. The ObjectID of the Algolia item corresponds to the uniqueID in Bubble.io.
I have already checked whether the database trigger is triggered. For this I created a Create a new thing workflow next to the Delete Objects (backend) workflow and saved Index + ObjectID in Bubble.io. This worked without any problems. I also tried not to pass the index ID via an option set, but to enter the ID of the index directly in the index field. I also tried the same with the ObjectID (fixed instead of dynamic coding). Everything led to the same result: 400 response.
If I trigger the workflow directly from the frontend, however, it works. It also works if I move the Delete Objects workflow to an API workflow and trigger it from the frontend. The error only occurs if I run the workflow from the database trigger.
Note: The database trigger is triggered due to a Make Change to list workflow. Consequently, it is triggered several times within a short time, but I do not get a rate limit error, but a 400 response with the first change made.
Thanks so much for providing us with these details
Currently, our app plan does not have the possibility to use the backend triggers, so we were not able to test this. Would you be able to provide us with collaboration access to your page by adding support@zeroqode.com to the list and sharing the editor URL with us?
Please tell us the steps to get to the page where we can trigger the backend workflow, along with any credentials needed to access it successfully.
Hope to hear back from you soon, and get to the bottom of this behavior!
Please take this as a small reminder about our previous message. In order for us to investigate your use case further, could you please follow the steps above and get back to us with a quick message?
sorry for the late response and thanks for the little reminder.
Without me having made any changes, the problem had resolved itself in the last few days until it just reappeared.
I went searching again and found the following: When the delete object (backend) is triggered via database trigger from the live version, it uses the wrong key (search key instead of write key, I can see this in the API logs of Algolia), although I have actually configured it correctly (see screenshot).
The error does not occur in the bubble dev version, only in the live version and only if the delete action is triggered from a database trigger. Add and update actions from the backend also work without problems using database triggers.
Is that perhaps enough to help me? Since this is already a running app and the problem is only in the live version, I’m a bit worried about giving others such extensive access. However, if there is no other way, I would simply contact the email you provided with the details.
Thanks for the details and apologies for the delayed reply over the weekend .
We think we understand why the delete function is not working in the Live version. Firstly, it is interesting to know that it has been working from time to time, as the Search Key does not have any permission to delete objects. Since you are using your Write key in the test version, it is normal to notice some things working in the test but not in the live version.
The Delete action is using the key from the “api_key” field, and as we see from the screenshot, the key itself is only for search. If you could create a new key and provide it with search, delete object, add object and logs permissions, this one key will have enough permission to do everything without giving admin permission.
I’ll try it out tonight and get back to you tomorrow at the latest.
But one more question in advance: Do I really have to configure an extra API key for this or can’t I just enter my Write API key in the API key field above?
It’s a bit confusing when Add and Update actions work with it (because they obviously use the X-Algolia API key (shared headers)), but Delete actions from the backend don’t because they use the api_key from the top field. A hint in the documentation would be great!
