Filename auto normalization to avoid upload errors

JeremyLaurenson

I want to publish a url for folks to contribute images for a slideshow...

I am getting an error message when trying to upload images using: https://jeremy.laurenson.com/a/?upload=1

The error I get is "Failed to upload xxxx.jpeg Invalid dir path"

This seems to be to do with filenames, so isnt there a way to normalize file names people upload? Currently for iPhone users as an example, it breaks often

Karl

JeremyLaurenson I think indeed there is a bug here.

There seems be un-assigned upload path when the folder is root and uploader opens with ?upload=1, as it says [object Object] (which essentially means the javascript upload does not have a path). It works if you close and re-open the uploader dialog. I will look into it for an update within tomorrow. Until then, you would need to avoid using ?upload=1.

On auto open from ?upload=1

After close and re-open, it works fine:

Thanks for reporting.

Karl

JeremyLaurenson This was fixed in update 0.12.3 released earlier today.

JeremyLaurenson

This may not be something as simple as the filename... Im getting error with basic ones too

KeepCoolCH

it is only your link, that doesn't work, when you upload in the folder directly it works (i uploaded a test.jpg file)

JeremyLaurenson

Ah, true dat.

So then the issue is how to fix it.

KeepCoolCH

i don't think you could specify the folder via the link, the number 1 only triggers the "true" statement to show the upload popup for my understanding. why the upload popup shows "[object Object] ≤ 536.87 MB" instead of the folder i don't know

KeepCoolCH

hey karl, in the 0.12.3 version i'm getting a file upload error but the files are written to the folder. i rolled back to a previous version with the same settings and the error don't show up. maybe you created an error with solving the ?upload=1 error 😉 thanks for looking into it 🙂

Karl

KeepCoolCH Arrgh, sorry there was a bug in 0.12.3 that output "error" in uploader, even after success. This has now been fixed, please download latest version 0.12.4 (or higher) ...