Changes to erb files not being noticed by server

Did you run server in production environment? Is the any page, action or fragment caching?

Although my guess would be your browser cache. Have you tried browsing with cache disable? Web developer plugin for Firefox could easily disable cache

Cheers! Arzumy

Arzumy wrote:

Did you run server in production environment? Is the any page, action or fragment caching?

I am assuming I am running in development mode as the development log is being filled by the server.

If I use reload I thought the browser would request the page again from the server, which it does according to the development log. The server manages to find the index.html.erb page even after I have deleted the page from the view folder.

It appears as though the server is caching the page. Which implies it is in production mode.

Have you accidentally (or on purpose) changed any settings in confg/environments/development.rb? In particular check config.cache_classes = false config.action_controller.consider_all_requests_local = true config.action_controller.perform_caching = false

Colin

Probably a dumb question, but have you checked to make sure there weren't actually "duplicate' files in the view directory? For example, does anything like both "index.html.erb" and "index.html.erb.swp" exist in app/views/whatever ?

Good point, .bak files have also been known to cause problems.

Colin

Good point, .bak files have also been known to cause problems.

I am using Ultraedit as my text editor which leaves behind a .bak file.

If I delete the bak file before reloading the browser then the updates I made appear on the screen immediately.

It was interesting, after I deleted the .bak and reloaded the browser, Rails complained the view file had disappeared. On hitting the reload button a second time the real erb file with the changes was displayed by the browser. Rails preferred the .bak file to the erb file.

I am sure I used Ultraedit to edit files elsewhere without the .bak problem getting in the way. It was also recommended as an editor for Rails in Simply Rails 2 by Patrick Lenz

I now just have to work out if I need to change editor or if there is a way to fix the leaving of .bak files behind.

Thanks for shedding light on this curious and infuriating problem.

Cheers,

Roy

I have just been through the Ultraedit help and found there are several options available for using the .bak file.

Thanks once again.

Roy

This was a bug in Rails at some version (not sure which), it was fixed by 2.3.2 or possibly earlier I think. Which version are you using?

Colin

I am running Rails 2.3.2.

Cheers,

Roy

Maybe it was 2.3.3 it was fixed in then, or maybe I am talking rubbish.

Colin