Thanks a lot @fabrice.latour04
Looking forward to those accents.
Have a nice day.
I am having the exact same issue now when attempting to use the nested field option. Copied settings from your demo but still receiving the TypeError similar to Zavitac. Are you able to assist me in resolving this issue?
Thanks! Sorry for my very late response!
The color wanted was #449EDA, to get a similar one (by try and failure) I had to set #185A66.
I tried again with the new version, but I get the same trouble.
Thanks for your effort on this.
Thanks, great! I checked that in the last version is already working nicely.
Yes, I was using the Event to save it in a custom state Yes/No, but it was just setting Yes when the first data is loaded, but not for every change in the source (conditionals changing the data source). The workaround I used was preloading in a search element, and using here the Event to set the custom state.
Now I tried the Exposed data “Data source loaded”, thanks, this is lighter because it does not need the Event (to save it in the custom state). However, I still need the workaround of preload search element, because once the “Data source loaded” value is set on Yes in the first load, will always keep Yes even if the data source changes.
Also, I think I noticed an improvement if the plugin, now preloads all the data even if the conditionals have not been triggered yet ¿?
I was using the mentioned workaround (preload in a different search element) for doing this, it would no longer be needed as far as I see, except for the “Data source loaded” trouble I mentioned before.
- Deprecated/Removed: The search option Allow typo. This was impacting too much performance for Long input words x Long targets;
Pitty, I found that useful. Maybe it can be kept to be used in not too long inputs (names, title, etc.), with a warning in the editor, to notify users to not use this in large inputs.
Though maybe I’m not understanding this completely, how works the “Search threshold” in relation with this?
As other mates mentioned before, my opinion is that speed is the top priority in this matter (loading data/searching).
Though the feature for accents insensitive you are working in, will be great too
Thanks, awesome work!
Pretty amazing plugin @fabrice.latour04 ! Works like a charm with Bubble data.
Trying to make it work with data coming from an API (another Bubble app as a matter of fact), but without success. Do you have any setup examples for API data?
I’m getting the following error:
How do you configure the fields into which the search is supposed to happen? The search fields disappear when using API data as a data source.
Very nice plugin!
Is it possible to combine several quick find elements to achieve more than 8 fields search? i can see that it can search only 8 fields.
And the RG data source would be: quickfind_1´s data merge with quickfind_2´s data and so on