Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
This release introduces Content Hub Pull Syndication Mode, a significant enhancement to Acquia Content Hub that enhances security and compliance needs of our customers. Traditionally, the push-based syndication model required subscriber sites to be publicly accessible for receiving webhooks, which could pose challenges in private environments. With the new Pull Syndication Mode, subscribers can now actively request and pull content updates from Content Hub, removing the dependency on inbound webhooks and public endpoints.
Acquia Content Hub, version 3.6.0, is now compatible with Drupal 11
Improvement in Webhook API
Until now, CH dispatched individual entities through a single webhook, leading to a high volume of outgoing API requests. We have revamped the implementation to embrace a new-format webhook capable of batching up multiple entities in a single dispatch. This substantial increase in the payload capacity markedly diminishes the total number of webhook calls, thereby significantly enhancing the efficiency and speed of the import process.
New feature: Manual Export Mode
This feature provides capability for a publisher to have two export modes: automatic or manual. Automatic would be the current behaviour, and manual would require a manual action (via UI View) to add the entity to the export queue. Acquia ContentHub Export Tracker view is available under /admin/content/ach_export_tracker.
Allows publisher sites to control whether they want to syndicate config dependencies or not. If this checkbox is enabled (under Exclude from export queue form), then config entities won’t be syndicated and will be excluded from the dependencies of content entities. This makes sure no config entity reaches the CH service.
Once content has been imported into a subscriber, it continues to receive updates from the publisher. However, Content Hub administrators and content editors may prefer to keep changes to that content that were made on the subscriber. Unsubscribing the content from Content Hub syndication will keep the local changes intact and prevent all future updates to that entity on a subscriber. The action is available on both Interest List view and by clicking on Content > kebab menu > View Syndication Details.