Recently we ran in a very strange caching bug with one of our umbraco sites.
Durning testing we discovered that when altering some properties on a doctype didn't trigger a flush of the umbraco cache. So even though in the backend the property correctly shows the new value, the front-end keeps displaying the original value. The steps we took so far are:
Deleting the Umbraco.config file from the App_data folder and republishing the entire site: no effect
Cross referencing the staging environment with the development environment: they both have the same issue
Checking the umbracoSettings.config for the XmlCacheEnabled and ContinouslyUpdateXmlDiskCache settings: they are both set to true
None of these things resolved the issue.
the only thing that does work is restaring the application pool the website is running in.
What could this be? obviously constantly restarting the app pool isn't an option and the only option that is left is backtracking in our version control system to figure out when this issue strated occuring.
found it! it was a bug in our own code with some static variables used for temporary caching after an import of an external system. Not a problem with umbraco itself.
Strange Caching Bug
Recently we ran in a very strange caching bug with one of our umbraco sites.
Durning testing we discovered that when altering some properties on a doctype didn't trigger a flush of the umbraco cache. So even though in the backend the property correctly shows the new value, the front-end keeps displaying the original value. The steps we took so far are:
Hi Martjin
What version of Umbraco are you running?
/Jan
Jan,
This condition occurs in Umbraco version v 4.7.0 (Assembly version: 1.0.4090.38017).
Thanks,
Pieter
Check you are only running a single worker process this can mess up caching.
found it! it was a bug in our own code with some static variables used for temporary caching after an import of an external system. Not a problem with umbraco itself.
Thanks for the replies
is working on a reply...