Ruby on Rails, JRuby, AWS, EC2, Exalead - Goodbye attachment_fu, hello Paperclip Comments

Comment on 'Goodbye attachment_fu, hello Paperclip' by Casé Oliveira

2010-07-05T21:56:06Z

Thanks for the post!

Comment on 'Goodbye attachment_fu, hello Paperclip' by Drew

2010-03-31T08:21:27Z

Thank you very much for this detailed description of Paperclip. It saved my ass.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2010-03-27T20:03:12Z

While I don't want to disagree with Jon (it is his plugin after all!) I'm not sure what the problem is here. The styles aren't evaluated when the attachment is initialised, any procs are called when the styles method on the attachment instance is first called. Typically this will be in the post_process_styles method which runs when a file is assigned to the attachment.

The cache classes setting shouldn't cause any problems because the 'solidified' styles are stored in the attachment instance not the class, and this instance should be reinitialised on each request.

We've been using styles in this way on production apps for some time, but I will have to take another look to check things haven't changed recently as these apps are running on older versions of the plugin.

The only problem I have noticed with the way Paperclip handles these procs is that if you assign a file to the attachment and then assign another file to the same attachment instance then the proc won't be re-evaluated. But that's a different problem to the one you're talking about.

I'll have to have a play with the code and see what happens!
Rob

Comment on 'Goodbye attachment_fu, hello Paperclip' by mleszcz

2010-03-27T12:12:36Z

Please remove/change Styles can be Procs too. It turns out that this solution causes errors in production environment. Read Yurek's explanation. There is other solution for dynamic styles.

Comment on 'Goodbye attachment_fu, hello Paperclip' by What It Dont Do

2009-12-21T09:22:03Z

InlineUploader is cool, but not quite what I was looking for.

I've been trying to hack something out with Paperclip, a Rails plugin, a model only solution that implicitly (when instructed via a hidden input) saves (on disk) and loads images across multiple forms, allowing you to link to the styled images without saving the model.

For example:

class Image < AR
  has_attached_file :file
  attr_accessor :file_id #Used to associate req. with images 
  after_post_process :save_images_for_session  

  def save_images_for_session
    file.queued_for_write.each do |style, file|
      #Oops, file_id hasn't been assigned by AR::Base.initialize yet
      FileUtils.mkdir_p(Dir.tmpdir + file_id + style)
      #copy to file_id/style, etc...
    end
  end
end

Since Paperclip writes the styles on assignment, in this case before file_id was assigned, you can't do the mkdir.

In lieu of using after_initialize (which I'd think one would want to avoid for a plugin), I might end up doing it explicitly:

photo = Photo.new(params[:photo])
photo.load_sessions_attachments!

Plus, that saves me from class_eval overrhacking into attachment_for().

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-12-14T16:36:13Z

You could always look at something like InlineUploader to do something like that: it allows files to be uploaded separately and then reunited with a form on submission.

Comment on 'Goodbye attachment_fu, hello Paperclip' by What It Dont Do

2009-12-14T06:47:30Z

What about forms that require you to approve your changes before saving?

I'm surprised no one's written a processor -err no, an after_post_process hook for this. Something that copies the file(s) to a location where they won't be deleted (as I believe Paperclip does so once the response is sent) and associates this location with the session or a hidden field so that they can be linked up on save.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-11-27T11:01:20Z

@jose: if you're ok for all of your thumbnails to use png format then you can specify this in your styles definition:

:styles => { :thumbnail => ['120x120', :png] }

If you only want certain types to use png then things get more tricky: you should look at my video thumbnailing post for inspiration :)

@tiago: you can use the to_file method of the attachment. This returns you an actual file object that you can then use to do your validation and if the attachment is unsaved this'll be a reference to the temporary upload file.

Comment on 'Goodbye attachment_fu, hello Paperclip' by tiago

2009-11-23T11:17:42Z

Do you know how i can get the path to the temporary file in the model? before it was created/saved? I would like to make some validations in the before_create, but at that time the attachment.path doesnt exist yet.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Jose Boza

