Open nddeluca opened 10 years ago
@nddeluca sorry to resurrect an old issue, but is there anything I can do on my side to get around this? I'm running into this also
@kevinc This should be fixed with the following https://github.com/dwilkie/carrierwave_direct/pull/198
thanks @p8! just found that and adding it to my codebase until v0.0.16 is out.
Great! Let us know if it solves this issue.
adding this in addition to https://github.com/nddeluca/carrierwave_direct/pull/1 seems to have fixed my issue
looks like i spoke too soon @p8 . i'm still having the issues where it's doubling up a section of the URL.
I've gone down the road of pointing my Gemfile at the latest commit and the problem still persists, similar to: https://github.com/dwilkie/carrierwave_direct/pull/160 https://github.com/dwilkie/carrierwave_direct/issues/118
When using an uploader that uses carrierwave_direct, uploads that are not done directly mistakenly use carrierwaves temporary cache_id as part of the filename. This gives inconsistent url's between files that are directly uploaded and those that are not.
Files should be able to be directly uploaded by the user or programmatically uploaded by the server without any change in url behavior.