Services Plugins FAQs

Wasabi plugin error

Received this error. Been working fine for probably a year

plugin evaluation error The plugin Wasabi cloud Storage / action Reset File Uploader a Wasabi S3 threw the following error: TypeError: t[_0x1227c1(…)][_0x1227c1(…)] is not a function at eval (PLUGIN_1602732136092x484352338159730700/Wasabi-cloud-Storage-element_action–Wasabi-S3-Reset-File-Uploader-.js:3:2412)
please report this to the plugin author)

1 Like

Hi, @brfriedman

Thank you for your message and sorry for the delayed reply over the weekend and past Christmas holiday. :christmas_tree:

We’ve carefully tested the plugin demo page (link here) and couldn’t reproduce the error on our side.
To understand better what went wrong inside your app with our plugin, please share the following information as:

  • Plugin Version: Please confirm the version of the Wasabi Cloud Storage plugin you are currently using.

  • Plugin Action Details: Specify the action within the plugin you were using when this error occurred.

  • Workflow Description: A brief description of the workflow where the error is occurring would be greatly appreciated.

  • Element Configuration: Details about your configuration of the plugin element.

This information will help us better understand your use case and check the issue.

Thank you for your cooperation and patience. Looking forward to hearing from you soon. :pray:

Best regards,
Stephan

I went to the pages that have the Wasabi element on it and errors just opened up. It appears you put the access key and secret key on the element even though its set at the plugin level? Seems redundant.

Seems like I have to go to all the Wasabi elements and add the keys into the element now?
2024-01-03_15-27-13

Im now on version 1.102.0

Hello @brfriedman,

Thank you for your question.

“It appears you put the access key and secret key on the element even though its set at the plugin level? Seems redundant.” - Yes, you’ve correctly noted the requirement to insert both the access key and secret key at both the plugin and element levels. This update, introduced on “23.10.2023 - Version 1.97.0”, was done for security reasons as some of our users reported that their API keys were visible in browser console. By inserting the keys into the plugin element, it removes the chance of displaying them in the console.

We apologize if this change led to any confusion or errors in your experience. :pray:

For additional guidance, please check the plugin supporting documentation and the demo editor page.

Thank you for your understanding, and let us know if you have other questions, we will gladly assist you. :slightly_smiling_face:

Best regards,
Stephan

@Stephan
What do you mean with “lowers the chance of displaying them in the console”? So it is basically absolutely unsafe to use it because anyone can see the API keys and access all of the data with it?

1 Like

Hello @rhabarberling,

Thank you for reaching out.

We’ve been diligently testing various solutions to ensure that the keys are not visible in the console. Initially, we tried incorporating them into the plugin element and using temporary keys. However, due to Bubble’s design, all element fields are visible in the source file it generates.

We are currently developing an update that will completely obscure the keys, and we expect to have it ready for your review soon.

Thank you once again. If you have any other questions or need further clarification, please feel free to contact me.

Have a great weekend ahead!

Best regards,
Stefan

Was this fixed @Stephan ?

1 Like

Hi @rhabarberling :wave:,

Thanks for your message.

We have update the AWS File Uploader plugin, now at version 1.187.0. This version introduces new Beta actions and elements to enhance security while preserving existing functionalities. These changes address previous concerns about visible keys with a new, secure setup.

New Setup Highlights:

  • Previous Setup: Add elements and AWS keys to your app, customize, and use file URLs.
  • Beta Features Setup: Add elements, set up “Generation URL” events, and use new actions for secure URL generation and file uploads.

Beta Feature Changes:

  • Updated GUI and NoGUI elements for the new flow.
  • Replaced “S3Objects” with “Get All Files” action.
  • “Delete Files/File (backend)” remains for secure deletions.
  • Documentation updated with setup instructions. (We’re also preparing a demo page!)

These features are still in Beta, and if you’ll have any questions or came upon any problems please report them at support@zeroqode.com to help us improve.

Thank you once again looking forward to your reply.

Best regards,
Stefan