2009-10-28T15:54:23Z

what if I have a asset model that can take any contenttype and want to create thumbnails according to that contenttype, lets say if i upload and image i want it to create a thumbnail of that image, but if i upload a video or an mp3 file i want to set the thubnail to a predefine file on my server like video.png or mp3.png thank you

Comment on 'Goodbye attachment_fu, hello Paperclip' by Nick T

2009-10-14T00:56:59Z

Thanks for the TempFile monkey patch. I absolutely needed it.

Comment on 'Goodbye attachment_fu, hello Paperclip' by ocdave

2009-08-08T06:36:21Z

I've "had it" with windows! You have to jump through so many hoops, just to trick it into being useful. I order Fedora Core Linux today

Comment on 'Goodbye attachment_fu, hello Paperclip' by ashley

2009-05-22T08:06:50Z

Im using paperclip for a lib upload/download site and im trying to figure out how to protect the model from a hacked upload form, one that switches model attribute that the file is uploaded too.

Ie if i define the model with the following;

hasattachedfile :new_upload attrprotected :newuploadfilename, :newuploadcontenttype, :newupload_size

hasattachedfile :virus_checked attrprotected :viruscheckedfilename, :viruscheckedcontenttype, :viruschecked_size

and then a form with <%= form.filefield :newupload %>

Then it only stops the hackers from from pointing the inital *filename fields to something like "/etc/password" and such... I can successfully hack the form and directly upload a bad file into the "virus_checked" field

Do you know a solution to this? I tried to use this; attrprotected :viruschecked

But it has no effect, the hack can still bypass it

Thanks

Comment on 'Goodbye attachment_fu, hello Paperclip' by nugatowy

2009-04-28T22:43:56Z

Thank You, that's it indeed. I have now two ways: to use attr_accessible in my model or comment indicated line in the module. I need to guess what would be better in my case. Thanks again!

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-04-28T20:42:19Z

I'd guess that you're not using attr_accessible in your model: my module does and will therefore have made mass-assignment fail for all of your other attributes. An easy fix would be to comment out the attr_accessible "delete_#{name}" line in the module.

Comment on 'Goodbye attachment_fu, hello Paperclip' by nugatowy

2009-04-28T19:49:21Z

Seems to be a good solution but it doesn't work for me. I placed all the code You show in proper places. But with the line "has_deletable_attachment :photo" my model object is not going to be saved - validation messages about all fields of article model appear. :/ The output of console says among others: "WARNING: Can't mass-assign these protected attributes: photo, category, title, body" Why does it happened using Your module as without it evrything worked?

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-04-27T07:55:07Z

I've recently moved the deletion code into a module (with a view to eventually submitting it as a patch to Paperclip. You can get the gist here. The module is included in an initializer and adds the has_deletable_attachment method to your models. You can then do something like this:

class MyModel < ActiveRecord::Base
  has_attached_file :photo_one, ... # paperclip options
  has_attached_file :photo_two, ... # paperclip options
  has_attached_file :photo_three, ... # paperclip options

  has_deletable_attachment :photo_one, :photo_two, :photo_three

  # rest of model
end

Your form can then include checkboxes for deletion like this:

  <%= f.label(:delete_photo_one, 'Delete photo') %>
  <%= f.check_box(:delete_photo_one) %>
  <%= f.label(:delete_photo_two, 'Delete photo') %>
  <%= f.check_box(:delete_photo_two) %>
  <%= f.label(:delete_photo_three, 'Delete photo') %>
  <%= f.check_box(:delete_photo_three) %>

Comment on 'Goodbye attachment_fu, hello Paperclip' by nugatowy

2009-04-25T07:08:30Z

Rob has presented a cool way to delete attachment. How should I modify the code in an elegant way to handle the storage of 2-5 attachments? I have prepared a sufficient number of columns in the database table and few "has_attachment" statements in a model. How should the methods of deleting the greater number of attached files in a single model look like?

Thanks for any help.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-04-10T16:55:06Z

You need to use a geometry string. In this case "800x600>" should do what you want: it says to only resize to 800x600 if the image is larger than that, if it is smaller the size is left alone.

