It took a fair bit of trial and error to reach this level of understanding, so I hope one of you experts can help me on this!
I have an Umbraco installation setup with 4 nodes off the root, each linked to a different host name.
If I log into the Umbraco admin area using one of the domains, and update content for that domain, everything works fine.
If I try to save and publish content for the nodes linked to other domains, the umbraco.config file is updated with the changes, but they do not appear when I browse to the appropriate public web links.
(Yes, I've checked that it isn't related to any browser caching!)
So, my question is, are there any settings I can tweak (in either Umbraco or IIS) which will allow updates to any node from any domain to be published and correctly cached.
I don't want to turn the XML caching off for performance reasons.
This sound like an issue I also read and replied at last week here on the forum. You can find it here. The problem seems to have something to do with the setup in the IIS. Maybe you can try reading through the other thread, and try out some of the ideas that we talked about there.
On my IIS, each host name is bound to a separate IIS website (for logging purposes), pointed at the same physical path, but sharing an app pool.
Given the size of the app pool (~240MB for 4 very small sites all based on the same template and generating minimal traffic so far), I'm a bit loathe to point the sites at separate app pools.
In my mind, if they're all sharing the same database and content, it actually makes sense that they share an app pool as well. The app pool size is something I mentioned on another thread as I was surprised by how large it is.
The caching sites based on the same template separately so that they don't all show updates? A simple recycle of the app pool does the trick as a workaround..
XmlContentCheckForDiskChanges setting in umbracoSettings.config might be the setting you're looking for.
It seems like umbraco has two levels of cache. One in the xml file, and one in memory. When restarting IIS, or overwritting web.config, the inmemory cache gets erased, and reread from the XML file.
When XmlContentCheckForDiskChanges is set to true, umbraco should check if the xml cache has changed, and if it has, it should update the inmemory cache.
Umbraco caching issues - multiple hostnames
It took a fair bit of trial and error to reach this level of understanding, so I hope one of you experts can help me on this!
I have an Umbraco installation setup with 4 nodes off the root, each linked to a different host name.
If I log into the Umbraco admin area using one of the domains, and update content for that domain, everything works fine.
If I try to save and publish content for the nodes linked to other domains, the umbraco.config file is updated with the changes, but they do not appear when I browse to the appropriate public web links.
(Yes, I've checked that it isn't related to any browser caching!)
So, my question is, are there any settings I can tweak (in either Umbraco or IIS) which will allow updates to any node from any domain to be published and correctly cached.
I don't want to turn the XML caching off for performance reasons.
Thanks,
Martin
Hi Martin.
This sound like an issue I also read and replied at last week here on the forum. You can find it here. The problem seems to have something to do with the setup in the IIS. Maybe you can try reading through the other thread, and try out some of the ideas that we talked about there.
/Kim A
Hi Kim,
On my IIS, each host name is bound to a separate IIS website (for logging purposes), pointed at the same physical path, but sharing an app pool.
Given the size of the app pool (~240MB for 4 very small sites all based on the same template and generating minimal traffic so far), I'm a bit loathe to point the sites at separate app pools.
In my mind, if they're all sharing the same database and content, it actually makes sense that they share an app pool as well. The app pool size is something I mentioned on another thread as I was surprised by how large it is.
Any other ideas at all?
Martin
Quick bump for this one if I may..
Does anyone have any further suggestions for a solution to this at all?
Thanks,
Martin
Another quick bump on this one. Is anyone able to help?
Martin
Hey Martin, did you ever get this resolved? Running into the same issue.
The caching sites based on the same template separately so that they don't all show updates? A simple recycle of the app pool does the trick as a workaround..
Martin
XmlContentCheckForDiskChanges setting in umbracoSettings.config might be the setting you're looking for.
It seems like umbraco has two levels of cache. One in the xml file, and one in memory. When restarting IIS, or overwritting web.config, the inmemory cache gets erased, and reread from the XML file.
When XmlContentCheckForDiskChanges is set to true, umbraco should check if the xml cache has changed, and if it has, it should update the inmemory cache.
/Martin
I had the same issue and the XmlContentCheckForDiskChanges worked for me. Thanks Martin!
- Eskil
is working on a reply...