Thank you very much for your help. It was a very stupid mistake and is solved now:
After upgrading to rails I removed the /vendor/rails folder, because I freezed rails. Then I've run $ rake rails:freeze:gems to freeze the new version (2.3.2). I forgot that I had to do this as root, so the freezed rails version was incomplete. I didn't notice that... This caused the include problem. To solve this problem I just had to run in my Application folder: $ sudo rm -r vendor/rails $ sudo rake rails:freeze:gems Make sure to also run the remove command as root, just trashing the folder in TextMate will not work. Thanks anyway! Bharat Ruparel wrote: > I am assuming that you don't have a statement like; > > RAILS_GEM_VERSION = '2.2.2' unless defined? RAILS_GEM_VERSION > > Since you were doing fine until you installed the gem in question. If > you have not updated it for Rails 2.3.2 then do so and try again. > > If that does not work then my advice would be to: > > a) back up everything, and > > b) downgrade again to 2.2.2 by installing Rails 2.2.2 gems and > activating that version by uncommenting the statement > > RAILS_GEM_VERSION = '2.2.2' unless defined? RAILS_GEM_VERSION > > And then try again. Until you get to the troublesome gem. Then if > you can install it as a plugin so that you can debug it in your > application environment instead of the global environment. > > It is a step-by-step process and you have to test every step of the > way. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
