Hi, @xttechnology!
Thank you for reaching out!
Unfortunately mentioned error is not reproducing on our side. Could you please provide us as more details, as possible?
For example OS/browser, screenshots of workflows and settings, steps to reproduce the issue so we could try and help you out better.
Thanks for understanding.

Unfortunately, this issue is not reproducing on our side by replicating your settings . In order to help you better we’d need more details on the issue, like the step by step how to reproduce, browser/os, console.logs, workflow /setup.
Also please check our demo editor here: https://bubble.io/page?type=page&name=fuzzy&id=zeroqode-demo-16&tab=tabs-1 to preview the plugin settings and see how the plugin works and try to replicate it.
Hope this helps.
Regards, Julia.

as the element “Search&Autocorret” is connected to the element “Input Search Flight” then the field “Input box ID” : https://prnt.sc/spg4qi should be similar to the “ID Atribute” : https://prnt.sc/spg3hm , please check these settings too.

Please make that both plugin element and RG/inputs are in the same Group Container.

Hello @julia.minacova, thanks for your assistance! I changed my mind, I need it fuzzy because the database will be filled with files so it is useful to do fuzzy search. It is working properly and doing its purpose. However, there is a downside when I changed the type of the RG. Usually when I upload many files per log, each file will be in a separate cell of the RG. But now all the files are in one cell of the RG. Is there a way to fix this problem? Also if I click on that cell that contains many files, they are not opening. It is opening all of them in one tab as you can see in the URL of the tab.

To help you with your issue better, can you please provide more details of your setup, like screenshots of Plugin element settings, database, workflow etc.
Also the result that you’re getting when searching through db entries.

So, I analyzed provided screenshots. Let me give you some insights that might help you. RG has to have the same type of content you are going to display. In your case it should be file instead of posts.
Also, in order the search to work properly, there should be the field of type text which the plugin will be able to process and find matches - so there is a need to restructure your current DB a bit.

First: I would suggest you create the separate table in DB called, for example “File”, and it should contain two fields - 1) field name: attached_file (type file) and 2) field name: file_name (type text): https://prnt.sc/stsrfk .

Third: in the WorkFlow you are creating your post, the second step should be “create a new File” and on the third step you need to add just created file to the post you just created: https://prnt.sc/stte3r .

Also, make sure that you didn’t missed the Third step that I mentioned in a previous mail.

Just in case: Third: in the WorkFlow you are creating your post, the second step should be “create a new File” and on the third step you need to add just created file to the post you just created: https://prnt.sc/stte3r .