Hi, I’ve just updated rails from 1.1.6 to 1.2.1 and I’m getting the
following errors whenever I load a page that uses a class that uses
ferret. I have ferret 0.10.13 and acts_as_ferret. They were working
fine before the upgrade.
In case it’s any use, I moved a Rails 1.1.6 site to 1.2.1 the other day
with Ferret 0.10.14 and it’s working fine, though it doesn’t use
acts_as_ferret.
The dependencies system has changed in Rails 1.2, perhaps acts_as_ferret
is tickled by this. You might want to try including the Ferret
libraries manually, in config/environment.rb.
On Wed, Jan 24, 2007 at 11:39:45PM +0000, John L. wrote:
Ruby on Rails — Reloading Revamped
I have a live application here running aaf trunk, Rails 1.2.1 and Ferret
0.10.14 without problems. I’m not running Mongrel, though.
But it really looks like some dependencies issue. can you make sure
there is no other version of ferret lying around? It’d be also
interesting to know where ferret is installed (systemwide or frozen to
your app).
Jens
–
webit! Gesellschaft für neue Medien mbH www.webit.de
Dipl.-Wirtschaftsingenieur Jens Krämer [email protected]
Schnorrstraße 76 Tel +49 351 46766 0
D-01069 Dresden Fax +49 351 46766 66
On Wed, Jan 24, 2007 at 11:39:45PM +0000, John L. wrote:
Ruby on Rails — Reloading Revamped
I have a live application here running aaf trunk, Rails 1.2.1 and Ferret
0.10.14 without problems. I’m not running Mongrel, though.
But it really looks like some dependencies issue. can you make sure
there is no other version of ferret lying around? It’d be also
interesting to know where ferret is installed (systemwide or frozen to
your app).
Jens
Well I finally got around to testing this again after finishing a work
item today. I upgraded my ferret gem from 0.10.13 to 0.10.14. I also
installed acts_as_ferret 0.3.1 as a gem today(it wasn’t available as a
gem before). I added
require ‘acts_as_ferret’
in my environment.rb and my project ran in rails 1.1.6 fine. Next I
switched to rails 1.2.1(changed RAILS_GEM_VERSION = ‘1.2.1’ in
environment.rb) and did a rake rails:update (which didn’t do anything
related to my problem, I think). Ferret now seems to be working.
However, I’m getting another error:
HWBColorspace is part of the Rmagick gem. I think rails 1.2.1 breaks a
lot of backward compatibility. Now I need to decide if I want to
upgrade my Rmagick gem and hope that I won’t run into another
compatibility problem. May be I should stay with 1.1.6 as 1.2.1 is at
least 50% slower than 1.1.6.
HWBColorspace is part of the Rmagick gem. I think rails 1.2.1 breaks a
lot of backward compatibility. Now I need to decide if I want to
upgrade my Rmagick gem and hope that I won’t run into another
compatibility problem.
I doubt that updating the gem will solve your problem. Rails 1.2 just
has a different way of how it deals with dependencies - afair the main
difference is that it does not try as hard as older versions to resolve
missing classes - so maybe you are missing a require somewhere?
Jens
–
webit! Gesellschaft für neue Medien mbH www.webit.de
Dipl.-Wirtschaftsingenieur Jens Krämer [email protected]
Schnorrstraße 76 Tel +49 351 46766 0
D-01069 Dresden Fax +49 351 46766 66
It doesn’t seem to be common knowledge yet but are you running the
engines plugin? If so it needs to be updated to use rails 1.2+. And,
if you’re using login_engine and/or user_engine they will need to be
removed. In other words, you can’t use login_engine or user_engine and
rails 1.2+. And the engined plugin is what caused similar errors for
me.