Content Sync makes it easy for your editors to see what content has been pushed or pulled, where it comes from and what sites it was distributed to. You can also filter your content list by this state to easily find and identify content.
Show usage
The Sync State column documented below will display a Show usage link once content has been pushed. Even without the Sync State column added to your site you can still use the Operations menu at each content item to access it:
Both of these links will open the Content Cloud tab of the node.
Filter by Sync State
After enabling our "views" sub module, you can add a new filter Sync State to your views.You can filter by the following sync states:
- Is pushed: Identify content that this site has pushed.
- Is pushed - Update waiting: Identify content that was pushed and that has a local update waiting to be pushed. This is only available for content using: Push Content Manually.
- Is pulled: Identify content that Content Sync has pulled from another site.
- Is overridden locally: Identify content that was pulled from another site and then explicitly customized on the current site. Overridden content is not updated to preserve the local changes so this filter can be especially useful to check compliance after important content updates.
Sync State views field
After enabling our "views" sub module, you can add a new column Sync State to your views. This column contains all relevant information about the sync state as a list of messages. It typically looks similar to this:
Besides messages, editors can view the current sync state visually as a summary that will show the current synchronization progress in real time, if it's still ongoing:
The views field uses the "sync_status" template from the submodule to render the progress and the messages.
Developers can remove or change messages here by using the hook cms_content_sync_views_sync_state_alter.
By default, one or more of the following messages are shown:
1. Local content ("not_syndicated")
Content that was neither pushed nor pulled.
2. View status ("view_status")
Specifically for nodes, a link to the "Content Cloud" tab of the node where editors can view the details of the current and previous push and pull operations for the current site and the target sites or the source site.
3. Content was pushed from this site ("pushed_on" and "pushed_triggered_on")
It will also provide you the Pool it was pushed to (Content in the example below).
Please note that the date shown here is the published date of the content. So even if you push the content later, it will still show the date of when the revision was originally saved on the site.
4. Translation deletion waiting to be pushed ("translation_deletion_requires_push")
Shown if one of the translations of this content item was deleted so editors can manually push the deletion when ready.
When you delete the default language, the whole content is deleted in Drupal so in this case Content Sync pushed the deletion immediately when you delete the content.
5. Update waiting to be pushed ("update_waiting")
This includes a quick link to push the local changes if they weren't shared yet.
6. Content was pulled into this site ("pulled_from")
This includes a deep link to the content on the source site, making it easy to identify the content and it's origin.
It will also provide you the Pool the content was pulled from in brackets.
7. Overridden locally ("overridden_locally")
See Override content locally for details about this feature.
