Hi @Tyler1, thanks for the reply and appreciation .
Let us check once again, and share the results asap 
.
Regards,
Zeroqode Support Team
Hi @Tyler1, thanks for your patience.
We have pushed an additional plugin update, that has added a list of additional extensions allowed.
To check changes, please upgrade your plugin to the latest version (Version 1.62.0: updated list of file extensions) and give it a try.
Regards,
Zeroqode Support Team
Wonderful!
Works perfectly now, thank you!
Hi, is the documentation for this deleted?
https://docs.zeroqode.com/wasabi-cloud-storage
I am trying to set up the plugin and can’t figure out what I am doing wrong, would love some official guidance.
Hi @ian11, thanks for your message and sorry for the created inconvenience with the supporting documentation.
We’ve recently migrated our docs, so please find the plugin supporting documentation available on: https://docs.zeroqode.com/plugins/wasabi-cloud-storage
Have a good weekend ahead!
Regards,
Zeroqode Support Team
1 Like
the delete folder function is not working.
Nothing happens - even tried it with sending the name of the folder static via your plugin.
Nothing happens…
In the doc is says it works same like with files - for files it works fine - but for folders not.
Hi @buero, thanks for your message.
We’ve tested folder delete case on our side and it is working properly.
Please make sure your setup is like the following:
- the folder should be placed inside the bucket
- the delete bucket action setup looks like this
In case this won’t help you please describe your case (here or on DM) in more detail and show us your setup screenshots.
Thanks and have a good weekend ahead.
Regards,
Zeroqode Support Team
1 Like
What is the delete success/error handling workflow? For example, my understanding it should be:
- Initiate a delete action on a file
2.Receive delete success (or error) event in another workflow
3.Act on the data from the callback event, such as remove the DB record or alert the user to the error, etc.
What I can’t seem to find is any information about the file that was deleted in the callback event via the wasabi element? For upload there is “last upload”, for retrieve there is retrieved files. What do I have to work with on delete?
Hi @andrew, thanks for your message.
For that, please use the following events:
Hope the provided hint helps. Please let us know if there is anything else that we can help with about our plugin.
Regards,
Zeroqode Support Team
Yes, I am using those. But the delete successful event does not provide any information about which file was deleted. I want to use the delete successful event to confirm before I remove the bubble record of the deleted file. Also, the Error deleting file event provides no info on which file had an error when deleting. If someone clicks delete on several files…which file had error? So back on my original workflow:
- Initiate a delete action on a file - This is no problem
- Receive delete success (or error) event in another workflow - This is no problem
- Act on the data from the callback event, such as remove the DB record or alert the user to the error, etc. - This is where i am stuck. The delete success event and delete error event do not provide any information on which event.
@andrew , thanks for the provided details.
We’re afraid that current plugin functionality doesn’t allow tracking certain objects in events (if a certain object is uploaded, deleted, etc.)
We’ve passed your request to the developer team, so they will check how feasible would be to add such an improvement to following plugin updates. Once any news will become available in this regard, we will let you know
Regards,
Zeroqode Support Team
Thank you, it will be important for any error handling for me
hi @ZeroqodeSupport ,
Thank you for your support as always.
I tested my app on a native app tester of air native for android in the below.
Then I’ve faced an issue that downloading a file from wasabi function doesn’t work on a native app tester. When I started a workflow of that plugin action, a native app tester went down suddenly.
Could you confirm this issue on your end?
Regards,
Miyazawa
Hi @mizawaya, thanks for your message.
We’ve passed it to the developer team for investigation.
Would it be also convenient to share (here or in DM) a link to your app page where the Wasabi plugin is used?
Once any results will become available, we will let you know asap .
Regards,
Zeroqode Support Team
1 Like
Hi @ZeroqodeSupport
Need your help.
Every time I use the workflow Upload file to wasabi from another cloud it gets this
Although I have provided the access key and shared key in the plugin.
Hi @waleed.mudassar, thanks for your message.
Please be sure that you’ve indicated Wasabi API Keys in both fields, following the supporting documentation guidance: https://docs.zeroqode.com/plugins/wasabi-cloud-storage#qd-how-to-setup
Hope the provided info helps. Please let us know if there is anything else that we can help with.
Regards,
Zeroqode Support Team
1 Like
Thank you got it working perfectly.
1 Like
Hello,
I need support for the error below that started to appear in my Bubble application when trying to access files hosted on Wasabi.
Thanks in advance and looking forward to advice.
Hi @webermarques, thanks for your message.
For a better understanding of your case, please share (here or in DM) a screencast (we suggest using the Loom tool) with the plugin element and actions settings. It will allow us to provide the required support much faster.
Also, following the shown error description, please check if the API keys have been correctly introduced, using the plugin supporting documentation:
No similar issues on our demo page has been identified:
Looking forward to your reply.
Regards,
Zeroqode Support Team
Hello,
Thanks for the reply.
Here for me, even on the DEMO page the error persists, I’ve already tried to clear cache and use another browser, the error is the same.
Here’s a link to the video made on loom.