Building Software Better . . . One Programmer at a Time
This video goes over some issues that popped up while upgrading a Rails 3 application to the Release Candidate
This video goes over some issues that popped up while upgrading a Rails 3 application to the Release Candidate.
Download 131 MB
Download (iphone & ipod) 11.7 MB
Previous post: Ruby’s Enumerable Module: The Inject Method
Next post: Rails 3 Documentation: Generate Your Own
Anybody can learn to write code. The hard part is solving problems, not typing commands. This means that learning to program is a mental exercise followed by its interpretation into code.
TeachMeToCode.com is about helping you learn to think about problems and how to write code once you've figured out what you want. Sign up for the mailing list, watch a video, listen to the podcast, or read an article to get started.
{ 6 comments }
Maybe the routes deprecation error is caused by the block variable 'map' that is passed? It's not needed anymore..
For the DSL deprecation warning just take the |map| off the end of the start of the routing block:
YourApp::Application.routes.draw do
instead of
YourApp::Application.routes.draw do |map|
I really didn't check new Rails routing thoroughly, but I noticed you have “routes.draw do |map|”. If I had to guess, I'd guess the “|map|” part is the one giving you deprecation warnings.
Thanks for the help. Feedback like this helps everyone and it's why I released a video without the answer in it.
Running `rake rails:update` helped me zero in on the cause of the deprecation warning. You may also want to run `bundle update` (replaces lock and unlock) to update your gems.
In your Rakefile, Rails::Application needs to be changed to YourAppName::Application
Comments on this entry are closed.