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.

Sign up for GitHub

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

Jump to bottom

Cloudinary::Uploader.upload's return_error option doesn't work for 404's #70

Closed
jturkel opened this issue Apr 15, 2013 · 3 comments
Closed

Cloudinary::Uploader.upload's return_error option doesn't work for 404's #70

jturkel opened this issue Apr 15, 2013 · 3 comments

Kommentare

@jturkel
Copy link

jturkel commented Apr 15, 2013

It's pretty easy to reproduce:

Cloudinary::Uploader.upload(
    'http://salsify.com/foobar.png', resource_type: 'auto', return_error: true
)

We would like this to work so we can add special handling of images not being found and we don't want to parse the exception message.
TalLevAmi added a commit that referenced this issue Apr 15, 2013
@TalLevAmi
Issue #70 - Return parsed error message for 401,403 and 404 error cod…
9622a40 
…es as well
@TalLevAmi
Copy link
Contributor

Fixed in master. We will release a new gem in the next few days.

@jturkel
Copy link
Author

jturkel commented Apr 15, 2013

Awesome. Thanks for the fast turnaround!

nadavs added a commit that referenced this issue Apr 19, 2013
@nadavs
Increment version to v1.0.55: Support folders in PreloadedFile, Allow…
0d19de1 
… cloudinary helpers to work directly with CarrierWave uploaders, Issue #70 - Return parsed error message for 401,403 and 404 error codes as well, CarrierWave - allow returning format in dynamic methods.
@nadavs
Copy link
Contributor

nadavs commented Apr 19, 2013

The fix is available in v1.0.55 of the GEM.

@nadavs nadavs closed this as completed Apr 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@TalLevAmi @nadavs @jturkel