Would it be possible to create a bucket from a backend workflow? We would then use it with a database trigger (f.e. when new company is created, create a new bucket).
Currently, there are no significant updates regarding the upload issue on iOS. Our developers are diligently working on it. Rest assured, we’ll notify you as soon as we have a resolution or any new information!
Regarding the request for a new action to create a bucket, I’ll discuss this with our development team and get back to you with more details as soon as possible
@ZeroqodeSupport The filename filtering is an incredibly important function to me. I was the user who originally paid the prior builder of this plugin to add it. But, I’ve noticed that the plugin REALLY struggles with more than ~ 200ish filenames. Is there anything we can do to make this function more efficient? The plugin seems to work well aside from this issue, but when it freezes because of this issue, it really degrades the experience.
To better understand and address the issue, could you please provide more detailed information about when the freezing occurs? Specifically, we’re interested in knowing what types and how many files you’re attempting to upload, the length of the filename filters, and the device, operating system, and browser where this issue arises. Any additional details you think might help us are also welcome
We’ll pass this information on to our developers to recreate the behavior on our end and to determine if there’s a way to enhance the efficiency of the process.
Feel free to share these details either here on the forum or via email at support@zeroqode.com.
We’re following up to see if the issue you were experiencing has been resolved or if it persists. If you’re still facing the problem, could you please share the information we previously requested? This will allow us to delve deeper into the matter.
Thanks for the reply! Working on setting up a little demo and recording a screenshare so you can see all the details. Might take me a little bit to pull everything together.
Also, I wanted to flag a separate issue with the plugin: If auto-submit is set to yes, then the files count state doesn’t get set until after the upload has completed. It use to work where the state would get set to a value and then the upload would begin, but doesn’t seem to work that way anymore. Switching auto-submit to no resolves that issue, but means I have to build an extra step or two for my users when they’re used to it just uploading automatically.
Apologies for the delayed response over the weekend .
We’ve provided more details in the direct message (DM) conversation we have ongoing. Let’s continue our communication there to avoid any double messaging and confusion.
Uploads are failing for video files. Anything larger than about 30MB, which is nothing for video. Failing on my app and on the Zeroqode Wasabi plugin demo site.
Regarding your first message, we’ve added a new action in version 1.108.0 that allows users to create buckets directly from the plugin.
Regarding your second point, another user has reported a similar issue, and we’ve opened an investigation. Currently, the developers suspect that the “generate previews” feature might be contributing to the problem as it generates base64 data for videos and images.
We’ll keep you updated as soon as we identify the cause and find a solution for this!
Our developers have identified the cause of the crashes you’re experiencing on your side and on the demo page. It appears to be linked to the “Generate Preview” feature. When uploading large video files, the plugin converts the video into base64 code, which can be quite extensive. For instance, a simple image’s code is long, but for a 70+ MB video file, it becomes enormous.
The crashes occur because the browser runs out of RAM to handle this process. In our tests, just one tab used over 8GB of RAM after selecting the video file.
Could you please disable the “Generate Preview” option and test it again? We would love to know your feedback!
My users upload files using the SSE option because the files contain sensitive information. However, a feature I am trying to build would require the generation of presigned URLs. The generate presigned URL action does not allow me to transmit the SSE key, so the presigned URLs that I receive do not work. Is it possible to get working presigned URLs for files that were saved using SSE?
We will forward your request to the developers to check if it would be possible for the “Generate Presign-URL” action to accept SSE keys. We will keep you updated with more information as soon as it becomes available
If you have more questions in the meantime, feel free to reach out to us at any time!
Upon reviewing your request, our development team has confirmed that, unfortunately, it is not possible to generate a preassigned URL for an encrypted SSE file.
If you have any other questions about plugins or suggestions for improvements, please don’t hesitate to reach out.
I have created a bubble app, in which users can upload files and store them. (I am using the wasabi bubble plugin for this)
Now, when people upload a file, refresh the page and try to download it, the console says “Action Download File Wasabi S3 A - Missing credentials in config”. The weird thing is: if they now upload a new file, the error is gone and people can download all their files. If they then refresh the page, the error occurs again and people can’t download their files.
To sum it up: you can only download your files if you uploaded a file during that session.
Thanks so much for your message. We are sorry to hear about this behavior
Could you please send us some screenshots of how you configured the Wasabi element and how you are trying to download a file (including the workflows related to it)? This will help us recreate a similar use case, reproduce the issue and get to the bottom of it!
This is a friendly reminder regarding our last message. We’ve conducted additional testing and were able to download files without needing to upload a file first.
Could you please provide the requested information so we can assist you further?
Thank you for the great plugin here. I have been a long time user.
I want to provide access to my files to some partners I am working with and for that I know I will need to modify my bucket policies to add the domain/IP they access from.
Can you please confirm the functioning of the 2 use cases you mention in your documentation as they seem exactly the same to me?
Restrict access to the bucket (allows access only to application visitors).
This is intended to provide access only to application visitors (so people opening files from my app), coming from other app, or web, or pasting in URL does not work.
Restrict access to the bucket (deny access to all except the application visitors).
Deny access to all except app visitors. Isn’t this exactly the same as stated in use case 1?
At the moment I use the configuration from case 1, so I assume i will be able to add their domain/IP here:
Thanks so much for using our plugin and for reaching out to us .
The two use cases we share in the documentation are similar in functionality. Both policies provide access to authorized web pages. The only difference is the complexity of the code, with the second one allowing for more security and additional functionality.
Feel free to use the first policy we provided and customize it to suit your use case!
Hope this helps, and if you have more questions, feel free to reach out to us at any time .
I discovered an issue with the 1.105.0 update that added encoding for special characters in file names.
After this update, my customers report “strange” characters in file names when downloading using the zip function (bubble plugin). Print attachment where the “space” in the name of the file uploaded using version 1.105.0 is
replaced with “%20”.
Another file uploaded with a previous version does not experience this problem.