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 loaded, including all 
filesystem changes. A conversation with a very experienced Radiant user has 
described this behaviour as normal. 

I have never seen Radiant behave this way. I'd like to try your solution of 
changing set_cache_control. If I'm successful, I'll post it here.


On 2012-07-12, at 9:16 AM, Jim Gay wrote:

> 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 7:41 PM, John Moroney <jpmoro...@gmail.com> wrote:
>> 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 issue came up and was
>> fixed by Mr. Long, but that issue describes the behaviour. Any ideas would
>> be greatly appreciated.
>> The extensions are:
>> file_system_resources
>> page_factory
>> page_parts
>> ruby 1.9.2
>> radiant 1.0.1p180
> -- 
> Write intention revealing code #=> http://www.clean-ruby.com
> Jim Gay
> Saturn Flyer LLC
> 571-403-0338

Reply via email to