Monday 28 January 2008 8:34:29 pm
We have a page on our municipal council website which displays a 4 day weather forecast using an XML feed. The feed is working, but the page on our production site often displays data up to four days old, presumably because of caching. The same page on our dev site, which is not cached, always displays correct data. The data is displayed using <custom name> tags in a "page" that is actually the description field of a published folder. To force an update on the production site, I have to manually clear the Content View Cache. It will occasionally update itself, but without any discernible pattern. As an eZ publish newbie, I don't know where to start trying to fix this. I've tried adding a {cache-block expiry=3600}{/cache-block} around the design template that publishes the forecast data (it is part of a custom extension), but it has no effect. Do cache blocks work at this level? Should I set up a cron job to force a daily clearance of the Content View Cache?
Is it normal for a site to go 3 or 4 days without the Content View Cache being renewed? Should this cache should be renewed every two hours by default? Any other suggestions? We only need this particular page/cache to be renewed once or twice a day. I've read the documentation on cache-blocks but haven't found it particularly useful so far.
|