We have a customer site that is supposed to be going live on Monday and we're having all sorts of problems with apparent caching issues.
For example:
We moved a main site section (which was hidden from nav) to be a sub-section of another site section and have 'unhidden' it. It is now (intermittently) showing up in the Main navigation menu as thought it was still in it's old site structure, but you get a 404 when you click on it because the page is no longer there of course.
When you publish a page you don't always see the newest version of the page. If you refresh/reload the page it can randomly show you the old version or the newer version.
We have tried republishing from the root downwards and we have turned off micro caching in the navigation component. What else can we try please?
If you're still experiencing issues, remove umbraco.config from the App_Data folder (which holds the published xml) and republish the site either using your method or browsing to /umbraco/dialogs/republish.aspx?xml=true so it will be re-created.
Thanks for your post. We did as you suggested and while it didn't work straight away, it seemed to work after a few random deletions of that file and some republishing at various levels. Hard to say which bit cured it though.
This sounds a lot like the issue some people seem to be having where we have to publish twice to get things to show up correctly. Could you have a look at that post? Are you using any aftersave event handlers that might be interfering (like the one in that topic)?
Caching issues - menu items still showing up etc.
Hi All
We have a customer site that is supposed to be going live on Monday and we're having all sorts of problems with apparent caching issues.
For example:
Claire,
If you're still experiencing issues, remove umbraco.config from the App_Data folder (which holds the published xml) and republish the site either using your method or browsing to /umbraco/dialogs/republish.aspx?xml=true so it will be re-created.
Hope this helps.
Regards,
/Dirk
Hi Dirk
Thanks for your post. We did as you suggested and while it didn't work straight away, it seemed to work after a few random deletions of that file and some republishing at various levels. Hard to say which bit cured it though.
Claire
This sounds a lot like the issue some people seem to be having where we have to publish twice to get things to show up correctly. Could you have a look at that post? Are you using any aftersave event handlers that might be interfering (like the one in that topic)?
is working on a reply...