Please allow me to mention that currectly, our plugin encodes the title of the files, which contain the special characters: - _ . ! ~ * ’ ( ) and spaces sometime. Unfortunately, the encodinch of such files is the only way for being defined by the AWS bucket.
In order to prevent the download being cancelled, all invalid characters are replaced by “%” .
Plugin returns you not the name of the file from the bucket, but the original name of the file.
Please check this documentation in case of necessity: encodeURIComponent() - JavaScript | MDN
In case you are meaning another case, please provide me as many details as possible regarding it: screenshots of the settings, an exact way to reproduce the issue ans etc.
Thank you for the reply! I think there are two things here:
Is there a way to change the filename before uploading? Ideally I would not want ‘%’ signs in filenames and simply delete special characters. Or could I just ignore the filename and give a random name?
The problem I was having was a different one: After using the File Uploader plugin, the resulting file has the two system defined metatags that I showed in the image above. For a downstream calculation the first one is not acceptable as it prevents me from using lib curl to access the file. I know that giving a content encoding during upload is an option when using AWS utilities (as shown in the stack overflow post) and is not a defaulted to base64. Thus my question: Why is the Content-Encoding set to “base64” I’m my image above (like I said, this doesnt happen when I upload the image with any other AWS tool except the zeroqode fileuploader)?
Hello, @majako91
Thanks for the questions regarding the plugin.
This is the method of the work of the plugin. The unique way to ignore the “%” character, is not to use any incorrect symbol in the file’s title.
You can manually verify and rename all the files, but we can’t prevent the mentioned symbol in the file’s name in the bucket.
In order to provide you a response to this point, I need to consult with our developers. Once I will receive any feedback - I will let you know.
Hello, @majako91
Thanks for your patience and sorry for my late reply.
Just for our note, can you please let us know if the link, which should be returned by the plugin in the Bubble Application works? We need to understand the functionality you are trying to implement.
As for your issue with the MetaTags, please allow me to mention, that our plugin does not affect this functionality on AWS.
Seems, like this issue appears due to the fact, that you are trying to connect the bucket with a third party ( as you mentioned earlier). So, the files are uploading to your S3 bucket, but after it, you are trying to connect the bucket with another platform.
Unfortunately, we can’t affect the behavior of the AWS and any third party, because it is not related to the plugin functionality.
In case I have not understood you correctly, please provide more details regarding your problem and the moment of occurrence.
Thank you for your help! We solved both issues by implementing our own endpoint the is called after an upload which converts the image and decoded the filename.
