Content Hub
Installing Content Hub
| 4 | Enable a site as Content Hub publisher or subscriber |
| 5 | Enable additional modules |
To connect to the Content Hub content repository on Cloud Platform, you must have the following:
If you do not have these credentials, contact your account manager.
To install Content Hub modules on your Drupal application:
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:
Content Hubsettings.php: $settings['cache']['bins']['depcalc'] = 'cache.backend.database'Enable the Content Hub module.
To enable the module, you can use the Drupal admin user interface or the Drush command.
To register your site with the Content Hub service:
In the Connection Settings section of the Acquia Content Hub Settings page, enter the following required fields:
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.
After configuring the Content Hub module, enable either of the following modules on every site:
acquia_contenthub_publisheracquia_contenthub_subscriberFor more information about choosing whether your site must be a publisher or a subscriber, see Common syndication models.
The following table lists the optional modules that must be enabled depending on the role a site needs to perform:
| Module | Description |
|---|---|
acquia_contenthub_curation | Provides a Discovery user interface that serves as a legacy interface for reviewing exported content and creating filters. |
acquia_contenthub_dashboard | 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. |
acquia_contenthub_metatag | Provides 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:
| Module | Description |
|---|---|
acquia_contenthub_moderation | Enables a subscriber to set a default moderation state to all content imported through Content Hub to that site. |
acquia_contenthub_s3 | Provides integration with the s3fs module.
|
acquia_contenthub_site_health | Provides audits for known incompatibilities between Drupal and Content Hub. |
acquia_contenthub_translations | Enables 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 |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
| Provides audits for known incompatibilities between Drupal and Content Hub. |
acquia_contenthub_translations | Enables 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 |
If this content did not answer your questions, try searching or contacting our support team for further assistance.