On 25 April 2010 16:45, Hassan Schroeder <[email protected]> wrote: > On Sun, Apr 25, 2010 at 8:38 AM, RichardOnRails > <[email protected]> wrote: >> I think I see the cause of lack of communication between params in > >> Am I all wet about this? > > Yes. I think you are totally missing how the Web works :-) > > The params hash represents name/value pairs passed from a client > (browser, typically) to your server, either as a GET request's query > string, or as body parts of a POST request. > > So the life of a params hash is one request. If you want something > to persist beyond that, put it in session, store it in the DB or use a > hidden field in a form.
Or copy it into an @ variable in the controller action to make it available in the rendered view. But I believe for the OP's problem he does not require to use params (or persistence) at all. See my previous post. Colin -- 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.