Comment on 'Goodbye attachment_fu, hello Paperclip' by RashOnRails

2009-04-10T15:37:40Z

I was surprised to find that when specifying original => "800x600", ALL images were resized to 800x600, even teeny tiny files that were rized UP to that resolution. If the intention is to limit storage usage, I would've thought images would only be resized DOWN if necessary. Any simple way to implement this functionality? Thanks!

Comment on 'Goodbye attachment_fu, hello Paperclip' by TJ Sherrill

2009-04-09T21:01:41Z

Thanks, that did the trick. In the case of my app, this is a huge help. If not for this, all the images would save in separate folders and it would have made the whole thing confusing.

thanks

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-03-30T08:07:55Z

Sounds like you need to create your own interpolation for property ID. Something like this:

Paperclip::Attachment.interpolations[:property_id] = proc do |attachment, style|
  attachment.instance.property.id
end

This assumes that your photo model has a belongs_to :property association. Then in the has_attached_file definition you can do this:

:url => "/images/properties/:property_id/:basename_:style.:extension",
:path => ":rails_root/public/images/properties/:property_id/:basename_:style.:extension"

If you still want to use ID partitioning then the approach is the same:

Paperclip::Attachment.interpolations[:property_id_partition] = proc do |attachment, style|
    ("%09d" % attachment.instance.property.id).scan(/\d{3}/).join("/")
end

Change your has_attached_file to use :property_id_partition instead of :property_id for the :path option.

Hope that helps,
Rob

Comment on 'Goodbye attachment_fu, hello Paperclip' by TJ Sherrill

2009-03-28T22:56:25Z

I am writing a Property mgmt app and have gotten Paperclip to upload mulitiple files which is great, but when its saving 6-9 images per property its not a good idea to save them in the same folder. I have seperate property and photo models. I would like it to save to /public/images/property_id/:basename_:style.:extension

I have worked with the tutorial and cant figure it out.

:url => "/images/properties/:id_partition/:basename_:style.:extension",
:path => ":rails_root/public/images/properties/:id_partition/:basename_:style.:extension"

thats what I currently have. I would be ok if it didn't save to a property id folder if it would save all photos for a specific property in its own folder. Any help would be amazing.

thanks

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-03-14T13:29:01Z

The first thing I'd try is changing the line where you open the mp3 file:

# Original
mp3info = Mp3Info.open(params[:track][:mp3].path)

# How about this?
mp3info = Mp3Info.open(@track.mp3.to_file.path)

So then you'll be using the file being handled by Paperclip rather than the one in the params hash.

But I'd really want to move the mp3 processing code into my model to keep the controller thin, like this.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Petr

2009-03-13T14:21:09Z

Hi all,

can't make the create action to save info tags to my DB.

def self.up
    create_table :tracks do |t|
      t.column  :title,             :string
      t.column  :artist,            :string
      t.column  :album,             :string
      t.column  :year,              :string
      t.column  :genre,             :string
      t.column  :user_id,           :integer
      t.column  :mp3_file_name,     :string
      t.column  :mp3_content_type,  :string
      t.column  :mp3_file_size,     :string   
      t.column  :play_count,        :integer, :default => 0
      t.column  :length,            :integer
      t.timestamps
    end
  end

<% form_for :track, @track, :url => { :action => "create" }, :html => { :multipart => true } do |f| %>

        <p><%= label_tag 'File to upload' %>
        <%= f.file_field :mp3 %></p>

        <p><%= submit_tag 'Send' %></p>
        <% end -%>

def create
        @track = Track.new(params[:track])

        mp3info = Mp3Info.open(params[:track][:mp3].path)
            @track.length = mp3info.length
            @track.title = mp3info.tag.title
            @track.artist = mp3info.tag.artist
            @track.album = mp3info.tag.album
            @track.year = mp3info.tag.year
            @track.genre = mp3info.tag.genre

        if logged_in_user.tracks << @track
            flash[:notice] = "Uploaded."
            redirect_to :action => :index
        else
            flash[:error] = "Ohhh, something went wrong. Try it again."
            render :action => :new
        end
    end

