I recently upgraded my application to rails 3.1 and generally everything seems to be working but one thing is driving me insane.
I have 2 main js files, we\'ll call the
I had the same problem, and I finally stumbled across something in my development.rb. I had config.action_controller.perform_caching
set to true, and changing it to false solved the problem.
I had the same issue, but config.action_controller.perform_caching
was already set to false.
For me and another guy I was working with, the problem was that Chrome was caching the page despite the settings in Rails.
To fix it, we just closed the tab, opened a new tab, and visited the site again.