> The params hash get passed from the view to the controller.
Really? I'm definitely thinking the other way around. Let's think
about this for a minute. In the URL box of my browser I enter 'http://
my_host/members/update/15' and press enter. I would expect this
request to be routed to the update action of the members controller
and I would expect there to be an :id=>'15' entry available in params
for that action to use along with an :action=>'update' entry and
a :controller=>'members' entry. The action does its thing and renders
the default update view which is the view that I showed. As far as I
know, that's exactly what happens when I have the @profile=profile
line in my controller commented out. However, when I uncomment that
line, for reasons unknown to me, I get a totally different set of
parameters available in my action even though I used exactly the same
URL in my browser. It blows my mind! :)
So, to answer your question:
> you've shown a controller method. Is that method being
> called from the view you showed? Or generating the values passed to the
> view template?
It is the later, i.e., the controller method generates the values
passed to the view template.
> The request / response flow is what we need to
> understand to help you.
I hope that my response in this post has clarified the issue. If not,
please let me know. 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
-~----------~----~----~----~------~----~------~--~---
