14 Mar 2011
09 Nov 2011
Link to this post
We have an internal site set up for editing and publishing content in Sitefinity. All changes made in the latter database are replicated to our production database on another server. We're running into an issue, however, with caching when a change is made to a page. While the changes made will be replicated to the production database, the page will not be updated on the production site without actually logging into Sitefinity on the prod site and clicking publish. What's odd is that neither recycling the app pool nor editing the web.config will force the page to refresh.
Is there a way to allow our internal published changes, once replicated, to force a publish on our production site?