Closed microspino closed 10 years ago
Thanks for opening an issue on this and bringing it to our attention. This brought to light an issue with any database-backed field that's wrapped by some other kind of Ruby object. In your case, calling avatar
returns an AvatarUploader
when sprig-reap really only wants the underlying file location (the string stored in the database).
In order to handle these circumstances, I had to make some changes. I will be pushing a new version of sprig-reap (0.0.6
) with a fix shortly.
CarrierWave uploaders should be fixed as of version 0.0.6
. Give it a shot!
OS X 10.7 - Rails 4.0.3, ruby 2.1.1p76 using PostgreSQL. My Rails app. uses either ActsAsTaggableOn and Carrierwave. Every user has a Post and an Avatar uploaded via carrierwave on S3. Dumping all the user in a users.yml seed file works fine but the script explodes in my face with:
The strange thing is that when i run for the first time
I don't get any error. I start receiving the error above from the second time i launch that command onward.
Here is a snatch of the users.yml file:
Any clue, hint help is appreciated.