The cache is by default activated on the public instance only.
The cache is available as finish html-files in magnolia/cache/default On requesting a page, the cache is first checked. If no corresponding html file is found, it is then generated and stored. When activating content for a corresponding page, its cached html file is deleted. If the content remains the same after activation, then there's something wrong. Keep an eye on the logs and see if there's any hints on what has happened. Like in any caching system, it is not faultless. You can force a removal of the cached files simply by deleting the contents of the cache folder. On 5/3/06, Ingo Bergen <[email protected]> wrote:
hi, we have the following problem: after editing an existing site and publish this site to the public the content is the same as before? how does the caching mechanism works exactly?
---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
