Hello, is there a way to get a progress % output from the “Download File” action? Right now when my files are large, when you click download it just sits idle and you can’t tell anything is actually happening, but after awhile the file just finishes downloading instantly.
Also could you put on the suggestion list to support multithread downloading? Meaning it requests the file in multiple parts then stitches it all together for much faster speeds?
Thank you!
Also is there any way to rename a file or folder?
Also folders don’t display correctly, their type is just undefined and don’t report a name or anything. How do people handle folders with this plugin? I would want to show folders then you click on a folder and it changes the uploaders data source to the folder you clicked. (similiar to google drive for example). Thanks!
Where can I get some help to implement wasabi into my file upload work flow it keeps giving me errors can anyone help me please ?
Hi @tylerboodman, thanks for your messages.
Regretfuly, the progress bar can be used only for the upload process. The download process depends on many factors that the plugin can’t consider ( network bandwidth, device capability, file size, etc)
Unfortunately, the Wasabi platform itself is not supporting such an option (multithreaded downloading), thus, such a feature would not be possible to implement so far. Sorry about that.
Please use for guidance and setup examples the plugin:
As an additional source of examples, you can check other available editor pages (both live and development versions), we’ve tried to reproduce the most frequently asked cases there:
Hope the provided information will help. In case there will be any persisting issues, please let us know within this thread 
Regards,
Zeroqode Support Team
I’m having a strange issue. On “Page A” I have the Wasabi S3 element so I can upload files, and for that one I have a specific folder path. Now I have another Wasabi S3 element on “Page B” with a different file structure, and when I click on it to upload it doesn’t do anything. If I go back to “Page A” and click on the uploader it works, then I go back one more time to “Page B” and click on the uploader then it pops up the window to choose files. Any idea why? Hopefully multiple uploaders per Bubble app are allowed?
I’ve tried deleting the uploader on “Page B” and dragging in a new one, but the same behavior happens.
Hi @tylerboodman, thanks for reaching out.
We’re afraid that without additional information (screenshots or screencast of the plugin settings and workflows), it would be difficult to identify any possible issue that occurred on your app.
Please share a bit more information. For screencast - we suggest using the Loom tool.
Looking forward to your reply.
Regards,
Zeroqode Support Team
Okay let me follow up with more information once I test some more things. Just to confirm this plugin can have multiple uploader elements in the same app right? How about on the same page?
Hi @tylerboodman, thanks for your reply.
Yes to both questions. As an example - you can check the plugin demo page, where we have on one page several plugin elements, and on additional testing pages - some setups and plugin elements too.
Have a good day!
Regards,
Zeroqode Support Team
Hi, @ZeroqodeSupport. We’re using your plugin for about 4 months. Recently we have been experiencing some issues when trying to view some pictures that has been succesfully uploaded to Wasabi. The issue is that some pictures takes too much time to load on the page, and when we right-click the image and try to open it in another tab, it shows a Download pop-up instead. It happens only with some pictures, not all of them.
Do you have any idea about what it could be?
Thank you! We look forward to a reply
Okay, I just tested it out some more and figured out what the bug is. The file structure for the Wasabi S3 uploader element has dynamic values in it. Mine for example is "Locations/{current pages unique id}. When the page loaded it must load the Wasabi S3 element before the page even has the unique id loaded? When it wasn’t reacting to my clicks, I could manually refresh then it would work.
I made the Wasabi S3 element hidden on page load, then set up a workflow so “On Page load” it schedules a custom event after 5 seconds, the custom event shows the Wasabi S3 element and it’s working as its supposed to. Could you guys test this and see if you’re getting the same result? Have the Wasabi S3 element use the “Current page’s unique ID” in the folder structure and have another page send data to the page with the S3 element.
Thanks.
Hi @caiohm.comercial, thanks for your message.
Unfortunately, the plugin can’t influence the file loading speed or file opening, as this part of functionality relates already to the Wasabi Storage platform.
For reference, you can check how the plugin is set up and is working on our plugin demo page.
Also, such a use case may be possible if you are uploading files in Base64 format, in this case, yes, it can retrieve it as a downloadable file.
Please let us know if there is anything else that we can help with 
Hi @tylerboodman,
To have it working properly, you can also use the following setup:
Hope the provided hints will help. If there will be any other questions that we can help with, please let us know.
Regards,
Zeroqode Support Team
Okay perfect, I will try that out. As long as you guys know about this happening and there’s a workaround for now. I should be good on this issue.
Also in the demo editor for this plugin you guys seems to always have a “Retrieve files” button that the user has to manually press. I’m looking for it to automatically retrieve after any uploads/deletions (kind of like Google Drive).
Right now I have it retrieving after upload, delete, etc. Just in case it misses it somehow I have it scheduling a retrieve every 5 seconds. Does that sound like an okay way to make sure a repeating group has the latest files retrieved automatically?
Thanks!
I just tried the conditional format method to show the uploader element and it’s still doing the same thing. I also tried “When condition is true” event in the workflows and did the same conditional statement to show the Wasabi S3 element but it still doesn’t react when I click to upload. I think it’s all just happening to quickly and somethings going wrong. I used the same conditional statement but scheduled a custom event to show the Wasabi S3 element after 1 second and that works no problem. Please just look into this but I can work around it for now. Thanks so much.
Hi @tylerboodman, thanks for your reply.
Please check if you are using the right events for triggering workflows:
To be able to identify an issue in your case, please share a screencast with the use case workflow & settings setup and how the issue looks on the page
Looking forward to your reply.
Regards,
Zeroqode Support Team
hi @ZeroqodeSupport
It seems I’m facing an error on the function Upload File To Wasabi From Another Cloud. Internal Server Error.
I’m using Pad & Signature plugin provided by Zeroqode, and what I want to do is to upload the signed image to wasabi, but I couldn’t find the way to do that directly.
So I planned to upload the image from Pad & Signature plugin to my bubble storage (aws) once, and upload that image to my wasabi bucket using Upload File to Wasabi from Another Cloud, with the below workflow.
The given url for the file uploaded on my bubble storage (aws) starts from (//s3…) omitting https: so I added it to be able to refer properly. But it didin’t work.
I saw the past communication discussing about the error on this function but I couldn’t confirm if it’s solved or not (it seems some updated made on plugin - my wasabi & pad & signature plugin both are latest by the way)
Hi @mizawaya, thanks for your message.
Please note that for your case, you also need to indicate the API keys in plugin fields related to the “upload from another cloud” option.
Hope the provided hint will help. In case the issue will persist, please let us know.
Regards,
Zeroqode Support Team
hi @ZeroqodeSupport , thanks for your quick replying.
Copied same access/secret keys like below as you mentioned but still same error continues - internal server error. Just in case I did it to other dev fields but the result remain same.
I’m trying to upload a file stored on bubble storage to wasabi bucket (and that file is public) - is there anything I’m missing??
Regards,
Miyazawa
Hi @mizawaya, thanks for your reply.
We’ve checked once again, and a solution in your case would be to modify the workflows in the following way (divide the workflow shown above into two separate flows):
Hope the provided hint will help. Please let us know if the flow is working properly now or any other support is required.
Regards,
Zeroqode Support Team
hi @ZeroqodeSupport ,
Thank you very much for your instruction.
I tried it, divided the workflow as instructed, but still, a file couldn’t be uploaded to my wasabi account.
I checked the error message for this wasabi uploading action, picking up values like below workflow and I’ve found the below messages only for body and returnened_an_error. Confirmed other fields are empty and internal server error description is gone.
Body: Access denied
Returned_an_error: No （いいえ）
Is there anything you can assume about root cause from the above values?
Regards,
Miyazawa
Hi @mizawaya, thanks for your reply.
We’re afraid that for a better understanding, a bit more details are required. Please share (here or in DM) a screencast (we suggest using Loom) with related workflow, data type setup (if any privacy rules are applied), and use case (with opened browser console).
This will allow us to identify any possible issue much faster.
Looking forward to your reply.
Regards,
Zeroqode Support Team
