Hi What would you say are the top reasons for getting this error? I don''t seem to have any of the example cases I''ve found searching with Google, and trying to trace through the stack is not giving me any clues. Any tips you have for me? Thanks in advance. jlb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
jlesleyball wrote:> Hi > > What would you say are the top reasons for getting this error? I > don''t seem to have any of the example cases I''ve found searching with > Google, and trying to trace through the stack is not giving me any > clues. Any tips you have for me? > > Thanks in advance. > > jlbtypically caused by good_var + ''abc'' + var_that_should_be_good_but_is_currently_nil_for_some_unexpected_reason # you prolly want to debug why that var is currently nil for some reason -- 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 -~----------~----~----~----~------~----~------~--~---
On Thu, 2008-04-17 at 00:45 +0200, Roger Pack wrote:> jlesleyball wrote: > > Hi > > > > What would you say are the top reasons for getting this error? I > > don''t seem to have any of the example cases I''ve found searching with > > Google, and trying to trace through the stack is not giving me any > > clues. Any tips you have for me? > > > > Thanks in advance. > > > > jlb > > typically caused by > good_var + ''abc'' + > var_that_should_be_good_but_is_currently_nil_for_some_unexpected_reason > # you prolly want to debug why that var is currently nil for some reason---- but it may be useful to note that var_that_should_be_good_but_is_currently_nil_for_some_reason.to_s = '''' instead of nil 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 -~----------~----~----~----~------~----~------~--~---