Hi Keith,

We ran into the same issue, but instead of sticking our custom Paperclip processors in Rails.root.join('config', 'initializers'), we worked around this issue as follows:

http://gist.github.com/482893

(which keeps the processors in the "standard" paperclip location) It does indeed appear though that this is something that needs to be fixed properly in Paperclip itself.

PS - based on our cursory investigation, this issue is caused by the Paperclip gem being loaded before the Rails object is properly configured... see the following snippet in the lib/paperclip.rb file

if defined?(Rails.root) && Rails.root
  # load custom Paperclip processors
end

Yes, your solution is certainly cleaner and agrees with the documentation as it stands now. Since (as I understand it) rails 3 loads gems as early as possible during app initialization maybe the loading code needs to be moved into application.rb permanently. It is more configuration but it could probably be reduced to a one-liner to call a class method in paperclip that loads the custom processors.

config.paperclip.custom_processors = :foo

No time to submit a patch so I guess this is a cry for help. :-)

Am also experiencing this problem. Wondering if the paperclip team has fixed this issue already?

Has there been any progress on this issue?

This has been fixed in [4e4f427]. Thank you :)