Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Original uploaded image does not have an extension when the path is specified #132

Open
CodeStrumpet opened this issue Mar 9, 2017 · 2 comments

Comments

@CodeStrumpet
Copy link

I'm trying to achieve a specific naming result with the uploaded S3 files but have been unsuccessful so far.

This is a pretty minor issue. When the path I pass to S3-uploader does not have an extension I can force my desired behavior on the versioned images (by specifying a suffix and the resultant image format) but the original image does not get an extension.

In my example, the path is the_whole_damn_thing_front_blunt. Notice in the screenshot below that the original image gets a period but does not have an extension appended.

image

When I put an extension in the path passed to s3-uploader, I get double extensions.

image

Is there any way to have the original image (in the first screenshot above) to get an extension when it is uploaded to S3?

Thanks for any insight and please let me know if this is not the appropriate place to pose this question.

@webdevian
Copy link

I'm having this problem too, I feel like I must be doing something wrong, this can't be the default behaviour

@webdevian
Copy link

@CodeStrumpet It seems that this happens if the tmp file on your server doesn't have an extension

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants