acquia_dam 1.1.14

Contributors (3)

Rajeshreeputra, amangrover90, danflanagan8

Changelog

Issues: 14 issues resolved.

Changes since 1.1.13 (compare):

Bug

• Resolve #3584070 "Flush image style after updating focal point crop on DAM media."
• Resolve #3580543 "Fix: Imported media name initially ignores configured field mapping."
• Resolve #3577492 "Fix media update queue to download new file when version is updated."

Feature

• Resolve #3546077 "DAM authentication status in the Drupal status report."
• Resolve #3542480 "Provide decorative image option for Acquia DAM Image media type."

Support

• Resolve #3580856 "Support trailing underscores in filename."
• Resolve #3582163 "Update image media type url pattern from version_id based to external_id based."
• Resolve #3582771 "Fix: switch to v1 API for dependent metadata fields availability."
• Resolve #3588200 "Implement file changed timestamp as query param in file url for local DAM assets."
• Resolve #3588200 "Cover public and private both uri schemes."

Task

• Resolve #3584060 "Fix stream wrapper warnings."
• Resolve #3584059 "Add menu links for Metadata, Image styles, and Integration links configuration pages."
• Resolve #3583037 "Fix: Refactor Cron to use chunked asset categorization for improved performance and reliable unpublish of unavailable assets."
• Resolve #3583037 "Add test coverage for unpublish message in test."

Note:

The fix for #3583037 in version 1.1.14 applies only to assets processed after the module has been updated in your codebase. If you notice that older assets remain in the acquia_dam_media_item_update queue and fail to update, perform the following steps:

1. Empty the acquia_dam_media_item_update queue: drush queue:delete acquia_dam_media_item_update
2. Clear the state variable that tracks the last update check: drush state:set acquia_dam.last_update_check ''
3. Run cron: drush cron
4. Run the Acquia DAM media‑item update queue: drush queue:run acquia_dam_media_item_update
5. Repeat steps 3 and 4 until the queue is empty.

Once the queue stays empty after a cron run, affected older assets should be updated correctly. You only need to follow these steps if you observe assets stuck or failing in the queue after updating to 1.1.14.