--- title: "Known issues" date: "2024-02-14T06:18:38+00:00" summary: "Explore known issues and workarounds for Content Hub, including user syndication, translation imports, and file storage compatibility." image: type: "page" url: "/drupal-starter-kits/add-ons/content-hub/known-issues" id: "83ad2b7c-4805-4c09-9278-9a16d08187be" --- Table of contents will be added. Publicly inaccessible webhooks are shown as disabled ---------------------------------------------------- Webhooks that are not publicly accessible are shown as disabled on the Connected Sites page in [Publisher’s Dashboard](/drupal-starter-kits/add-ons/content-hub/publishers-dashboard "Publisher’s Dashboard"). For example, a website that uses Shield module or Tethered Arrow. Excluding User Fields from syndication incompatible with Disable User syndication --------------------------------------------------------------------------------- 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: [![9fded_chs_8580.pdf preview](https://acquia.widen.net/content/kq6xhlbllb/jpeg/9fded_chs_8580.jpg)](https://acquia.widen.net/view/pdf/kq6xhlbllb/9fded_chs_8580.pdf?t.download=true) Translation import error for Japanese content --------------------------------------------- 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`. Do not use Memcached for DepCalc -------------------------------- 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](https://docs.acquia.com/acquia-cloud-platform/performance/memcached/intro). Large interest lists cannot be displayed in Publisher’s Dashboard or retrieved through Drush -------------------------------------------------------------------------------------------- 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. Sites must be fully HTTP or HTTPS --------------------------------- Mixed-mode sites experience difficulties while using Content Hub. Cloning a database or staging a site causes content syndication failures ------------------------------------------------------------------------ Acquia discourages cloning a database or staging a site. Acquia recommends customers to follow the instructions in [Staging down syndication websites](/acquia-cms/add-ons/content-hub/managing-connected-sites/staging-down). Access control or password protection using .htaccess or Shield module causes syndication failures -------------------------------------------------------------------------------------------------- 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](https://www.drupal.org/project/shield) module. Highly dependent entities can cause massive exports --------------------------------------------------- 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. Limited compatibility with file storage modules ----------------------------------------------- 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](https://www.drupal.org/project/s3fs) module and Content Hub. Cron job log files are using too much storage --------------------------------------------- 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_: * Adjust the cron jobs to cease logging if logs are not regularly reviewed or used for debugging. * Implement a new daily or weekly cron job executing a script to systematically rotate log files. For more information, see [Guidelines on log rotation for customer-owned logs](/acquia-cloud-platform/manage-apps/cron/advanced-cron#cloud-scheduled-job-output). Large increase in Purge module queue when importing content with Content Hub ---------------------------------------------------------------------------- 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. 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, see [Swapping the entity ID and the entity UUID during import and export](/acquia-cms/add-ons/content-hub/manage/developing/events#hub-swapping-entities). Undesired translations appearing on the site even when acquia\_contenthub\_translations is enabled -------------------------------------------------------------------------------------------------- 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. Note The `acquia_contenthub_translations` was introduced in Content Hub 8.x-2.36. 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` 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`