The Push Publishing feature allows you to Remotely Publish multiple types of content from one server to another server. You can use the same simple process and interface to Publish Content, Hosts and Folders, Dynamic plugins, Users and Content Types.
To add Content to the Publishing Queue (Content that is scheduled to be Published), right-click on the content and select Push Publish from the menu.
On the Content Search screen, you can select multiple content items for Push Publishing at the same time. Select the checkboxes for all the items you want to Push Publish, click the AVAILABLE WORKFLOW ACTIONS button at the top of the screen, and then press the PUSH PUBLISH button from the popup.
Push Publishing Options
After selecting Push Publish, a popup displays with the following options:
|I want to||What you want to do with the selected content: |
|Publish Date||The date on which the Content will be published.|
Defaults to now (publish immediately).
Only applies if Publish or Publish and Delete are selected (see above).
|Expire Date||The date on which the Content will be unpublished.|
Defaults to now (publish immediately).
Only applies if Delete or Publish and Delete are selected (see above).
|Force Push||Force the Content to be Pushed, even if it does not appear to have changed since the last push.|
|Push to||A list of the Publishing Environments the Content will be Pushed to.|
Push to Delete
Whenever you select Delete or Publish & Delete in the push publishing popup window, you schedule dotCMS to perform a Push to Delete on the specified Expire Date. At the specified date and time, dotCMS will unpublish and delete the pushed content from the receiving Endpoint.
- When you Push to Delete, it does not mean that the selected content will be reverted to an older version.
- Instead, on the specified date and time the content included in the push will be removed from the receiving server, and will thus no longer exist on the receiving server at all.
- Push to Delete only works on content which can be pushed normally.
- Content which can only be synchronized (Categories and Rules) can not be deleted via a push.
By default, dotCMS automatically remembers when Content was last pushed to each Environment (based on the Content modification date), and only actually pushes the content to an Environment if the Content has changed since the last Push to that Environment. This prevents redundant Content pushes and allows you to push content without worrying about causing unnecessary network traffic, even if you don't know whether the content has actually changed.
The Force Push option disregards the modification date, pushing the Content (and all it's dependencies) regardless of whether or not any of it has changed since the last Push.
- This option can be useful to ensure that all documents are synchronized between two servers.
- However it should be used sparingly, especially on large sites, as it can cause a significant increase in network traffic.
- Whenever possible, do not use this option as your default behavior (e.g. in Workflows).
Force Push and Static Publishing
- This is intentional, to ensure that the many different elements of each Page that affect the display of the Page (including the content in the page, common page elements in Containers and Templates, etc.) are automatically updated on the Static Endpoint without you needing to understand how changes to other items in the system may have changed how the page should display.
Any time dotCMS automatically creates a new bucket on the Static Endpoint, dotCMS automatically does a Force Push of the entire site to the new bucket.
- Note that this does not happen if the bucket already exists (either because you manually created it or because dotCMS previously created it at some time in the past).
- This ensures that any new buckets created (via the AWS S3 Parameters) receive all content for the site, regardless of previous pushes to other buckets on the Static Endpoint.
For more information on what information is pushed when you push any selected object, please see the Push Publishing Dependencies documentation.
Video: Push Publishing Content
Managing Push Publishing
The following sections provide an overview of managing push publishing of Content. For more information, please see the Push Publishing documentation.
The Publishing Queue
When you Push Publish Content, it is added to the Publishing Queue. You may view the Publishing Queue to see what Content is scheduled to be pushed (including items which were scheduled to be pushed immediately, but have not yet been sent).
Content Push History
To view the push history of a Content item, edit the Content, select the History tab, and scroll to the bottom of the screen.
To remove the push history for the Content, click the Delete Push History in the Push History section of the History tab.
System Push History
To delete the push history of all Content on the entire system, select System -> Maintenance and click the Tools tab. The Delete Pushed Assets History tool removes all pushed assets from the history table; this both cleans up old push history and ensures that all asset dependencies will be included in every push, regardless of when Content was last pushed to the receiving server.