Any help would be most welcome. Thank you.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2009-01-17T19:42:06Z

No, you can't do file uploads via AJAX due to browser security. What you can do though is use a flash uploader like FancyUpload, something I blogged about recently.

Comment on 'Goodbye attachment_fu, hello Paperclip' by marcus

2009-01-16T16:17:59Z

hello, great post, thank you very much.

Does it work with form_remote_tag ? how ?

Comment on 'Goodbye attachment_fu, hello Paperclip' by Daniel Lopes

2008-12-22T22:51:29Z

Amazing explanation.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2008-12-21T23:24:38Z

@Aditya: you're quite right, they're was something amiss with the code. My fault: originally my example handled deletion in the controller, then Chris suggested I move it into the model but I messed up making the changes to this blog entry :( Fixed it now though - thanks for the reminder!

@Austin: I'd have suggested something like this:

has_attached_file :image, :storage => Rails.env.production? ? :s3 : :filesystem, ...

but either way looks fine to me :)

@Andrew: does the reprocess! method of Attachment work with S3? There's also a rake task to do this, so you change your model to add the style, then run rake paperclip:refresh:thumbnails.

@johny: sounds like you've hit a problem which I have submitted a patch for but which hasn't yet made it into the plugin. In the meantime you can download my monkey patch, put it in your RAILS_ROOT/lib folder and require it from an initializer and you should be good to go. This patch also includes a couple of other Windows specific fixes.

Comment on 'Goodbye attachment_fu, hello Paperclip' by johny

2008-12-20T03:23:16Z

anyone can help me plz. I got an error like this

Permission denied - Permission denied - C:/DOCUME~1/john/LOCALS~1/Temp/stream20081220-2836-1duxmf0-0 or C:/Documents and Settings/john/My Documents/NetBeansProjects/userprofile/public/avatars/7/original/naruto.jpg

os win xp ruby 1.8.6 gems 1.2 rails 2.1 database adapter mysql application server webrick apache 2.2 imagemagick 6.4.5

on my controller

def create
  @user = User.new(params[:user])
end

on new application

<% form_for(@user ,:html => { :multipart => true }) do |f| %>
  <%= f.error_messages %></p>
  <p>
    <%= f.label :lastname %><br />
    <%= f.text_field :lastname %>
  </p>
  <p>
    <%= f.label :firstname %><br />
    <%= f.text_field :firstname %>
  </p>
  <p>
    <%= f.label :address %><br />
    <%= f.text_field :address %>
  </p>
  <p>
   <%= f.file_field :avatar %><br>
  </p>
  <p>
    <%= f.submit "Create" %>
  </p>
<% end %>

on my model

class User < ActiveRecord::Base
  has_attached_file :avatar, :styles => { :medium => "300x300>", :thumb => "100x100>" }
end

Comment on 'Goodbye attachment_fu, hello Paperclip' by Andrew Clark

2008-12-19T01:29:49Z

Looking for a way to add a style once we have a DB full of attachments. anyone have anything written for this?

for attached_file in model open file crop/resize file save file to s3 end

Comment on 'Goodbye attachment_fu, hello Paperclip' by Andrew Clark

2008-12-19T01:27:52Z

@austin - with paperclip, you can now define buckets in your S3.yml file.


development:
    bucket: bucketname
    access_key_id: access_key
    secret_access_key: secret_key

Comment on 'Goodbye attachment_fu, hello Paperclip' by Austin Schneider

2008-12-17T18:52:19Z

Here's my solution to providing different options depending on environment

has_attached_file :image, :storage => {
  'development' => :filesystem,
  'production' => :s3
}[RAILS_ENV], ...

You can do this for path, etc.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Austin Schneider

2008-12-17T16:35:35Z

Per 18. CED

I'm also trying to figure out how to set the storage based on environment (filesystem for development, s3 for production)

Anyone know?

Comment on 'Goodbye attachment_fu, hello Paperclip' by James MacLeod

2008-12-17T15:36:09Z

