AWS File uploader - Wrong file url using prefix

[alexandre.boulme]

I’m using the “AWS File uploader” with a the “add prefix” option, but I get a wrong url where the prefix is written twice :

Here is the configuration of the element :

The url I get is the following :
“https://xxxxxxxxxx.amazonaws.com/payslip_month/1655297182307x765525130185196700_payslip_month_3__1655297182307x765525130185196700_payslip_month_3__Picture7.png”

Where “1655297182307x765525130185196700_payslip_month_3__” is the prefix, when the right url should be : “https://xxxxxxxxxx.amazonaws.com/payslip_month/1655297182307x765525130185196700_payslip_month_3__Picture7.png”

@Ecaterina any help would be appreciated !

[Ecaterina]

Hello, @alexandre.boulme
Thanks for reaching out and sorry for the trouble.

I need to highlight a few things about the prefix:

• the uuid_ format prefix will always have a constant length of 36+1 = 37 characters, while for the prefix with the zq_random format the length will vary;
• filenames prefix - custom prefix to add to file names; is applied only if the ‘Add prefix to filename’ checkbox is checked.

In order to help you, I need to understand why you are using the prefix twice. Usually, it is not possible to use it twice and make the URL workable.

Also, can you please let me know if these files are uploaded to your AWS bucket and you can open it?

Looking to hearing from you soon.
Best regards,

[alexandre.boulme]

Hi @Ecaterina,

I’m not sure to understand. I don’t want to use it twice, but maybe my configuration is wrong and I’m doing it ?

What I want to do : use the “folder_name/filename_prefix”, in my filename_prefix I use dynamic value which lenght vary. Is my configuration (on the screenshots) fine compare to what I want to do ?

The very first screenshot is a condition that changes the filename_prefix value if needed.

The problem I have is that the file uploaded correctly toe the S3 (with the right name including the prefix) and I can open it, BUT the “File URL” returned is : “https://S3adress/foldername/prefix_filename|prefix_filename|picture_name” (the | are not in the url, it’s just to make the example readable)

When the url of the file is “https://S3adress/foldername/prefix_filename|picture_name”

Tell me if I’m not clear or mistaking on something ?

[Ecaterina]

Hello, @alexandre.boulme
Thanks for the detailed explanation.

Please allow me to recommend you to remove your conditions from the Plugin Element:

Usually, adding the prefix is performing only in the plugin element, not in the condition.
Thus, please try to remove the Conditional part and let me know about the result.

Best regards,

[alexandre.boulme]

Hi @Ecaterina,

Sorry to the late reply, I just tried and it doesn’t work. I still get the prefix twice in the url …

Example of url with this config :
“https://xxxx.s3.eu-west-3.amazonaws.com/selfie/1656061334815x891631087512079000_selfie_1__1656061334815x891631087512079000_selfie_1__Capturedecran20220624a10.44.20.png”

[Ecaterina]

Hello, @alexandre.boulme

A prefix is the complete path in front of the object name, which includes the bucket name. For example, if an object (123. txt) is stored as BucketName/Project/WordFiles/123. txt, the prefix is “BucketName/Project/WordFiles/”.

I suppose that the double prefix is related to the:

• Folder name, since you have a dynamic source for it;
• Filenames prefix construction.

Allow me to note that our team encountered the issue of the double prefix for the first time. Analyzing the source for the Filenames Prefix, I suppose that exactly this reproduces the issue.
As an experiment, I suggest you clear this field and try uploading the file to your AWS Bucket.

If the issue with the double prefix will be fixed, the only solution would be re-write this field on your side.

Please try it and let me know about the result.
Best regards,

[alexandre.boulme]

Hi @Ecaterina,

I just tried to chage the foldername and prefix value with static strings to see if it was due to my dynamic sources. But it seems that I still get the same issue, see the new configuration :

Here is the link I get : “https://XXXXXX.s3.eu-west-3.amazonaws.com/testFolder/prefix__prefix__Capturedecran20220624a10.44.20.png”

If it’s the first time you get this problem maybe you should know that I use your pluging in a repeating group, see my element tree :

I’m not sure, it could impact the upload, still can be a good insight to solve the problem.

Thanks for your help !
Alexandre

[alexandre.boulme]

@Ecaterina It’s blocking us from going live could you please provide us with a solution ?! I brought this plugin to gain time, and it’s already the third issue I got with it since I tried to set it up…

[Ecaterina]

Hello, @alexandre.boulme

@alexandre.boulme

I just tried to chage the foldername and prefix value with static strings to see if it was due to my dynamic sources. But it seems that I still get the same issue, see the new configuration :

Please allow me to check your request above ASAP and revert with a solution.

@alexandre.boulme

It’s blocking us from going live could you please provide us with a solution ?! I brought this plugin to gain time, and it’s already the third issue I got with it since I tried to set it up…

As for this, can you please share a message, that you saw while you trying to go live?
These messages are created by the Bubble, so the issue is related to your application, but not the plugin.

Thank you!

[Ecaterina]

Hello, @alexandre.boulme

Due to the fact that we have some additional questions regarding your settings, can you please add our Support Team email to the list of collaborators to your application and provide me a link to your application? This will allow us to check your settings and run some tests to fix the mentioned problem.

To add our Support Team as a collaborator, you need to do the following steps in the Bubble Editor:

Settings > Collaboration > Add email support@zeroqode.com

Note: avoid the warning message regarding the plan, as we are an agency and you can easily add us to your collaborators.

Looking to hear you soon.
Regards,

[alexandre.boulme]

Hi @Ecaterina,

Sorry I didn’t see your message, I just add your account to the application and sent you the link in direct message, with all the explanations.

Thanks and sorry for the delay !