Staged content showing up in prod without being synched

Krysta Hunt asked on May 22, 2017 17:26

This has happened to me twice in the last few days, where content that I have been working on in stage (published)has been live in production.

  1. the synch scheduled task is completely disabled
  2. the edit page view of the page in production shows all of the old content.
  3. the version history of the page in production shows no recent publish events.

  4. in stage, all of the synch tasks related to this page are still sitting in my task group waiting.

The only possibility I can think of is that for some reason the cache from stage is becoming active in production through me being logged into both on the same browser at the same time.

Anyone else experienced this? is it a known happenstance? is there a best practice or is this a bug? could anything else be causing the issue?

Recent Answers


Prashant Verma answered on May 22, 2017 17:45 (last edited on May 22, 2017 17:45)

Hi krysta, Can you please be more specific with kentico version you are using, are you using any third party storage ? Please share some more info. Thanks

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on May 22, 2017 17:54

Are there other editors on your site making changes as well? If so, is it possible they are making changes and publishing their changes which might include your changes?

You might also look into other tools for staging changes which work very well.

0 votesVote for this answer Mark as a Correct answer

Krysta Hunt answered on May 22, 2017 19:24

the latest version of 9, there were other editors but we have a very strict content approval and publish process. Plus if the content had been published by anyone, a version would have shown up in the versions of the page and the page preview would show the new content, neither of which is true.

0 votesVote for this answer Mark as a Correct answer

Trevor Fayas answered on May 22, 2017 19:37

To me it sounds like something on the live site is looking at the staging site.

First things to look at, are is there any queries or such that are accidentally referencing the staging site through a full table name (ex: [Kentico_staging].[dbo].[CMS_Tree])

Second, i would look to any custom global module loader that may be catching certain page events and automatically pushing them.

Thirdly, check your hosts, make sure you're looking at the production server.

Fourthly, take a look at the database, find the record and see when it was last modified, was it pretty much instantly after you made the change on staging, or what was the delay? are there any other events that occurred around the time of the modification?

Some good places to start.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.