I think this might have to do with Rails reloading classes in development mode.
If we set the timeout during the initialization process, that step is
skipped during a reload.
Of the top of my head, it might be necessary to rewrite
set_cache_control to overcome this.
-Jim
On Wed, Jul 11, 2012 at
Jim,
Thanks for the reply. I think I've narrowed the issue down to file system
resources. If the file system is changed and saved, the cache does not refresh.
A web inspector shows the 300 second setting. If, however, a page is saved in
the CMS itself, the cache refreshes and the changes are
I'm in the development environment and the cache is locked on five minutes.
The config settings are correct, and I see nothing obvious in the
extensions that would cause a conflict.
This install was also working just fine until it wasn't.
I noticed on line 525 of the changelog that a similar
