Known issues¶

Important

EOL notice! Drupal 8 reached end-of-life on November 2, 2021. Therefore, Acquia will not be performing any testing related to Drupal 8 to ensure compatibility. Acquia recommends upgrading to Drupal 9 or later. For more information, see Frequently Asked Questions.

If you encounter any difficulties with your Acquia DAM Classic subscription, contact Acquia Support for help.

Acquia DAM Classic issues ¶

Authentication issue with the Google Chrome browser using Acquia DAM Classic login credentials ¶

The changes made by Google Chrome are impacting DAM Classic users from authenticating to access files through the Drupal entity browser.

To use the Embedded Media browser for automatic authentication to DAM, you must use https on your site. However, in certain cases such as Acquia DAM Classic SSO customers, you must disable the Embedded Media browser and authenticate outside the modal.

To disable this functionality:

Go to the DAM configuration page: /admin/config/media/acquiadam.
In Acquia DAM Classic Entity Browser settings, select the Disable SameSite Cookie Bypass checkbox.

Workaround: Instead of directly selecting the Embedded Media browser, authenticate through the user profile page link. If your site uses http or disables SameSite cookie policies, you are redirected to your user page. After you’re authenticated, you can access the Embedded Media browser. The authentication issue does not occur with Firefox.

The authentication works correctly with Chrome 87.0.4280.88 (official version) (x86_64), but not with Chrome 90.0.4430.93 (official version) (x86_64).

Users can’t download Acquia DAM Classic assets using direct download links ¶

For security reasons, email downloads are only for non-Acquia DAM Classic users. Acquia DAM Classic requires an active Brand Portal for download links to work. When sharing, the link must direct to the Brand Portal for these users to access the asset. If the account doesn’t have a Brand Portal, the link directs to a landing page, which will direct users to register and sign in.

Workaround: Create a brand portal. Published assets or registered users are not required in this brand portal, which provides a landing page for links emailed to non-Acquia DAM Classic users.

Acquia DAM Classic Connector for Drupal 8 issues ¶

Syncing a large asset into Drupal may time out after 30 seconds ¶

If you experience difficulty syncing large files from Acquia DAM Classic into your Drupal 8 website, you can increase the HTTP timeout by editing the settings.php and then changing the following configuration option to a value greater than 30:

$settings['http_client_config']['timeout'] = 30;
// timeout in seconds

For information about making changes to settings.php values in Site Factory, see Altering values in settings.php with hooks.

Expired and deleted assets aren’t removed from Drupal ¶

When you delete or set an asset to expire on a particular date, the asset will continue to persist in your Drupal website.

The Replace asset file option doesn’t sync file back to Drupal ¶

The Acquia DAM Classic Drupal module checks if a new version of the asset was uploaded before downloading the new asset to avoid unnecessary downloads. This causes the Replace asset file option not to sync the asset file back to Drupal as the version number remains unchanged. Acquia recommends using the Upload new version option instead.

Acquia DAM Classic Drupal integration doesn’t support SSO ¶

The Acquia DAM Classic Drupal integration doesn’t support single sign-on (SSO) with Acquia DAM Classic. Drupal content authors wanting to add assets from Acquia DAM Classic to Drupal must have local Acquia DAM Classic accounts.

Double-clicking folders causes a display error ¶

When navigating the Acquia DAM Classic media browser user interface in your Drupal administrative interface, single-click folders to view their contents. Double-clicking folders displays a system error.

Uploading large files can cause memory issues ¶

Subscribers uploading large files (about 800 MB or greater) in Drupal with the Acquia DAM Classic Drupal integration may receive out-of-memory errors for various reasons, such as:

The size of the subscription’s Cloud Platform server instance
Amount of physical memory (RAM) available
Amount of file system space available

If you receive out-of-memory errors when copying large files from Acquia DAM Classic to Drupal, contact your Account Manager about a server upsize.

Disk space issues when using both Acquia Content Hub and Acquia DAM Classic ¶

If you have image resources stored in Acquia DAM Classic which are then served by Acquia Content Hub, frequent file revisions in Acquia DAM Classic may cause excessive disk storage use.

The account used to create the Acquia DAM Classic account must have admin permission ¶

Acquia DAM Classic requires an account with administrative permissions during setup. Acquia DAM Classic assets are unavailable if this account is removed or loses its administrative permissions.

Revisionable DAM Classic Media entities referencing wrong files prior to version 8.x-1.40 ¶

If you see the wrong file on revisionable Media entities synced from Acquia DAM Classic and have used the module with versions prior to 8.x-1.40, update the media_acquiadam module to the latest version and contact your TAM or Acquia Support to have the issue fixed.