AFter some debugging, I got it working:

  acts_as_ferret (:fields => {:description=>{},
  :product_id=>{:index => :untokenized},
  :product_description=>{},
  :product_label_description=>{},
  :product_label_free=>{},
  :product_product_id_supplier=>{},
  :product_description_supplier=>{},
  :supplier_description=>{},
  :pub_date_sort => {:index => :untokenized_omit_norms, :term_vector => 
:no},
  :location_id => {:index => :untokenized},
  :tab => {:index => :untokenized}},:remote=>true)

Small difference in usage of {}

Izit Izit wrote:
> Some more info.
> 
> What I also find strange is that when I start Mongrel it shows:
> 
> => Booting Mongrel (use 'script/server webrick' to force WEBrick)
> => Rails application starting on http://0.0.0.0:3000
> => Call with -d to detach
> => Ctrl-C to shutdown server
> ** Starting Mongrel listening at 0.0.0.0:3000
> ** Starting Rails with development environment...
> Using AdapterExtensions
> Asked for a remote server ? false, ENV["FERRET_USE_LOCAL_INDEX"] is nil, 
> looks like we are not the server
> Will use local index.
> using index in script/../config/../index/development/mutation
> default field list: [:supplier_description, :description, 
> :product_description, :pub_date_sort, :product_label_description, 
> :product_label_free, :product_product_id_supplier, 
> :product_description_supplier]
> ** Rails loaded.
> ** Loading any Rails specific GemPlugins
> ** Signals ready.  TERM => stop.  USR2 => restart.  INT => stop (no 
> restart).
> ** Rails signals registered.  HUP => reload (without restart).  It might 
> not work well.
> ** Mongrel available at 0.0.0.0:3000
> ** Use CTRL-C to stop.
> 
> Why is it refering to AAF during startup. It only does this for the 
> Model I have the issue with, other models with AAF configured do not 
> show up during Mongrel startup. I have also check it with webrick and 
> some occurs.
> 
> 
> 
> Izit Izit wrote:
>> I am running revision 217 of the AAF plugin
>> 
>> Strange thing is that I have another model where remote => true is 
>> configured but this does not give an issue, only this specific model 
>> generates the problem as soon as remote is set to true.
>> 
>> The other model looks like this:
>> 
>> acts_as_ferret ({:fields => 
>> [:description,:label_description,:label_free,:product_id_supplier,:description_supplier,:supplier_description]
>>  
>> , :remote => true})
>> 
>> 
>> 
>> 
>> Jens Kraemer wrote:
>>> Hi!
>>> 
>>> 
>>> Do you use the latest acts_as_ferret (0.4.1)?
>>> 
>>> Jens
>>> 
>>> 
>>> On Wed, Jul 25, 2007 at 01:04:01PM +0200, Izit Izit wrote:
>>>>   :product_product_id_supplier=>{},
>>>> 
>>>> :no},
>>>>         from /opt/local/lib/ruby/1.8/drb/drb.rb:729:in `open'
>>>> /opt/local/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in
>>>> Posted via http://www.ruby-forum.com/.
>>>> _______________________________________________
>>>> Ferret-talk mailing list
>>>> [email protected]
>>>> http://rubyforge.org/mailman/listinfo/ferret-talk
>>>> 
>>> 
>>> --
>>> Jens Kr�mer
>>> webit! Gesellschaft f�r neue Medien mbH
>>> Schnorrstra�e 76 | 01069 Dresden
>>> Telefon +49 351 46766-0 | Telefax +49 351 46766-66
>>> [EMAIL PROTECTED] | www.webit.de
>>> 
>>> Amtsgericht Dresden | HRB 15422
>>> GF Sven Haubold, Hagen Malessa

-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to