Installing Content Hub

This page provides information about how to install Content Hub modules on your website for Drupal 9 or later. For information about how to install Content Hub on a Drupal 7 website, see, Installing Acquia Content Hub for Drupal 7.

To use Content Hub, you must install a group of Drupal modules on each of the websites in your content network that needs to share content with each other. This group of modules is referred to as the Content Hub client. You can use the client and can also share content with your websites by using the Content Hub API.


To use Content Hub with your website, review the technical requirements for the latest version of Content Hub modules.

Installation checklist

Use the following checklist to install Content Hub:




Obtaining your Content Hub credentials


Installing Content Hub modules


Enabling a site as Content Hub publisher or subscriber


Enabling additional modules

Obtaining your Content Hub credentials

To connect to the Content Hub content repository on Cloud Platform, you must have an API key, a secret key, and a hostname. If you do not have these credentials, contact your account manager.

Installing Content Hub modules

Before installing Content Hub, ensure that you review the known issues for Content Hub.

To install Content Hub modules on your Drupal application:

  1. Install the Content Hub project by using the instructions on the Content Hub module page.

  2. Set the cache backend for the Depcalc module to use the database.

    • If your site is hosted in Cloud Platform, use the default Memcached configuration. The default settings set the cache backend to the correct value.

    • If your site is not hosted in Cloud Platform, ensure that the settings.php file includes the following:

      settings.php: $settings['cache']['bins']['depcalc'] = 'cache.backend.database'
  3. Deploy the changes to the desired environment.

  4. Enable the Content Hub module.

    To enable the module, you can use the Drupal admin user interface or the Drush command.

Enabling a site as Content Hub publisher or subscriber

Enable either of the following modules on every site:

  • Publisher module: acquia_contenthub_publisher

  • Subscriber module: acquia_contenthub_subscriber

For more information, see Common syndication models.

Enabling additional modules

Content Hub modules can be divided into the following categories:

  • Required modules

  • Additional modules

  • Experimental or deprecated modules

Required modules

These are essential modules that must be enabled on every site:




Enables Drupal sites to connect to Content Hub. It is a requirement for all sites.


Enables sites to export content. If this module is enabled, the site exports entities to the Content Hub service.


Enables sites to import content from other sites. If this module is enabled, the site receives entity imports from Content Hub.

Additional modules

These are optional modules that must be enabled depending on the role a site needs to perform.




Provides a Discovery user interface that serves as a legacy interface for reviewing exported content and creating filters.


Provides the Content Hub Publisher’s Dashboard, which is a user interface that offers usage insights, views of data stored in the service, and logs related to the service. Acquia recommends this module for both publishers and subscribers.


Provides metatag controls and tools for Content Hub.

Experimental or deprecated modules

These are optional modules that must be enabled with caution.




Enables a subscriber to set a default moderation state to all content imported through Content Hub to that site.


Provides integration with the s3fs module.


Provides audits for known incompatibilities between Drupal and Content Hub.


Enables subscriber sites to selectively import languages associated with content entities.


Provides an interface to unsubscribe entities from Content Hub.


From Content Hub version 3.3.0, the acquia_contenthub_unsubscribe module has been deprecated in favor of the unsubscribe feature within the Publisher’s Dashboard.

Next step

Configure the Content Hub client