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

Unable to parse path with space #108

Open
hoodsy opened this issue Aug 29, 2016 · 2 comments
Open

Unable to parse path with space #108

hoodsy opened this issue Aug 29, 2016 · 2 comments
Assignees
Labels

Comments

@hoodsy
Copy link

hoodsy commented Aug 29, 2016

Steps to reproduce

Upload a file with a space in the path, e.g. T/altright kreiger.png

Expected behaviour

The space in the path is accounted for, and the image is correctly found.

Actual behaviour

I can escape the space, like so: T/altright\ kreiger.png but then the path isn't correctly found: Error: ENOENT: no such file or directory,

@Starefossen

@anthonyringoet
Copy link
Contributor

Can you provide info about your environment?

  • Operating system (Mac, Linux, Windows)
  • Node.js version (node --version)
  • ImageMagick version (identify -version)
  • s3-uploader version

@webdevian
Copy link

This happens for me, it throws an error with no stacktrace with

MacOS v10.12.4 
Node v6.10.2
ImageMagick 7.0.5-4 Q16 x86_64 2017-03-25
s3-uploader 2.0.3

I got around it by renaming files with encodeURIComponent() first, but it would be nice for the plugin to handle it.

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

No branches or pull requests

3 participants