Help shape the future of CMS PaaS release notes! Take this quick survey and share your feedback.
Help shape the future of CMS PaaS release notes! Take this quick survey and share your feedback.
Hi, some additional questions
Hi Eric,
Yes this is a regular MVC application hosted on DXP. The changes appear when they are published. This issue is occuring on all 3 environments - integration, preprod and production. We are using cloudflare CDN
Have you added AddCmsCloudPlatformSupport to your startup? (Enabling Cloud Support for CMS 12 - a look under the hood)
And can you reproduce this in a local development environment?
Yes, we have added AddCmsCloudPlatformSupport to startup file. We are not able to reproduce this issue locally.
What status code and cache control result will you get on the loaded document?
E.g
The status is 200 OK, and below is the cache control. This means it is getting cached at cloudlfare. Because once we clear CDN cache, and then click preview, then we can see the changes, then the doc gets cached again, and stops reflecting new changes.
Cool, then we know why.
It's recommended having CDN disabled in edit mode.
You can also (probably) bypass the CDN by using the webistes azurewebsites.net address.
Another approach is to have a separate domain, e.g. edit.yourdomain.com, and ensuring that CF won't cache that.
When we are updating any page/block data, first time clicking on View mode/preview shows the updated changes. But on further updating the page/block, both the View and preview mode keeps showing the previous data and does not show the updated changes. We have tried clearing cache and refreshing the page as well.
We are using the quick edit dialog to update the block, and save it.
We are on episerver cms 12.31.2.
Is there any caching in CMS that can be checked?