After you import content into a subscriber, it continues to receive updates from the publisher. Content Hub administrators and content editors might prefer to keep content changes made on the subscriber. Unsubscribing content from Content Hub syndication keeps local changes intact and prevents future updates to the content on a subscriber.

To manually unsubscribe entities from syndication, you can follow one of these:

Using Publisher’s Dashboard

• Navigate to the Publisher’s Dashboard and click Content.

• On the Content page, find the entity you want to unsubscribe.

• Click View Syndication Details for the specific entity.

  

  Content Hub displays a modal. The subscription status for each subscriber is listed as a toggle switch.

• Locate the subscriber from where you want to unsubscribe the entity and then disable its SUBSCRIBED status.

  

When you unsubscribe an entity from a subscriber, any future changes made to that entity by the publisher do not import to that subscriber. Additionally, Content Hub preserves any local changes made to the entity on the subscriber’s side.

Using Drush

You can use the following Drush commands to manage entity subscriptions on subscribers:

Using the acquia_contenthub_unsubscribe module (deprecated)

The Content Hub unsubscribe module is a low-level, experimental interface for developers to programmatically unsubscribe entities from further updates. This module is intended for advanced users who have unique requirements that are beyond the existing features.

After you import an entity for the first time, you can disable further updates to that entity by setting the entity status to auto_update_disabled in the import tracking table.

After you disable updates to that entity:

• On entity update:

  When you import the entity subsequently, the subscriber checks the entity status. If the status is set to auto_update_disabled, the entity is excluded from subsequent updates.

• On entity delete:

  If you delete an entity from a publisher, Content Hub deletes the entity from the tracking table on webhook landing. However, the actual Drupal entity remains intact.

Unsubscribing entities from syndication