I suspect this is more of an Azure question really. We have a site running Umbraco 7.3.8, which has two web apps for CMS and Frontend
As per the documentation we've set umbracoContentXMLUseLocalTemp to true, to encourage Umbraco to use temp storage. This moves the xml cache file to D:\local\Temporary ASP.NET Files\root\cac15514\4afd33e2\UmbracoData on the web app storage.
What we're seeing is that we can publish changes and the cache updates, however when we restart the web app the umbraco.config is replaced by an old one and reverts the content.
We have absolutely no idea where this old file is coming from or why.
Has anyone seen this or similar before? The Azure docs suggest that the app will return to its "Original State" on a restart, but why that means content from a week ago is anyone's guess.
I think we might just have to disable the local temp option.
We discovered the problem to be related to compilation snapshots, and believe that we have resolved it by setting the obscure Azure setting aspnet:PortableCompilationOutput to false in the web app.
Azure web app surfacing old xml cache on restart
Hi All,
I suspect this is more of an Azure question really. We have a site running Umbraco 7.3.8, which has two web apps for CMS and Frontend
As per the documentation we've set umbracoContentXMLUseLocalTemp to true, to encourage Umbraco to use temp storage. This moves the xml cache file to D:\local\Temporary ASP.NET Files\root\cac15514\4afd33e2\UmbracoData on the web app storage.
What we're seeing is that we can publish changes and the cache updates, however when we restart the web app the umbraco.config is replaced by an old one and reverts the content.
We have absolutely no idea where this old file is coming from or why.
Has anyone seen this or similar before? The Azure docs suggest that the app will return to its "Original State" on a restart, but why that means content from a week ago is anyone's guess.
I think we might just have to disable the local temp option.
Any help would be much appreciated!
Hello Dave,
May be something went wrong with the file permissions on the /data/umbraco.config file
Try to remove the /data/umbraco.config file and then 'Republish
Hi There,
I've tried that but the same file just pops back up following the restart.
Just in case anyone ends up here...
We discovered the problem to be related to compilation snapshots, and believe that we have resolved it by setting the obscure Azure setting aspnet:PortableCompilationOutput to false in the web app.
is working on a reply...