[PATCH] Dependency bug in rails 2.0.1

same fix as previous patch, but diff made from rails root (if that helps)

+1 (Verified using Rails-2.0.2)

+1 Also verified using Rails 2.0.2

I guess we'll need to investigating a little more into the fix I suggested. I'm still not very clear/satisfied about appropriate use cases of to_prepare callbacks. What is it that you do in to_prepare callbacks that you cannot do witj after_initialize callbacks ?

Thanks.

My usage of to_prepare dynamically generates some ActiveRecord classes and various associations with existing classes.

Regardless of my usage, the error still occurs with no code in the to_prepare block as outlined in my example.

lifofifo, we're still using config.to_prepare to patch application classes from plugins. It's most probably not what this hook initially has been meant for. But it's a place where you can hook in stuff that needs to be re-run when app classes have been unloaded.

+1

+1

patch verified to work on rails 2.0.2

For those that need fix NOW (who does not?) and do not want to keep vendor/rails, here is quick monkey patch, paste in environments.rb just before first call to config.prepare_to:

#fixes rails bug described here: http://dev.rubyonrails.org/ticket/10520
#this monkey patch should be removed when problem is fixed in rails
  module Rails
    class Configuration
      def to_prepare(&callback)
        after_initialize do 
          require 'dispatcher' unless defined?(::Dispatcher) 
          Dispatcher.to_prepare(&callback) 
        end 
      end
    end
  end

(In [9211]) Fix that config.to_prepare dependency error. Closes #10520 [akaspick, Pratik]