Rails - Apr 2008 - How to find nil object error in the rails application?

After I added some plugins to rails my application it begin to give
following error.

  Error during failsafe response: You have a nil object when you didn''t
expect it!
  The error occurred while evaluating nil.symbolize_keys
  (originally You have a nil object when you didn''t expect it!
  The error occurred while evaluating nil.symbolize_keys)

But there is no stack trace I dont know why?

When I searched in the code symbolize_keys is used in lot of places. So
I dont understand which one is error reason.

Could someone teach me how to investigate such error?

I really have no experience in debugging rails application?
-- 
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

rake test                      # Test all units and functionals
rake test:functionals
rake test:integration
rake test:plugins
rake test:recent
rake test:uncommitted
rake test:units

if you want do trace rake test --trace

reinhart
http://teapoci.blogspot.com

-- 
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

or you can use it :

http://snippets.dzone.com/posts/show/697
-- 
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Without a backtrace, all I can think of right now is to remove plugins
one-by-one until the error goes away. Once you eliminate the error,
you''ll
know that the last plugin that you removed was causing the problem. Of
course, the problem could be caused by the interaction of two or more
plugins. Thus, once you''ve identified the offending plugin, you may
want to
remove all other plugins that you can and try just the offending plugin to
see if it still causes problems.
Good luck,
Craig

--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---