paperclip

The scenario is a normal model that contains a paperclip attachment along with some other columns that have various validations. When a form to to create an object cannot be saved due to a validation error unrelated to the attachment, columns like strings are preserved and remain prefilled for the user, but a file selected for uploading is completely lost and must be reselected by the user. Is there a standard approach to preserving the attachment in the case of a model validation error? This seems like a very common use case. It seems inelegant to hack up a solution where the file is saved

I am looking for a solution to give the user the ability to upload multiple images through one file_field. I have looked in to options such a Jquery File Upload and Uploadify but have yet to come across good examples with a working solution. I already have multiple images setup, has_attached_file :asset, :styles => { :large => "640x480", :medium => "300x300", :thumb => "100x100" }, :storage => :s3, :s3_credentials => "#{Rails.root}/config/s3.yml", :path => "/:contributor_id/:listing_name/:filename" Right now I am displaying 5 individual file_fields def new @listing = Listing.new 5.times {

I am adding user uploaded videos to my RoRs site with the help of the paperclip gem and s3 storage. For some reason that I can't figure out, whenever a user uploads an mp4 file, s3 sets content-type for that file as application/mp4 instead of video/mp4 . Note that I have registered mp4 mime type in an initializer file: Mime::Type.lookup_by_extension('mp4').to_s => "video/mp4" Here is the relevant part of my Post model: has_attached_file :video, :storage => :s3, :s3_credentials => "#{Rails.root.to_s}/config/s3.yml", :path => "/video/:id/:filename" validates_attachment_content_type :video,

I'm creating a multi-part form in the style that Ryan Bates describes here: http://railscasts.com/episodes/217-multistep-forms http://asciicasts.com/episodes/217-multistep-forms (text-based version) To summarize, I have one view (with a bunch of partials for each form step), and the form variables are stored in a session when the user clicks a next button and a different part of the form is displayed. One of my form steps allows the user to upload several images via the Paperclip gem. The problem with that is that Rails is trying to upload the image data to the session, which is returning

I used gem "paperclip" for upload images and gem "paperclip-storage-ftp" for store images on my own ftp server. It worked fine for a while, but now I am getting random errors, when I upload photos. Sometimes this Net::FTPReplyError - 150 Connecting to port 3270 Sometime this Net::ReadTimeout - Net::ReadTimeout: Sometime this Paperclip::Storage::Ftp::NoServerAvailable .. and sometimes this: Net::FTPPermError - 500 ? Model class AlbumPhoto < ActiveRecord::Base has_attached_file :photo, { # Choose the FTP storage backend :storage => :ftp, :path => "www.abcd.com/:attachment/:id/:style/:filename",

We've recently moved to a new webhost that offers limited storage space so we're trying to move all of our user uploads (Avatars, Files, etc.) uploaded via the Paperclip gem to Amazon S3. I have several hundred files all corresponding to different models that I'm now trying to migrate en masse. I found this document that introduces a nifty paperclip rake task: rake paperclip:refresh:missing_styles This command does some of the work for me, however, I noticed it's only setting up the files structure without sending any data - in addition it's not setting up any thumbnails defined using the