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.
Note
The Content Hub unsubscribe
module is deprecated in Content Hub 3.3.0. Acquia recommends you to uninstall
this module and update custom integrations to leverage the unsubscribe functionality
available in Content Hub versions 3.3.0 and later.
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.