Content Hub

FAQs and troubleshooting


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.

There may be instances when you find that Content Hub is not working as expected. In these cases, you must troubleshoot your installation.

Content Hub diagnostic module

The Content Hub diagnostic module, when enabled, provides you with information that ensures your installation has the proper basic configuration.

The Content Hub diagnostic module is included in the normal installation. After the module is enabled, a new section will display in Reports > Status report.

If this report section is green, your Content Hub installation is configured correctly. If there are potential issues with your installation, this report section will provide the corrections that must be made to ensure successful product use, and can include module updates or patches.

Content Hub history logs

Content Hub tracks information about the service by using the history API endpoint. This information can help you troubleshoot issues, and you can review the history logs for Content Hub. For more information, see Using the Content Hub API.

Composer and Drupal 7

We do not recommend using Composer to download Drupal 7 modules. Downloading the tarball for Drupal 7 modules is the recommended method.

Fatal error when installing Composer dependencies with Drush

Composer Manager depends on the Composer Drush extension to install the Composer tool.

Possible cause: Outdated Composer

If you run drush composer-manager commands and see errors like the following, try updating your Composer Drush extension.

Could not load package...
Could not parse version constraint...

To resolve this issue, delete the current version of the Composer Drush extension and reinstall it by running the following commands ( 8.x is the correct version):

rm -Rf ~/.drush/composer
drush dl composer-8.x

Then run the following command inside of your Drupal installation:

drush composer-manager install

AJAX errors with Views exposed filters

Views exposed filters may cause AJAX errors. Remedy this by either installing the latest -dev release of the Views module or by using this patch.

Local development

If you are working with a local Content Hub website and are experiencing difficulties, see the best practices page.