That was the problem. Sounds obvious now. Thanks again. Erik On Sep 12, 2007, at 2:10 PM, Jens Kraemer wrote:
> On Wed, Sep 12, 2007 at 01:37:55PM -0400, Erik Morton wrote: >> In my environment.rb I say the following: >> >> MyModel.disable_ferret >> puts MyModel.ferret_enabled? >> >> The console works as expected: >> >> script/console >> false >>>> MyModel.ferret_enabled? >> => false >> >> I can then edit an instance, ferret remains disabled and the changes >> are not immediately indexed. >> >> However, when I start mongrel Ferret is initially disabled, but then >> somehow becomes enabled again after the first request. I don't >> explicitly enable ferret anywhere. > > is this happening in development or production mode? This might be an > issue with the class reloading done in development mode, where the > class > is reloaded, but environment.rb isn't parsed again. > > 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 _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
