Hi I upgraded Rails using the GEMS utility and now my app doesn''t work. I get Not Found `/projects/list/'' not found. _____ WEBrick/1.3.1 (Ruby/1.8.2/2004-12-25) at localhost:3000 #<NameError: uninitialized constant Controllers> I have rolled back to gem uninstall rails gem install rails -v 0.9.4 but I am still getting errors like #<NameError: uninitialized constant ListController> I cant remember what version I was originally running on but I installed it about 1 Feb. Hope someone can get me up and running again (on XP) Peter _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
On Sunday 20 February 2005 18:17, Peter Cutting wrote:> Hi > I upgraded Rails using the GEMS utility and now my app doesn''t work.I''m not what the official line is, but whenever I upgrade to a new set of gems, I create a new rails application and then merge my old applications app, config and lib folders into the new version. Without this, changes made in places such as config/environment.rb will bite you.> #<NameError: uninitialized constant Controllers>If you want to get this to work, add Controllers = Dependency::LoadingModule.root(File.join(RAILS_ROOT, ''app'', ''controllers'')) to your config/environment.rb> I have rolled back to > > gem uninstall rails > gem install rails -v 0.9.4If you want to roll back, you''ll have to remove the newer gems for rails, actionpack, actionmailer, activerecord, activesupport, and actionwebservice. It appears that you actually updated to beta gems, which are unstable (as the beta implies). You probably wanted to upgrade to the latest stable Rails (0.9.5). You can avoid upgrading to beta gems by not giving gems the ''-s http ...'' arguments. -- Nicholas Seckar aka. Ulysses
On 21.2.2005, at 07:12, Nicholas Seckar wrote:> r config/environment.rb > >> I have rolled back to >> >> gem uninstall rails >> gem install rails -v 0.9.4 > If you want to roll back, you''ll have to remove the newer gems for > rails, > actionpack, actionmailer, activerecord, activesupport, and > actionwebservice. > > It appears that you actually updated to beta gems, which are unstable > (as the > beta implies). You probably wanted to upgrade to the latest stable > Rails > (0.9.5). You can avoid upgrading to beta gems by not giving gems the > ''-s > http ...'' arguments.You can also tie your rails app to specific versions of rails, ar and ap by changing your config/environment.rb like this: # Require Rails gems. require ''rubygems'' #require_gem ''activerecord'' #require_gem ''actionpack'' #require_gem ''actionmailer'' #require_gem ''rails'' require_gem ''activerecord'', ''= 1.6.0'' require_gem ''actionpack'', ''= 1.4.0'' require_gem ''actionmailer'', ''= 0.6.1'' require_gem ''rails'', ''= 0.9.5'' You should actually never have to downgrade your gems, all old versions are kept when you upgrade. You can see this by running ''gem list''. //jarkko> > -- > > Nicholas Seckar aka. Ulysses > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Jarkko Laine http://jlaine.net http://odesign.fi _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Subversion is great for this sort of thing. 1. create a new rails app 2. make sure your existing project is up-to-date (svn update, status, commit, etc) 3. copy the new project files over the old project 4. svn diff, merge and revert various files. -Dale On Mon, 21 Feb 2005 00:12:30 -0500, Nicholas Seckar <nseckar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On Sunday 20 February 2005 18:17, Peter Cutting wrote: > > Hi > > I upgraded Rails using the GEMS utility and now my app doesn''t work. > I''m not what the official line is, but whenever I upgrade to a new set of > gems, I create a new rails application and then merge my old applications > app, config and lib folders into the new version. Without this, changes made > in places such as config/environment.rb will bite you. > > > #<NameError: uninitialized constant Controllers> > If you want to get this to work, add > > Controllers = Dependency::LoadingModule.root(File.join(RAILS_ROOT, ''app'', > ''controllers'')) > > to your config/environment.rb > > > I have rolled back to > > > > gem uninstall rails > > gem install rails -v 0.9.4 > If you want to roll back, you''ll have to remove the newer gems for rails, > actionpack, actionmailer, activerecord, activesupport, and actionwebservice. > > It appears that you actually updated to beta gems, which are unstable (as the > beta implies). You probably wanted to upgrade to the latest stable Rails > (0.9.5). You can avoid upgrading to beta gems by not giving gems the ''-s > http ...'' arguments. > > -- > > Nicholas Seckar aka. Ulysses > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- All creativity is an extended form of a joke. - Alan Kay