☁️Wasabi Cloud Storage Plugin

Hi @phetxdphet, thanks for your reply.

A possible solution, in this case, would be to use a custom state. For example, on page load, it can get a value that is unrelated to the Wasabi plugin.
And when the plugin element is used - it gets other value.

Hope the provided advice helps.

Have a nice day!

Regards,
Zeroqode Support Team

1 Like

Hello! I’m trying to set this up, and I have followed your example. Although I can’t view the files at all. I set them as private at the upload stage. Is this the correct way to do it?

If I don’t set them as private I can still open them in the browser even with the policy set as described. Any advice on this? Thanks

Hi @nemanja.rilakovic :wave:

You must turn your file public in order to make the privacy policy work as expected!

Can you share more info about it?
What is the policie code you used in your Wasabi console?

2 Likes

Hi @nemanja.rilakovic, thanks for your message.

Allow us to recommend checking the plugin supporting documentation: https://docs.zeroqode.com/plugins/wasabi-cloud-storage#use-cases, where we indicated two cases, including the one advised by @rpetribu

Hope it helps. In case any issue will persist, to be able to help you faster, please share screenshots or screencasts of your setup and achieved results (here or in DM).

Regards,
Zeroqode Support Team

1 Like

thanks @rpetribu and @ZeroqodeSupport, now I have managed to make it work!

I have one question. If I have a datatype called “Post” which is a post that can have one or several images or videos. What is the best way to attach those files to posts and then load them in when someone opens the post to view it.

Should the files be attached just as S3-links, directly to each post and can they be loaded this way as images/videos or is it necessary to use the “retrieve” action?

What is the best method to get this done also with privacy in mind, so that the files are not publicly accessible, but only to the ones that have access to view the posts.

Thanks!

1 Like

Hi @nemanja.rilakovic, thank you for your question glad to hear that provided advice helps.

We would recommend saving uploaded files S3 links directly in the database (in Post datatype), this way, there will be no need to generate anything. This way, each post will retrieve links to saved files from database.

Hope the provided advice helps. Please let us know if we can help with anything else related to our plugin.

Regards,
Zeroqode Support Team

Hi,

I have a problem with “rename files” when allowing to upload and image to Wasabi. Whenever i put “yes” and using any dynamic data (including creating random strings), the image saved to Wasabi could not be previewed inside a browser and it pops up a download to PC instead.

When i do not use the “rename files”, the images is viewed nicely in Wasabi. Somehow i researched that by using “rename files” it strips off the Content-Disposition (inline) in the images. Is this correct and how do i rectify this?

Hi @ivanckw, thanks for reporting this issue.
Would it be convenient to provide a bit more additional details on the matter? A screencast or screenshots with the plugin setup and use case would help us to identify the case much faster.

We’ve already passed it to the developer team for investigation but still any additional information is welcomed.

Regards,
Zeroqode Support Team

Hi @ivanckw, thanks for your message.

The developer team has investigated the reported issue, and found out that the cause might be the following:

  • the problem is in the speed of image processing. Before displaying an image, the Wasabi platform needs to process and store it first on its side.

As a solution (for picture display), we recommend using the preview feature:

Hope the provided hint will help. In case there will be any other plugin-related questions, just drop a message here :slightly_smiling_face:

Regards,
Zeroqode Support Team

1 Like

@ZeroqodeSupport Hello! Is it possible to add the ability to upload an image from a link to the plugin? To be able to start loading images from the list in the database in the backend workflow

Hi! I’m researching alternative storage services for my bubble app and came across this promising plugin. Read various comments made by @rpetribu to @Alter345 regarding the Wasabi access management. I have a similar requirement.

My app is built with multi role functionality (particularly, with specific privacy rules for certain things). Thus, for some user roles, files marked as private on upload and attached to things to which Bubble’s privacy policies don’t grant access are restricted.

After reading this thread, my guess is privacy configuration is limited to allow any logged in user in my app to access the files as long as they have a file link and click/request the file from within the app.

At first glance, this doesn’t match my requirement but have a workaround in mind.

When using Bubble’s default storage to upload “private” files attached to something, the URL stored in the app is not the usual S3 link. Instead, bubble saves something like these https://[appname].bubbleapps.io/version-test/fileupload/f[somerandomID]/filename.ext.

When running the app, if the user complies with the thing’s policies, an S3 link is generated and the file made available, but with expiration and signature.

I wonder if some flow of this sort can be recreated using the workflows provided with the Wasabi plugin, or perhaps, included in the plugin in the near future?

@rpetribu @Alter345 have you guys implemented this variant?

Here are key thread posts.

http://forum.bubble.io/t/wasabi-cloud-storage-plugin/124862/304

http://forum.bubble.io/t/wasabi-cloud-storage-plugin/124862/339

Hi @krasab, thanks for your inquiry.

If we understood right, the image, in this case, is stored in another storage first, then, uploaded to the Wasabi Cloud storage with help of our plugin.
If it is so, please use the “Upload file to Wasabi from another Cloud”. For guidance, please use the related plugin:

If we understood you wrong, please add more details to your inquiry.


Hi @AAL, thanks for your message.

The described use case is a pretty custom one, so, unfortunately, we can’t provide many details on how that could be practically realized, as it would be beyond our responsibilities as the support team. Sorry about that.

Theoretically, this might be realized, by combining the current plugin features and the Wasabi platform functionality.

Please let us know if we can help with any other plugin-related questions.

Regards,
Zeroqode Support Team

1 Like

I understand, I might subscribe for a month and try out. Thanks!

1 Like

@AAL Hello there ! Sorry, i haven’t seen you mention :wink:
thanks for writing
regarding your thread, i haven’t tried your solution ;( so i can’t help you
if i have some future info, i’ll let you know
thanks !

I’ve managed to workaround my requirement with the plugin. Seems promising. Now I have a question. How do you recommend setting up the bucket and folder structure?

I was thinking of copying Bubble’s set up, as it seems to fit any or most of situations. Here an example.

https://s3.amazonaws.com/appforest_uf/[file unique id folder]/[filename].[extention]
where appforest_uf is a generic bucket for all files (or at least that is my guess).

Got a bug when trying to upload a base64 file.

image

Hi @AAL, thanks for your message.

This would depend on your particular project requirements, so unfortunately there is no general solution or advice for that.

This is noted, we’ve passed it to the developer team for investigation. Once any news will become available, we will let you know asap.

Regards,
Zeroqode Support Team

What does the Element’sreadystate mean? Ready/Initialized for upload? download? Ready for what?

Hi @AAL, thanks for your question,
Would it be convenient to add a screenshot with an example where the Ready state is used?
This will allow us to provide a much more detailed answer.

Looking forward to your reply.

Regards,
Zeroqode Support Team

Hi @AAL, thank you for your patience.

Our developer team investigated the reported error and the plugin elements and actions are working properly on our side.
Below we would like to share a few points that need to be considered on plugin setup.

  • please be sure that Wasabi S3 element is placed on the page
  • if the element is present on the page, please be sure that it is not hidden (if it is a project requirement to have the Wasabi S3 element hidden, you need to make it visible on the page load, and hide it by a workflow that starts with “When page is loaded”).

Hope the provided hint will help to solve the issue. In case there will be anything else that we can help you with, please let us know.

Regards,
Zeroqode Support Team

1 Like