Content Hub

Known issues


Content Hub 2.x will reach end-of-life on December 31, 2024. Acquia recommends that you update your Content Hub version to Content Hub 3.x by using the composer require instructions available on the acquia_contenthub project page.

Sites must be fully HTTP or HTTPS

Mixed-mode sites experience difficulties while using Content Hub.

Cloning a database or staging a site causes content syndication failures

Acquia discourages cloning a database or staging a site. Acquia recommends customers to follow the instructions in Staging down syndication websites.

Access control or password protection using .htaccess or Shield module causes syndication failures

Sites using Content Hub must make the /acquia-contenthub/* path publicly available. The Content Hub service must be able to make HTTPS requests to publishers and subscribers, and subscribers must be able to occasionally make HTTPS requests to publishers. To prevent issues, Acquia recommends that you allowlist the /acquia-contenthub/* path in your configuration of . htaccess or Shield module.

Highly dependent entities can cause massive exports

For any entity change that needs to be exported, Content Hub attempts to build a dependency tree that includes all dependencies. Depending on the site architecture, this may result in some changes enqueuing most of the entities on a publisher (for example, due to authorship or taxonomy terms).

Workaround: Write custom modules to exclude certain relationships from dependency calculation.

Limited compatibility with file storage modules

Content Hub has limited compatibility with file storage modules. There is an experimental module distributed with Content Hub, acquia_contenthub_s3, that serves as a bridge between the S3FS module and Content Hub.

Config split causes configuration changes with Content Hub 8.x-2.x

When syndicating content from the publisher website to the subscriber website using config split, you may observe configuration changes on the subscribing website. For more information, see Using config split with Content Hub.

Workaround: Update the config split to include the missing configuration to match the new data model required for the syndicated entities. For more information, see issue.

Cron job log files are using too much storage

The Content Hub import or export queue cron jobs are writing log files that do not undergo the necessary rotation process. If you do not manage the growth of the log files, they rapidly fill the mnt directory.


  • Adjust the cron jobs to cease logging if logs are not regularly reviewed or used for debugging.
  • Implement a new daily or weekly cron job executing a script to systematically rotate log files.

For more information, see Guidelines on log rotation for customer-owned logs.

Large increase in Purge module queue when importing content with Content Hub

When you use the purge_processor_lateruntime module during Content Hub imports, the purge queue might increase substantially.

Workaround: Disable the purge_processor_lateruntime module.

Issue with filters while syndicating Views

Before the View is imported, the content must be at the receiving site and the entities referenced in the View filter must not have any dependency calculation. Currently, you cannot create filters for configuration entities.


  • Create a filter for source, date, or any other generic criteria that includes the configuration entity.
  • Enqueue the entity on the publisher through the ach-rq export Drush command by specifying the entity UUID, or the entity ID and entity type.

For more information, see Swapping the entity ID and the entity UUID during import and export.

Undesired translations appearing on the site even when acquia_contenthub_translations is enabled

When there are no more translations to fall back to in case of a syndicating content, the language has to be imported.

Workaround: To avoid any unexpected language imports, Acquia recommends you to use a default language throughout the subscription. For example, English.


The acquia_contenthub_translations was introduced in Content Hub 8.x-2.36.

Metatag module does not export from URL with trailing slash

When using the Metatag module, Content Hub may not export content if you include a trailing slash when using the -l or --uri parameter with Drush.

Correct usage: drush -l queue-run acquia_contenthub_export_queue

Incorrect usage: drush -l queue-run acquia_contenthub_export_queue