Silently fails when the file could not be written via webdav

Question

Silently fails when the file could not be written via webdav

Opened this issue 10 years ago · 2 comments

I was testing this lib quickly and noticed that it will silently fail when the file could not be uploaded to the server via webdav. For example, the server returned a 413 status code (entity too large) and the model didn’t really care.

I’m not sure what’s the convention in carrierwave when an error happens when storing the file. Ideas?

Answer 1 · 2014-10-09T09:15:16.000Z

Hello,
I have merged #6, which seems like having fixed the issue. I have pushed the latest version to rubygems, you could try to use the version 0.4.1 in rubygems.

Answer 2 · 2014-10-09T13:21:15.000Z

@qinix cool! thanks! Your lib is saving me some time at work, thank you for that!