We have two publishing targets, staging and live.

When we publish certain pages, the content is not updated on the staging site, even though the publishing job shows a 'Success' message in the queue. Publishing the same page to live works just fine, with the content updated.

Other pages can also be published to staging and the content updates accordingly. Is there any reason why content for certain pages would not update, when publishing to a specific target, with a 'Success' message being displayed? Is there some other suggested ways to diagnose the problem? We've looked in server logs.

We’ve tried:

  • To restart the HTTP deployer and all Tridion windows services
  • To build the page with the Tridion template builder (this works as expected, with expected output produced).
  • We’ve seen a few errors from the last few days in the logs: ERROR HTTPSTransportConnector - An unexpected error occurred while polling: http://servername:8082/httpupload.aspx reason: Internal Server Error. This could be related, but is not logging any error for the specific publish transaction, so it may be a red herring.
  • To increase the length of the URL – we’ve had issues where the URL has been too long in the past (as the deployer task which adds the xml files on to the server fails because the total length of the path on the file system exceeds the maximum allowable characters). However, I don’t think this is the problem here as when we increase the length of the URL, publishing to staging still works.
  • I also don't think it's link levels that is the problem, as it wouldn't work to publish the page to another target then. Also, if items were checked out or in a workflow, then we also wouldn't see the latest content when publishing to the live target.

UPDATE: I've checked the Tridion Broker database and the [PAGE_CONTENT] table has got the latest text in the 'Content' column for the given page id. Hence, I'm thinking that the reason why the content is not updating on our staging site must be because of some caching issue. The cd_storage_conf.xml file has ObjectCache Enabled="false" set in it. Is there any other caching that could be happening, which means that old content is served?

  • 1
    If I understand correctly, the page contents gets published in the broker database, , so not on the filesystem. Does this mean you are using DXA, or DD4T, or any other custom built framework ? Commented Feb 19, 2019 at 12:44
  • Yes, we use DD4T Commented Feb 19, 2019 at 12:48
  • Can you check that the cd_storage_conf.xml of the deployer contains the same database information as the cd_storage_conf.xml of the content service (or the web application in case of an in-process setup)?
    – Quirijn
    Commented Feb 19, 2019 at 13:05
  • I've checked this, and the only difference is that the pool size is different. It's 5 in one and 10 in the other, but I don't think that should make a difference. Commented Feb 19, 2019 at 14:33
  • And I guess if you restart the web application on staging, the new content is showing?
    – Quirijn
    Commented Feb 19, 2019 at 15:34

1 Answer 1


The fix for the problem was similar to that for a question already published here:

Clean the ghost published records

For some reason we had a bunch of 'orphan records', which were pulled in for the given page URL when publishedm, instead of the content for the new page TCM id.

Doing what was suggested by Marko at the above link allowed us to work around the problem.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.