On Wed, Sep 12, 2007 at 03:14:21PM -0400, Erik Morton wrote: > That was the problem. Sounds obvious now. Thanks again.
Ok. Now how do you deal with this? I'd probably do something like this in application.rb: before_filter :disable_ferret if RAILS_ENV == 'development' def disable_ferret MyModel.disable_ferret end Not nice but should do until aaf gets a proper config mechanism that allows setting variables in environment.rb that are read whenever acts_as_ferret is called. While I think of it - maybe a simple :readonly => true switch for the acts_as_ferret method would be even more straightforward instead of calling MyModel.disable_ferret in environment.rb? Cheers, Jens -- Jens Krämer http://www.jkraemer.net/ - Blog http://www.omdb.org/ - The new free film database _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
