Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

S3 #2483

Closed
jasonivers opened this issue Sep 6, 2017 · 5 comments
Closed

S3 #2483

jasonivers opened this issue Sep 6, 2017 · 5 comments

Comments

@jasonivers
Copy link

Amazon has recently updated their SDK gems to version 3. This appears to have broken Paperclip's support of S3, as files are now being uploaded empty (0 bytes).

I don't have the time to dig through the gem to figure out where the issue is, exactly, at the moment, as I'm down 2 developers, but I would highly appreciate some help, or if there is a newer, more actively maintained repo (last real update was December of last year) that someone could point me at...

@jaybloke
Copy link

jaybloke commented Sep 7, 2017

Also experiencing similar problems with this too. Upgrade AWS SDK 3.0.1 and now receive this message:

NameError: uninitialized constant Aws::VERSION
/home/deploy/production/shared/bundle/ruby/2.3.0/gems/paperclip-5.1.0/lib/paperclip/storage/s3.rb:125:in `extended'

@morgoth
Copy link
Contributor

morgoth commented Sep 8, 2017

@jasonivers This should fix it #2481 - I guess for now you can freeze aws-sdk to ~> 2.0

@jasonivers
Copy link
Author

jasonivers commented Sep 8, 2017 via email

@aghamdi
Copy link

aghamdi commented Dec 15, 2017

Paperclip uses the Aws::VERSION to check features and compatibility of certin versions like 2, 2.0.33 and above 2.3.0. For now you can add the missing method VERSION in your paperclip initializer or any file that get loaded like the following:

module Aws
VERSION = "3.0.0"
end

It worked for me but use it with caution and test to ensure that nothing breaks in your code.

@mike-burns
Copy link
Contributor

We have migrated to awk-sdk-s3.

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

No branches or pull requests

5 participants