MaD wrote:
>> @word = params[:search][:word] || params[:word] || "home"
> you can still do that. there is only a problem if params[:search] is
> nil. because then you'd try to evaluate nil.[] which again leads to an
> error. this is what Phlip wanted to tell you way up in this thread.
And if James Bond's posts still don't reflect that awareness, I did not want to
get into...
@word = params.fetch(:search, params).fetch(:word, 'home')
Another fix - both the GET and POST flavors of this action should have the same
params, meaning the both things which hit the action from a web browser should
put their goodies into :search=>{} block. That's a best practice...
--~--~---------~--~----~------------~-------~--~----~
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@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
