> Commenting or uncommenting that line has nothing at all to do with what
> the controller is receiving in the params hash from a request initiated
> via a page rendered in the last cycle.

Or from a direct call from a browser.  My sentiments exactly.  That's
why I'm having so much difficulty explaining this behavior.

 > in fact, the
> view you showed is update.rhtml then that view will throw an error on
> nil.each if you comment out line 13.  You haven't mentioned that.  Is it
> happening or not?

Yes.  That is exactly what is happening.  I didn't mention it because
that is expected behavior and it's late enough in the game that I have
already ascertained everything I wanted to know so it really doesn't
matter to me.

> This is too hard to follow in fits and spurts.  Zip your app up and send
> it to me offline.  I'll take a look and get back to you with the
> explanation.

Do you want me to zip up the entire app directory and send it to you?
Is that what you're saying?  Please advise.  Thanks.

          ... doug

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

Reply via email to