rob
April 8th, 2006, 09:39 PM
Never fear! The cause is usually related to how environment.rb and the new boot.rb work. The fix is usually simple too!
1. Backup your environment.rb file just to be safe.
2. Copy in config/environment.rb and config/boot.rb from a fresh install of a Rails instance (you can run ocs-install-rails again and make a junk instance, then delete it when you're done with it)
3. Copy any configuration you had from your previous environment.rb file into the new one.
4. Restart Lighttpd or if you're running Apache FCGI/CGI it should pick up the new files.
If this doesn't work, we recommend copying everything in app/*, config/database.yml, and any other files you've modified to a new Rails instance.
Thanks to mtcodex's blog post about this (http://mtcodex.net/archives/working/site_broken_after_updating_to_rails_11.php) for a handy guide.
1. Backup your environment.rb file just to be safe.
2. Copy in config/environment.rb and config/boot.rb from a fresh install of a Rails instance (you can run ocs-install-rails again and make a junk instance, then delete it when you're done with it)
3. Copy any configuration you had from your previous environment.rb file into the new one.
4. Restart Lighttpd or if you're running Apache FCGI/CGI it should pick up the new files.
If this doesn't work, we recommend copying everything in app/*, config/database.yml, and any other files you've modified to a new Rails instance.
Thanks to mtcodex's blog post about this (http://mtcodex.net/archives/working/site_broken_after_updating_to_rails_11.php) for a handy guide.