Thanks for the explanation, but I was looking more towards of why the application works after changing that setting, which should have nothing to do about how sessions work, which I believe to be the real problem.
I have noticed that when auto-complete fields are used and vaulues selected the session variables I store those values in work fine and contain data but when I change to production those session variables are not being updated. I am using one controller only, if that means anything. Thanks. On Apr 26, 7:19 pm, 7stud -- <[email protected]> wrote: > pepe wrote: > > Found a hack? > > > I looked into the environments folder and compared development vs. > > production. I found this line: > > > config.action_controller.consider_all_requests_local = false > > > I changed it to 'true' and the application now works. Any kind soul > > that could explain this to me? I'm not really a Rails expert. > > AWDWR(3rd), p 686 says: > > The default setting of true means that all exceptions will display error > and backtrace information in the browser. Set this to false in > production to stop users from seeing this information. > > -- > Posted viahttp://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 [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 -~----------~----~----~----~------~----~------~--~---