@Rob Anderton: Thanks so much for the details about the gotcha with the Attachment model problem. It has saved me from tearing whats left of my hair out!

Comment on 'Goodbye attachment_fu, hello Paperclip' by Aditya Sanghi

2008-12-17T13:23:00Z

Hi Rob,

The code for deleting a photo seems a bit incorrect to me. You're calling delete_photo? in a method in the controller but the method exists on the user model i presume.

You may want to set the photo to nil in a before_save method on the user model perhaps, keeping the controller thin and setting the photo to nil using your newly minted delete_photo attributes in the model.

in your model..


  before_validation :set_photo

private

  def set_photo
    self.photo = nil if delete_photo?
  end

Cheers, Aditya

Comment on 'Goodbye attachment_fu, hello Paperclip' by CED

2008-12-16T16:52:09Z

Great, overview.

Would you know if there is a way to reference attachments differently depending on environment? For example, I would like to use S3 in production but the file system in development.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Chris Anderton

2008-12-12T16:29:11Z

Hi Mike

If you take a look at the following example:

class User < ActiveRecord::Base
  has_attached_file :avatar,
                    :styles => { :square => ["64x64#", :png],
                                 :small  => "150x150>" }
end

You'll see that the options for the :square thumbnail are passed as an array - the second value being the format for that style.

Comment on 'Goodbye attachment_fu, hello Paperclip' by mikej

2008-12-11T23:35:48Z

I am trying to figure out how to have .jpg thumbnails created for .tif files when uploaded. Having a bit of trouble figuring out where to make all the changes. Any help would be greatly appreciated.

Mike

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2008-12-06T16:46:01Z

Hi Dave,

You might want to take a look at the patch I submitted for Paperclip a couple of weeks back. While it primarily focuses on the broken tests on Windows there is also a change to the Attachment#assign method which might help you out.

Most permission denied errors of this sort on Windows are less to do with actual security permissions and more to do with open file handles preventing Windows from deleting a file: a problem that doesn't occur on Unix based systems because of the different way in which they handle files.

Hope it helps!
Rob

Comment on 'Goodbye attachment_fu, hello Paperclip' by dave

2008-12-05T11:30:34Z

Hi I am running on Windows and I keep getting a permissions denied error when I try to save the model.

paperclip creates the temp file version which I have full control over and it creates the new directory names in public which I also have full control over but fails with the following error.

I have tried the monkey patch of the temp file as recommended. I have put the patch in the Application.rb

I have searched all the forums and noticed other people had the same error but no responses. I installed the latest version from Git today again and I am running rails 2.1

[paperclip] Paperclip attachment photo on Exercise initialized. [paperclip] Assigning #<file:c: /> to ph oto [paperclip] Writing attributes for photo [paperclip] Post-processing photo ←[4;35;1mSQL (0.000000)←[0m ←[0mBEGIN←[0m ←[4;36;1mExercise Update (0.000000)←[0m ←[0;1mUPDATE exercises SET photo_ updated_at = '2008-12-05 11:12:04', photo_content_type = 'image/png', update d_at = '2008-12-05 11:12:04', photo_file_size = 62937, photo_file_name = 'P icture2.png' WHERE id = 18←[0m [paperclip] Saving attachments. [paperclip] Saving files for photo [paperclip] Deleting files for photo [paperclip] Writing files for photo [paperclip] -> C:/myapp/public/assets/exercise/18/original/Picture2.png ←[4;35;1mSQL (0.031000)←[0m ←[0mROLLBACK←[0m

Errno::EACCES (Permission denied - C:/DOCUME~1/dfalvey/LOCALS~1/Temp/stream.4996 .0 or C:/myapp/public/assets/exercise/18/original/Picture2.png):

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2008-11-22T18:30:55Z

To follow up on my earlier comment to Peter, there are two gotchas to be aware of if you have a model named Attachment and want to use it in a has_many association.

