🛠 ᴺᴱᵂ ᴾᴸᵁᴳᴵᴺ Wasabi Storage Dropzone & Utilities (Image Resize & Compression, MultiUploader, Folder support & No Filesize Limit!)

Showcase Plugins
101

@proteuscrypto, have you managed to resolve your issues?

I believe that the new “Uploaded File Loop”, which triggers after each successful upload, would allow you to use the “Set File Public Access” action which returns the permanent URL for your marketplace.

Feel free to refer to the demo editor for implementation example.

102

hi yes … thank you very much for the support.

103

@redvivi I’m getting this error message…can you help please?

Screenshot 2022-11-04 at 16.28.23
Screenshot 2022-11-04 at 16.28.23922×848 117 KB

104

Hello @LA81638 ,

This is due to node js 14 engine upgrade combined with version misalignment on Bubble platform.

Please upgrade to the latest emergency fix version. The error should be gone.

105

Would this only work once deployed? Have upgraded on dev site, but still not working:

Screenshot 2022-11-04 at 16.51.04
Screenshot 2022-11-04 at 16.51.041952×100 6.06 KB

106

There should be an upper version.
Try refresh the page or wait a few minutes.

107

Amazing! Thank you. Incredible customer service once again *****

1 Like
112

Also, When I hide the Dropzone’s parent group, then reshow it, the Dropzone becomes unclickable. It lets me drag files on it still but clicking doesn’t do anything. What’s the best way to diagnose it and share with you a possible cause?

113

Hey @tylerboodman !

Can you please DM a loom with reproduction steps and ideally access to a page to reproduce the issue?
It would be helpful if you could loom for each problem, it will be easier for me to schedule the fixes.

Thanks!

114

That sounds odd but plausible. Usually I use as input parameter of the second action the output of the first to create a sequence for sure.
Not ideal but may be worth trying.

Look at the logs to check the input parameters and conditions status for any error.

115

Is there any tips on improving the speed of the first upload? Had a few complaints from users about length of time so was hoping there may be a fix?

116

It is directly linked to the usage of your app. If the request is still in Bubble cache, it will fire in less than a second.

Otherwise, there is nothing to fix. It is due to Bubble’s backend performance and plugin architecture emphasized on security.

117

Thanks for quick reply :slight_smile: sorry my inexperience doesn’t quite understand…being in bubble cache, I’m assuming that’s what I’m in most of the time and it usually takes around 5 seconds for me. Is there something I should do differently?

118

Not really, users have no control over the caching system through the implementation.

Nothing that can be done on this as it is platform related.

1 Like
119

Oh ok, I see. Thank you, I’ll make the few seconds a bit more entertaining, am sure that will keep them happy :slight_smile: thanks for your reply

120

@LA81638 Yea I asked the same thing, it’s a limitation with Bubble right now it has a “cold start” where it needs to fire up all the scripts again if they haven’t been used for a while. As far as I can tell it only lasts a few minutes with no activity before it has to do it again… It’s at a server-level though so if one person uploads, then it is fast the next people for a while.

Maybe will get better in the future :pray:. @redvivi Maybe Node 16 could improve it?

For now if you google “CSS spinners” they are spinning loading animations, I just show one along side some text saying “Starting upload” and have it only show when the Dropzone's file:count > 0 and the total progress is 0 to distract the user a little bit. It helps if you don’t need any other Wasabi-related actions afterwards like “Set file public access” or anything because that also has a cold start of its own.

121

@redvivi Looks like when uploading files with # in the name through the client-side Dropzone is also results in a broken link (not encoding it?)

122

Characters to avoid

Avoid the following characters in a key name because of significant special handling for consistency across all applications.

  • Backslash ("")
  • Left curly brace (“{”)
  • Non-printable ASCII characters (128–255 decimal characters)
  • Caret (“^”)
  • Right curly brace (“}”)
  • Percent character (“%”)
  • Grave accent / back tick (“`”)
  • Right square bracket (“]”)
  • Quotation marks
  • ‘Greater Than’ symbol (“>”)
  • Left square bracket (“[”)
  • Tilde (“~”)
  • ‘Less Than’ symbol (“<”)
  • ‘Pound’ character (“#”)
123

Got it, I thought maybe it was that same issue you needed to fix with the Copy File action. You recommend find & replace on the name on the upload action? Windows lets you do some of those symbols… Maybe put that in the documentation if that’s what we should do

124

Either reject the file based on specific characters, or silently replacing those characters.

It mostly depends on your user’s tolerance to thing happening behind the scene.

2 Likes