Known issues in Content Hub¶

This page describes known issues for Acquia Content Hub.

Use the following icons to identify the applicable client versions for issues:

• D9: Applies to Drupal 9
• : Applies to Drupal 8
• : Applies to Drupal 7

See also the list of supported and unsupported modules for Content Hub.

• Issue while syndicating a new translation of an already syndicated entity
  

  While syndicating a new translation of an already syndicated entity in Content Hub 1.x, the published state of the new translation entity on the subscribing site may be unpublished.

  Workaround: Syndicate all translations simultaneously from the publishing website or update the newly syndicated translations manually on the subscribing website.

• Cloning a database or staging a website causes content syndication failures
  When you clone a database or stage a website, the UUIDs of the entities don’t change. The entities and other data are tracked in the tracking table with those UUIDs. Other settings are duplicated which may cause syndication issues in either the old or the newly cloned or staged website. Acquia doesn’t recommend cloning databases with Acquia Content Hub syndication data or staging websites in Cloud Platform or Site Factory.

• Drupal 8.8 or later is not compatible with Acquia Content Hub 8.x-1.44 or earlier
  Starting with Drupal 8.8, the method to handle URL path aliases is handled by a new entity. This change includes dropping the url_alias table and adding the path_alias table.

  The Acquia Content Hub 8.x-1.45 client for Drupal 8 (download) supports Drupal 8.8. Upgrade your Acquia Content Hub modules first, then upgrade Drupal core.

• D9 Acquia Content Hub compatibility with file storage modules
  

  • Acquia Content Hub is compatible with the S3FS module in version 8.x-2.9 and greater. Content Hub 2.x supports only s3 external file systems using the S3FS module.
  • Content Hub 1.x doesn’t support external file systems in Drupal 8 or Drupal 7.

• D9 Config split causes configuration changes with Acquia Content Hub 8.x-2.x
  When syndicating content from the publisher to subscriber website using config split, you may observe configuration changes on the subscribing website. See Using config split with Content Hub for more information.

  Workaround: Update config split to include the missing configuration to match the new data model required for the syndicated entities. See the drupal.org issue for details.

• Content Moderation module is incompatible with older versions of Acquia Content Hub 1.x
  When syndicating content from the publisher to subscriber website, some content remains unpublished on the subscriber website.

  Workaround: Upgrade to the most recent version of the Acquia Content Hub 1.x module.

• Drupal 8.6 requires Acquia Content Hub 8.x-1.30 or later

• Content Hub client for Drupal 8 requires Drupal 8.4 or later
  The Content Hub client for Drupal 8 requires Drupal 8.4 or later, and isn’t compatible with previous Drupal versions.

• Downgrading from Acquia Content Hub 8.x-2.x to 8.x-1.x
  If you have upgraded to Acquia Content Hub 2.x, and then downgrade to 1.x, you may receive an error message when attempting to use Drush like error Class \Drupal\acquia_contenthub\Commands\AcquiaContenthubCommands does not exist. See this drupal.org issue for details.

• No operability between Drupal 7 and Drupal 8 websites
  

  • All websites in a Content Hub installation must be on the same major version of Drupal.
    
  • Content can’t be shared between Drupal 7 and Drupal 8 websites.

• The discovery page doesn’t have a select-all option
  You must select one item of content at a time.

• Administrative users must ensure that they do not override the REST configuration entity types created by Content Hub
  Overriding these entities can remove saved Content Hub filters.

• Webhook registration sometimes fails when saving
  Workaround: If this occurs, retry and it should eventually save.

• Websites using Content Hub must be fully HTTP or HTTPS
  Mixed-mode websites will experience difficulties when using any version of Content Hub.

• Site Factory subscribers who clone content may encounter problems when attempting to publish the cloned content to Personalization
  

• Password protection using .htaccess
  Websites using Content Hub in development or staging environments that protect those environments using .htaccess password protection may have difficulties synchronizing content. To prevent issues, Acquia recommends that you allowlist both your webhook URL and the path. The path is based on your installed version of Drupal:

  • Drupal 8: /acquia-contenthub/*
  • Drupal 7: content-hub/*

  For information about using Content Hub with the Shield module, see Modules to use with Content Hub.

• Auto synchronization fails when entities in field collections have translations
  Synchronization of content does not work properly when Field collections are enabled on publisher and subscriber Content Hub websites, and where Entity translations are only in use on the publisher website. Field collections are not translatable in all use cases.

  The common use case is to leave the field collection field untranslatable and set the necessary fields inside it to translatable. There is a known issue where a host can’t be translated unless it has at least one other translatable field, even if some fields inside one of its field collections are translatable.

  Workaround: Errors are partially handled in Content Hub release 1.11.0, and Content Hub indicates in the user interface that this configuration is not supported. Users may continue to experience problems when using translation and Field collections.

• Issue when editing filters for websites with large numbers of tags
  If you have a large number of tags (800 or more), the filter controls may stop working when you save a filter.

  Workaround: Reload the content discovery page.

• Error when editing Views filters
  When you edit a saved filter in Content Hub, the filter controls may stop working. You may receive AJAX errors when using exposed filters.

  Workaround: Upgrade the Views module to 7.x-3.13 or later. If you must continue to use Views version 7.x-3.11 with your website, apply the patch described in issue 1809958 on drupal.org.

• Valid webhooks fail to register
  If the server hosting the publishing or subscribing website is not keeping correct time, webhook registration can fail with the following error message: There was a problem trying to register Webhook URL [URL]. Error Code = 4005: The provided URL did not respond with a valid authorization.

• 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 parameter with Drush.

  • Correct usage

    drush -l http://example.org queue-run acquia_contenthub_export_queue

  • Incorrect usage

    drush -l http://example.org/ queue-run acquia_contenthub_export_queue

• Content Moderation and auto publishing conflicts
  Lightning and Content Moderation module users may experience issues with auto publishing in Content Hub. See Saving filters and publish settings.

• Book module incompatible with Content Hub 7.x
  The Book module is incompatible with Content Hub 7.x.

  Workaround: Disable the Book module to use Acquia Personalization with Drupal 7.x.