Content Hub

Installing Content Hub

Important

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.

This page provides information about how to install Content Hub modules on your website running the current Drupal version.

Prerequisites

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:

S.No.Task
1Obtain your Content Hub credentials
2Install Content Hub modules
3Connect to Content Hub
4Enable a site as Content Hub publisher or subscriber
5Enable additional modules

Obtaining your Content Hub credentials

Important

For each Drupal Cloud environment, you need separate Content Hub credentials. To provision additional Content Hub accounts, contact your account manager.

To connect to the Content Hub content repository on Cloud Platform, you must have the following:

  • An API key
  • A secret key
  • Content Hub service hostname for your region

If you do not have these credentials, contact your account manager.

Installing Content Hub modules

Note

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 latest release of 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, include the following in the settings.php file:

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

  4. Enable the Content Hub module.

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

Connecting to Content Hub

To register your site with the Content Hub service:

  1. In your Drupal site, log in as an administrator and navigate to Administration > Configuration.
  2. In the Web services section, click Acquia Content Hub.

  3. In the Connection Settings section of the Acquia Content Hub Settings page, enter the following required fields:

    1. Acquia Content Hub Hostname: The region-specific hostname for the Content Hub API. Acquia provides these credentials to you.
    2. API Key: The API key for your Content Hub account.
    3. Secret Key: The secret key for your Content Hub account.
    4. Client Name: The unique name for your site in Content Hub.

  4. Click Register Site.

    The system displays a status message stating that your site is connected to Content Hub.

    By default, the Connection Settings section collapses after the site is registered. You can expand it to view details such as Account ID and site origin UUID.

Enabling a site as Content Hub publisher or subscriber

After configuring the Content Hub module, enable either of the following modules on every site:

  • Publisher module: acquia_contenthub_publisher
  • Subscriber module: acquia_contenthub_subscriber

For more information about choosing whether your site must be a publisher or a subscriber, see Common syndication models.

(Optional) Enabling additional modules

The following table lists the optional modules that must be enabled depending on the role a site needs to perform:

ModuleDescription
acquia_contenthub_curationProvides a Discovery user interface that serves as a legacy interface for reviewing exported content and creating filters.
acquia_contenthub_dashboardProvides 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.
acquia_contenthub_metatagProvides metatag controls and tools for Content Hub.

The following table lists the additional optional modules that are experimental or deprecated, and must only be enabled with caution:

ModuleDescription
acquia_contenthub_moderationEnables a subscriber to set a default moderation state to all content imported through Content Hub to that site.
acquia_contenthub_s3Provides integration with the s3fs module.
acquia_contenthub_site_healthProvides audits for known incompatibilities between Drupal and Content Hub.
acquia_contenthub_translationsEnables subscriber sites to selectively import languages associated with content entities.
acquia_contenthub_unsubscribe

Provides an interface to unsubscribe entities from Content Hub.

Note

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

Next step

Configuring scheduled jobs