Looks like globalize (1.2) is not compatible with rails 2.2.2. I am
getting:
’
=> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)
=> Rails 2.2.2 application starting on http://0.0.0.0:3003
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:3003
** Starting Rails with development environment…
D:/projects/passdate2009/src/vendor/rails/activesupport/lib/
active_support/dependencies.rb:159:in require': undefined method render_file’ for class ActionView::Base' (NameError) Exiting from D:/projects/passdate2009/src/vendor/rails/railties/lib/ commands/server.rb:49 from D:/projects/passdate2009/src/vendor/rails/railties/lib/ commands/server.rb:27:in require’
from D:/NetBeans/ruby2/jruby-1.1.4/lib/ruby/site_ruby/1.8/
rubygems/custom_require.rb:27:in `require’
from script\server:3
’
gloablize rewrites render_file (in order to cache templates).
render_file does not more exist, though…
second:
this is IMHO not the problem. As mentioned above:
globalize aliases/overrides render_file (in order to cache
templates).
render_file does not more exist, though…
Rayn,
sounds tempting, BUT my (2 year-old-legacy) app is built on Globalize
and I would prefer to stay with Globalize, at least with this app…
Should I go back to Rails 2.1.x?
Rayn,
sounds tempting, BUT my (2 year-old-legacy) app is built on Globalize
and I would prefer to stay with Globalize, at least with this app…
Should I go back to Rails 2.1.x?
I would suggest yes. I am/was using Globalite and it is incompatible
with
Rails 2.2.2. Almost any internationalization (I18N) package had to
reach deep
inside Rails and change things the new built-in I18N will also be
changing. I
suspect that the immediate problem you were seeing would only be the
first of
many. Lock your app to 2.1.x or start the change to the built-in. I
will be
doing the changes today and will post how hard it was when it’s
completed.
Rails 2.2.2. Almost any internationalization (I18N) package had to reach deep
inside Rails and change things the new built-in I18N will also be changing. I
suspect that the immediate problem you were seeing would only be the first of
many. Lock your app to 2.1.x or start the change to the built-in. I will be
doing the changes today and will post how hard it was when it’s completed.
This is what I did to migrate from Globalite to Rails 2.2 I18N:
Be sure all tests pass.
Install the latest rails gem:
gem install rails
Update the app:
rake rails:update
This likely modifies config/boot.rb and may update the Javascripts and
may add
scripts to script/ directory.
It took me 2 1/2 hours from start to all automated tests passing. 5
controllers, 12 models, approximately 1400 LOC. Another 10-15 minutes
fixing
things the automated tests didn’t catch.