Or SWFUpload and attachment_fu. SWFUpload does have some caveats you
need to overcome and I should start a blog and write a post on it.
Basically it comes down to overcoming Rails 2’s security measures
without disabling them and it’s perfectly possible. There are some
posts around that deal with it, but they all have their flaws. I’ll
just post some relevant sections of my code in here so everyone at
least has a reference to go by (it should be indexed by google).
Make a file “swf_session.rb” in config/initializers/ with
as the contents (this is a slightly modified version of the original
Include the following in your layout (and put the appropriate files
automatically add all of your app’s cookies as POST parameters):
:cache => “swfupload”)
Add this in the section of your layout:
Optionally you can add this to your application.js file (to
automatically add the authenticity token to all your custom
this is part of that code (you’ll need to implement all the handlers
and adapt the code to your application of course):
file_post_name : “document[uploaded_data]” is the name of the model
instance and field you want to post to (@document.uploaded_data),
attachment_fu automatically handles this field.
Expose the relevant controller actions (the ones that handle the
uploads) so the session can be passed in as a POST variable:
class DocumentsController < ApplicationController
session :cookie_only => false, :only => :create
Add the mime-types gem to config/environment.rb as a requirement:
config.gem “mime-types”, :lib => “mime/types”, :version => ‘>= 1’
Patch the attachment_fu plugin a little: vendor/plugins/
This is just to make your life easier and let attachment_fu do its
magic without you having to worry about setting the content_type.
Implementing SWFUpload can be quite an adventure and you really need
to understand what’s going on, but the result is the best “ajax”
upload you can imagine.
On 31 Jul 2008, at 16:26, Benjamin C. wrote:
Thanks in advance for any advice.
Peter De Berdt