Storage provider is not recognized about carrierwave-aws HOT 5 CLOSED

You'll need to change storage :fog to storage :aws so that it chooses the correct storage provider. Internally all of the privacy, expiration and other options work the same way, but you do need to specify :aws instead.

Note that the configuration options will be different if you have things set up for fog. You'll need to change anything prefixed with "fog" into "aws", such as aws_bucket, aws_acl, aws_authenticated_url_expiration, aws_credentials

from carrierwave-aws.

Hi @sorentwo! Thanks for the quick reply. I made that change (which completely makes sense, just wasn't sure how much it was basing itself on fog), but still have the error I was getting from fog:

NoMethodError (undefined method `original_filename' for #<CarrierWave::Storage::AWS::File:0x007fcebacf7868>)

I wrote an issue for Fog earlier today about the original_filename issue
fog/fog#1756

Any ideas how to deal with this on carrierwave-aws?

from carrierwave-aws.

Do you happen to be using CarrierWave::MimeTypes in the uploader that is causing this? It seems to be the only place where original_filename is called unguarded within the CarrierWave source.

I'm curious what your application's flow is. We are using carrierwave-aws with mime type processing in all of our uploaders and haven't had that error at all.

from carrierwave-aws.

@sorentwo - It looks to me like the actual issue may be in gzigzigzeo/carrierwave-meta. See also: gzigzigzeo/carrierwave-meta#4 (comment)

from carrierwave-aws.

Thanks @geemus, that is almost certainly the culprit here. @lbain - I am going to close this as it was in regard to configuration and your underlying issue isn't related to carrierwave-aws.

from carrierwave-aws.