If the Publishing Queue shows 'Success' but you see stale content on the website
Stale content may point to a workflow problem or a caching problem. Note that unpublished content that remains visible on the website is also stale content.
- 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 application properties file (application.properties) of the Content Deployer and of the (Session-enabled) Content Service? In both of these files, the
cache.enabledelement must resolve to the valuetrue. - Are the correct types of content configured as able to be cached in the application properties file (application.properties) of the Content Deployer and of the (Session-enabled) Content Service? In both of these files, individual parts of the cache can be enabled or disabled using the
cache.CACHENAME.enabledproperty. These settings must match across the two services. - Overall, are the caching configurations, both in application.properties and in the specific caching configuration file (config/cache-conf.xml by default), the same for both services?
- Is caching enabled in the application properties file (application.properties) of the Content Deployer and of the (Session-enabled) Content Service? In both of these files, the