Known issues¶

Cloning a database or staging a website causes content syndication failures

Acquia discourages cloning a database or staging a website. However, customers can do this by following the instructions in Staging down syndication websites.

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 cannot be shared between Drupal 7 and Drupal 8 websites.

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 cannot 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.

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.

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

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.

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.

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.

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. For more information, see Using config split with Content Hub.

Workaround: Update config split to include the missing configuration to match the new data model required for the syndicated entities. For more information, see drupal.org issue.

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

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. For more information, see this drupal.org issue.

The discovery page does not have a select-all option

You must select one item of content at a time.

Webhook registration sometimes fails when saving

Workaround: If this occurs, retry and it should eventually save.

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

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 cannot 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.

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.

Content Moderation and auto publishing conflicts

Content Moderation module users may experience issues with auto publishing in Content Hub. For more information, see Saving filters and publish settings.

Issue with filters while syndicating Views

Before the View is imported, the content must be at the receiving site and the entities referenced in the View filter must not have any dependency calculation. Currently, you cannot create filters for configuration entities.

Workarounds:

• Create a filter for source, date, or any other generic criteria that includes the configuration entity.

• Enqueue the entity on the publisher through the ach-rq export Drush command by specifying the entity UUID or the entity ID and entity type.

For more information, Swapping the entity ID and the entity UUID during import and export.

Cloning a database or staging a website causes content syndication failures

Acquia discourages cloning a database or staging a website. However, customers can do this by following the instructions in Staging down syndication websites.

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. For more information, see Using config split with Content Hub.

Workaround: Update config split to include the missing configuration to match the new data model required for the syndicated entities. For more information, see drupal.org issue.

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. For more information, see this drupal.org issue.

Websites using Content Hub must be fully HTTP or HTTPS

Mixed-mode websites will experience difficulties when using any version of Content Hub.

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.