Content Hub
Syndicating content with Content Hub
Syndication allows you to leverage content created on one site to other sites in your fleet. The creating site is referred to as publisher and sites receiving content from the publisher are referred to as subscribers. You need to have at least one publisher and one subscriber to be able to syndicate content. You can use one publisher and many subscribers, many publishers to one subscriber, or a many to many approach.
In case you need a website to act as both a publisher and subscriber, Content Hub associates the publisher of specific content to act as the owner of that content. A subscriber cannot act as the publisher of content it does not own.
To begin syndicating content:
Content Hub0.The imported nodes may be different content types, depending on your publishing website. Content Hub syndicates entities and configuration, which means that you do not have to set up a single content type as the module creates them for you.
Syndication is based on the following cases:
acquia_contenthub_subscriber_import_tracking table).Entity deletion is usually a part of a normal syndication process. After an entity is deleted from a publisher, the event is followed by a DELETE request to Content Hub, and a notification of this change is sent to all interested subscribers.
The same rules apply during a manual deletion when completed with the drush acquia:contenthub-delete UUID command.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.