Known Issues in Acquia Lift

This page describes known issues for Acquia Lift. For a listing of known issues for each component of Acquia Lift, select from the following list:

Applicable client versions for issues can be identified using the icons in the following table:

Icon Client
Applies to Drupal 8 client Applies to the Drupal 8
Applies to Drupal 7 client Applies to the Drupal 7

Known issues in Content Hub

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

  • Applies to Drupal 7 client Applies to Drupal 8 client 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.

  • Applies to Drupal 8 client Content Hub client for Drupal 8 requires Drupal 8.2 or greater

    The Content Hub client for Drupal 8 requires Drupal 8.2 or greater, and is not compatible with previous Drupal versions. If you are upgrading a Content Hub client on a website that uses Drupal 8.1 or lower, be sure to first upgrade your Drupal website to version 8.2 before upgrading Content Hub.

  • Applies to Drupal 8 client The discovery page does not currently have a select-all option
    You must select one item of content at a time.
  • Applies to Drupal 8 client 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.
  • Applies to Drupal 8 client Webhook registration sometimes fails when saving

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

  • Applies to Drupal 8 client Websites using Content Hub must be fully HTTP or HTTPS
    Mixed-mode websites will experience difficulties when using any version of Content Hub.
  • Applies to Drupal 8 client Acquia Cloud Site Factory customers who clone content may encounter problems when attempting to publish the cloned content to Acquia Lift
  • Applies to Drupal 7 client Applies to Drupal 8 client 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 whitelist 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/*
  • Applies to Drupal 7 client Applies to Drupal 8 client Autosynchronization 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 currently
    a known issue where a host can not be translated unless it has at least
    one other field that is translatable, 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.

  • Applies to Drupal 7 client Issue when editing filters for websites with large numbers of tags

    If you have a very large number of tags (800 or more), the filter controls may stop working when you save a filter.
    Workaround: Reload the content discovery page.

  • Applies to Drupal 7 client Applies to Drupal 8 client Error when editing Views filters

    When you edit a saved filter in the 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 greater. 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.

  • Applies to Drupal 7 client Applies to Drupal 8 client Valid webhooks fail to register

    If the server that is 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.

Known issues in Experience Builder

At this time, no known issues with Experience Builder are available for reporting. If you encounter any difficulties with your Experience Builder subscription, contact Acquia Support for assistance.

Known issues in Profile Manager

At this time, no known issues with Profile Manager are available for reporting. If you encounter any difficulties with your Experience Builder subscription, contact Acquia Support for assistance.

Contact supportStill need assistance? Contact Acquia Support