Webhooks that are not publicly accessible are shown as disabled on the Connected Sites page in Publisher’s Dashboard. For example, a website that uses Shield module or Tethered Arrow.
When you exclude the uid and revision_uid fields from syndication through the UI and enable Disable User Syndication, imported nodes on the subscriber site do not have proxy_user as the author. Instead, the author is assigned as Anonymous if the import runs through cron, or as current_user if executed through the UI.
Workaround: Implement custom code during the import process on the subscriber side to update the author. Use AccountSwitcher::switchTo to change to the necessary required_author or proxy_user (recommended), and reverse with AccountSwitcher::switchBack.
For implementation details, refer to the following patch:
On a publisher site containing text, media and other paragraph types, you can add English translations for Japanese content. However, this addition causes an error during the manual import process on subscriber sites.
Workaround: Enable the Show language selector on create and edit pages checkbox in the From library section. Acquia recommends you to use the drush cdel acquia_contenthub_translations.settings nt_entity_registry.unspecified.paragraph:from_library command to remove 'paragraph:from_library': unspecified from acquia_contenthub_translations.
Content Hub uses the DepCalc module to calculate dependencies for entities. Memcached can cause performance issues with DepCalc.
Workaround: Acquia recommends you to use the database cache instead:
$settings['cache']['bins']['depcalc'] = 'cache.backend.database';
For more information, visit Memcached and Acquia hosting.
Webhooks with interest lists exceeding 65536 items result in an error message in Publisher’s Dashboard on the client details page of connected sites. Depending on the available PHP memory, such webhooks may result in out-of-memory errors when retrieved through the ach-wh-list Drush command.
Mixed-mode sites experience difficulties while using Content Hub.
Acquia discourages cloning a database or staging a site. Acquia recommends customers to follow the instructions in Staging down syndication websites.
Sites using Content Hub must make the /acquia-contenthub/* path publicly available. The Content Hub service must be able to make HTTPS requests to publishers and subscribers, and subscribers must be able to occasionally make HTTPS requests to publishers. To prevent issues, Acquia recommends that you allowlist the /acquia-contenthub/* path in your configuration of . htaccess or Shield module.
For any entity change that needs to be exported, Content Hub attempts to build a dependency tree that includes all dependencies. Depending on the site architecture, this may result in some changes enqueuing most of the entities on a publisher (for example, due to authorship or taxonomy terms).
Workaround: Write custom modules to exclude certain relationships from dependency calculation.
Content Hub has limited compatibility with file storage modules. There is an experimental module distributed with Content Hub, acquia_contenthub_s3, that serves as a bridge between the S3FS module and Content Hub.
The Content Hub import or export queue cron jobs are writing log files that do not undergo the necessary rotation process. If you do not manage the growth of the log files, they rapidly fill the mnt directory.
Workarounds:
For more information, see Guidelines on log rotation for customer-owned logs.
When you use the purge_processor_lateruntime module during Content Hub imports, the purge queue might increase substantially.
Workaround: Disable the purge_processor_lateruntime module.
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:
Content Hubach-rq export Drush command by specifying the entity UUID, or the entity ID and entity type.For more information, see Swapping the entity ID and the entity UUID during import and export.
When there are no more translations to fall back to in case of a syndicating content, the language has to be imported.
Workaround: To avoid any unexpected language imports, Acquia recommends you to use a default language throughout the subscription. For example, English.
The acquia_contenthub_translations was introduced in Content Hub 8.x-2.36.
When using the Metatag module, Content Hub may not export content if you include a trailing slash when using the -l or --uri 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
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Webhooks that are not publicly accessible are shown as disabled on the Connected Sites page in Publisher’s Dashboard. For example, a website that uses Shield module or Tethered Arrow.
When you exclude the uid and revision_uid fields from syndication through the UI and enable Disable User Syndication, imported nodes on the subscriber site do not have proxy_user as the author. Instead, the author is assigned as Anonymous if the import runs through cron, or as current_user if executed through the UI.
Workaround: Implement custom code during the import process on the subscriber side to update the author. Use AccountSwitcher::switchTo to change to the necessary required_author or proxy_user (recommended), and reverse with AccountSwitcher::switchBack.
For implementation details, refer to the following patch:
On a publisher site containing text, media and other paragraph types, you can add English translations for Japanese content. However, this addition causes an error during the manual import process on subscriber sites.
Workaround: Enable the Show language selector on create and edit pages checkbox in the From library section. Acquia recommends you to use the drush cdel acquia_contenthub_translations.settings nt_entity_registry.unspecified.paragraph:from_library command to remove 'paragraph:from_library': unspecified from acquia_contenthub_translations.
Content Hub uses the DepCalc module to calculate dependencies for entities. Memcached can cause performance issues with DepCalc.
Workaround: Acquia recommends you to use the database cache instead:
$settings['cache']['bins']['depcalc'] = 'cache.backend.database';
For more information, visit Memcached and Acquia hosting.
Webhooks with interest lists exceeding 65536 items result in an error message in Publisher’s Dashboard on the client details page of connected sites. Depending on the available PHP memory, such webhooks may result in out-of-memory errors when retrieved through the ach-wh-list Drush command.
Mixed-mode sites experience difficulties while using Content Hub.
Acquia discourages cloning a database or staging a site. Acquia recommends customers to follow the instructions in Staging down syndication websites.
Sites using Content Hub must make the /acquia-contenthub/* path publicly available. The Content Hub service must be able to make HTTPS requests to publishers and subscribers, and subscribers must be able to occasionally make HTTPS requests to publishers. To prevent issues, Acquia recommends that you allowlist the /acquia-contenthub/* path in your configuration of . htaccess or Shield module.
For any entity change that needs to be exported, Content Hub attempts to build a dependency tree that includes all dependencies. Depending on the site architecture, this may result in some changes enqueuing most of the entities on a publisher (for example, due to authorship or taxonomy terms).
Workaround: Write custom modules to exclude certain relationships from dependency calculation.
Content Hub has limited compatibility with file storage modules. There is an experimental module distributed with Content Hub, acquia_contenthub_s3, that serves as a bridge between the S3FS module and Content Hub.
The Content Hub import or export queue cron jobs are writing log files that do not undergo the necessary rotation process. If you do not manage the growth of the log files, they rapidly fill the mnt directory.
Workarounds:
For more information, see Guidelines on log rotation for customer-owned logs.
When you use the purge_processor_lateruntime module during Content Hub imports, the purge queue might increase substantially.
Workaround: Disable the purge_processor_lateruntime module.
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:
ach-rq export Drush command by specifying the entity UUID, or the entity ID and entity type.For more information, see Swapping the entity ID and the entity UUID during import and export.
When there are no more translations to fall back to in case of a syndicating content, the language has to be imported.
Workaround: To avoid any unexpected language imports, Acquia recommends you to use a default language throughout the subscription. For example, English.
The acquia_contenthub_translations was introduced in Content Hub 8.x-2.36.
When using the Metatag module, Content Hub may not export content if you include a trailing slash when using the -l or --uri 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
If this content did not answer your questions, try searching or contacting our support team for further assistance.