Out of Sync Pages


Authority Level: This report is available to level 9 and 10 administrators.

Pages are shown in the Out of Sync Pages report when an error occurs during a publish. An example of the type of error that would result in pages being included in this report is a loss of Internet connectivity during the publish process. It is anticipated that pages should rarely be marked as out of sync.

To remedy an out of sync page or pages, click the Publish All button and all publishing updates will be completed. The Out of Sync Pages report will display pages that are out of sync within any site within the account, regardless of which site the administrator is currently viewing.

Out of Sync Pages in Required Actions Report

In the Out of Sync Pages report, administrators can:

  • View the number of out of sync pages listed in the report
  • Filter results either by site name or path
  • Click on the hyperlinked page name to travel to the page
  • Use the Publish All button to publish all the out of sync pages listed in the report
  • Use the Export CSV button to export the list of out of sync pages for the account in CSV format
  • Sort by any file type, site name, or path

Publishing Dirty Pages

Whenever a page is moved or renamed, its subscribers (pages that link to it via a dependency manager tag) are marked as being "dirty" in the database. In this context, dirty means a page that has dependencies that will need to be republished in order to update it with the new link.

In order to support Multi-Target Publish (MTP), it is necessary to keep track of which files were published where, in order to know which versions need to be updated on any particular server.

Illustrative Example

This example includes a site with a production server, a test server, and a development server. The test server is on revision #10 of the page, the development server is on revision #15, and the page has never been published to the production server.

Whenever the page is republished as a result of a file that it links to being moved or renamed, the appropriate server gets updated with the correct version. Afterward, the file's dirty flag is cleared. However, if a page has never been published, as is the case in the example of the production server, it does not necessarily get automatically published, so the dirty flag remains.

This is the type of page that will be listed in the Out of Sync Page report until it is manually published by any publish action or with the use of the Publish All button on the Out of Sync Pages report.

After publishing out of sync pages, the pages are removed from the report. Any page checked out to a user remains checked out to the user.

Exporting the Out of Sync Report

  1. Navigate to Reports > Required Actions.

    Required Actions in the Global Navigation Bar
  2. From the Reports secondary navigation bar, select Out of Sync Pages.

    Out of Sync Pages in Required Actions Report
  3. Click Export CSV.

The report for the account is downloaded (dependent on browser settings) to the local computer in a CSV file. This includes the following information:

  • Path: Shows the root relative path and file name
  • Site: Shows the site to which the page belongs