Page cache

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? 

Thanks

Hi Jon,

Can you give us more information about your infrastructure as this is expected behaviour on a setup that is not running in NLB.

Greetings,
Victor Velev
the Telerik team

Hi Victor,

There really isn't much more to explain. We basically replicate all database transactions on our internal server to our production server. I don't think the CMS is acting unexpectedly; however, I would like to a page to be refreshed when a database change occurs so I don't need to log in into the production site and actually click the publish button on the page.

Thanks for you help!

Hi Jon,

If your internal and production sites are using one database, the desired scenario can only be accomplished in NLB.

Regards,
Victor Velev
the Telerik team

Hello Jon,

Just a quick follow up: if the above proposed solution is not suitable for you ( your sites are not using one database ) please explain what do you mean by 'replicated' and provide some additional information about your architecture and setup.

Kind regards,
Victor Velev
the Telerik team