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.
Here is my ferret config for the model in question:
acts_as_ferret( { :remote => true, :index_dir => "#{AAF_INDEX}/
supplier", :fields => { :supplier => { :store => :yes }, :name =>
{:store => :yes}, :private_description => {}, :title => {},
:ur
l => { :store => :yes }, :description => { :boost => 10.0 },
:su
pplier_id => { :store => :yes }, :supplier_name => { :boost => 10.0 },
:ke
ywords => { :boost => 10.0 }, :data => {}, :extract => {}, :city => {},
:st
ate => {} } } )
Does anyone have any idea what could reenable ferret?
Thanks,
Erik
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
