If the Publishing Queue shows 'Success' but you see stale content on the website

Stale content may point to a workflow problem, a caching problem, or a problem with multiple Content Deployers . Note that unpublished content that remains visible on the website is also stale content.

Check the following areas:

Workflow

Is the content you are publishing in workflow? If so, has it reached an Approval Status that allows it to be published to the selected Target Type? If not, this is why you are still seeing stale content.

Caching
If you use caching, and if you see your published item on your Presentation Server as a file or in your Content Data Store as a database record, check the following:
  • Is caching enabled in the Storage Layer configuration files (cd_storage_conf.xml) of the Content Deployer and of the website? In both of these files, the ObjectCache element must have its Enabled attribute set to true.
  • Are the correct types of content configured as able to be cached in the two Storage Layer configuration files? This is configured in the cached attribute of the ItemTypes element and (possibly) in the cached attributes of individual Item element inside the ItemTypes section.
  • Is your website caching the same type of content as your Content Deployer? For example, if you configured your Content Deployer not to cache binaries, is your website doing the same?
Cache synchronization using JMS
If you use a JMS provider to synchronize caches, check the following:
  • Is your JMS provider up and running?
  • If you are still using the deprecated in-process setup, are the host and port on which the JMS provider is running the same host and port as specified in the RemoteSynchronization section of the Storage Layer configuration files of the Content Deployer and of the website? Are they the same as the host and port configured in Content Deployer and the Content Interaction Services (CIS)? Note that the hosts may be different, as long as they refer to the same IP address (ping each host to confirm this).
  • Can you create a telnet connection to the host and port using the telnet HOST PORT command, where HOST is the host name and PORT is the port number? If this results in an empty screen and no connection denied, then something is listening on that port.
  • Have you (re)started any Content Delivery Server Role after your JMS provider? You should always stop or (re)start your JMS provider before stopping or (re)starting your other Content Delivery Server Roles, such as the Content Deployer and the website.
  • Is your Content Deployer sending invalidation messages through the JMS provider? Check your Content Deployer log.
Cache synchronization using the Cache Channel Service
If you use the deprecated Cache Channel Service, check the following:
  • Is your Cache Channel Service up and running, either as a Windows service or as a Java process (found on Unix using the ps -ef com.tridion.cache.CacheChannelService command)?
  • If you are also still using the deprecated in-process setup, are the host and port on which the Cache Channel Service is running (configured as startup command line arguments) the same host and port as specified in the RemoteSynchronization section of the Storage Layer configuration files of the Content Deployer and of the website? Are they the same as the host and port configured in Content Deployer and the Content Interaction Services (CIS)? Note that the hosts may be different, as long as they refer to the same IP address (ping each host to confirm this).
  • Can you create a telnet connection to the host and port using the telnet HOST PORT command, where HOST is the host name and PORT is the port number? If this results in an empty screen and no connection denied, then something is listening on that port.
  • Have you (re)started any Content Delivery Server Role after your Cache Channel Service? You should always stop or (re)start your Cache Channel Service before stopping or (re)starting your other Content Delivery Server Roles, such as the Content Deployer and the website.
  • Is your Content Deployer sending invalidation messages to the Cache Channel Service? Check your Content Deployer log.