You must explicitly define the attachment class name when defining the association, otherwise you'll get an error like NoMethodError: undefined method `quoted_table_name' for Paperclip::Attachment:Class when you try and access the association. For example:
```
has_many :attachments, :class_name => '::Attachment'
```
The current version of Paperclip creates a naming conflict with an association named attachments. I've posted a patch but in the meantime you can monkey patch your model with something like this:
```
def attachment_for name
  @_paperclip_attachments ||= {}
  @_paperclip_attachments[name] ||= Attachment.new(name, self, self.class.attachment_definitions[name])
end
```

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2008-11-22T11:44:30Z

I’ve just posted a patch for Paperclip to fix a few problems with failing tests and corrupted attachments after using reprocess! on our beloved Windows systems. I decided against including the Tempfile patch and have updated this blog to note that I no longer think this is needed.

@Jim: thanks for the original tutorial and for your recent advice - yeh I will get a mac :D

@Peter: don’t forget there’s nothing stopping you having a special model for your attachments just like attachment_fu, then you can has_many :attachments in the parent model just like the good old days!

@Roob: good thing to remember - my image content type list currently looks like this:

[ 'image/gif', 'image/png', 'image/x-png', 'image/jpeg', 'image/pjpeg', 'image/jpg' ]

Comment on 'Goodbye attachment_fu, hello Paperclip' by Roob

2008-11-20T15:39:28Z

Great in-depth tutorial! Remember to allow the content type 'image/pjpeg', otherwise that godforsaken Internet Explorer fails.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Peter Yanovich

2008-11-17T14:09:45Z

Sometimes using attachment_fu is really better. When we want to attach many files or we want to moderate big amount of files - attachment_fu is only way.

Really good and usefull article, man. Thank you!

Comment on 'Goodbye attachment_fu, hello Paperclip' by wictor

2008-11-12T17:07:30Z

Thank you for your resources. They were very helpful.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Jim Neath

2008-11-11T15:10:17Z

Good work, chaps.

I've been meaning to add half of this stuff to my old post for ages but alas, laziness always gets the best of me.

Thanks for the link :)

Comment on 'Goodbye attachment_fu, hello Paperclip' by cam

2008-11-10T21:22:08Z

this is a sweet post. Just what I was looking for!!

Comment on 'Goodbye attachment_fu, hello Paperclip' by musk

2008-11-07T13:10:55Z

Great plugin so easy to setup and use. Just some additions that are not so obviouse from the rdoc.

To configure paperclip you can add the following statements to your environment file

# this is essential if you do not have ImageMagick in your search path
Paperclip.options[:image_magick_path]='Path/to/ImageMagick/executables'
# this makes paperclip complain if no resizing is not possible
Paperclip.options[:whiny_thumbnails]=true

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rob Anderton

2008-11-07T11:53:29Z

In a spooky case of great minds thinking alike, Ryan Bates also posted a RailsCast covering Paperclip this week! I’ve added a link to it in the post, but thought it was worth a mention here too in case you missed it.

@DMitry: good question! I’ve added a new section about custom validations using MP3 files as an example so hopefully it’ll help.

@Jon: you’re welcome and thanks for the plugin. Would be nice for us long-suffering Windows users to have the Tempfile patch in the plugin, one less thing for us to remember!

Comment on 'Goodbye attachment_fu, hello Paperclip' by Jon Yurek

2008-11-06T15:00:20Z

Thanks for the write-up! And thanks for that Windows Tempfile patch. I think that's worth adding into Paperclip itself.

Comment on 'Goodbye attachment_fu, hello Paperclip' by DMitry Shaposhnik

2008-11-06T07:45:33Z

Cool!

Could you describe how to do some pre/post-save actions with attachment? For example dealing with mp3: before_save :check_id3_tags or something else, what could reject saving of an attachment. Thanx!

Comment on 'Goodbye attachment_fu, hello Paperclip' by Matt

2008-11-05T23:10:07Z

Nice. I think I'm going to convert my hacked up code (pre attachment_fu and paperclip) to use this. It will clean things up a bunch! Thanks for the very clear article.

Comment on 'Goodbye attachment_fu, hello Paperclip' by Rechnung

2008-11-03T20:10:46Z

Very usefull post! Thank you!