Hello Caleb,
This issue does not exist in version 1.1.x. We recommend that customers update to the latest version of 1.1.x for an improved experience and better support.
This module also works with another theme without causing UI breaks. Is there any reason to place the Gin theme condition?
Yes the fixes have been performed at MR !5 so closing this ticket.
This is working as expected. The finalized version updates in the Acquia DAM system, and the Drush command retrieves the finalized version without needing to manually click the “Check for update” button each time.
This issue should now be fixed against the 1.1.x branch instead of 1.0.x, as it is actively maintained.
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
Yes, Wim, I agree to search for issues to avoid duplication.I tried earlier, but I noticed that I might have a category filter set to (Bug/task), which is why it did not appeared.
vipin.mittal18 → created an issue.
The loop issue is addressed in https://www.drupal.org/project/acquia_optimize/issues/3525986 📌 Fix Race Conditions in AJAX Processing Active . Upgrading to version 1.2.2 resolves the problem.
Needs to be fixed
vipin.mittal18 → created an issue.
Hello @saurabhpandit26,
The issue might have been resolved in the latest 1.1.x version. Please update the module and inform us if you have any concerns.
I am able to reproduce the issue and have confirmed that the fix successfully resolves it. Refer below screenshot
vipin.mittal18 → made their first commit to this issue’s fork.
This issue is not associated with the Acquia DAM, so proceeding to close this ticket.
The issue can be reproduced by enabling the LottieFiles Field module and navigating to the page
admin/structure/types/manage/project/fields/add-field. Refer below screenshot:
vipin.mittal18 → made their first commit to this issue’s fork.
The Drupal Core does not natively support displaying an inline PDF viewer for local files.
This MR works like a charm. Thank you!
Refer attached video file
Hello Capysara,
What I understood for this ticket is that the "check for updates" option is currently only visible for Acquia DAM images and needs to be available for all media types?
Please note that this functionality has been expanded across all media types in the 1.x series due to improvements made since version 1.0. We recommend updating to the latest version.
The v2 structure format is causing issues with thumbnail generation. Therefore, we have decided to serve the thumbnail using v3 as a uniform solution.
How to migrate from Media Acquia module to Acquia DAM module?
https://community.acquia.com/acquiadam/s/article/How-to-migrate-from-Med...
No action is needed, as the Acquia DAM system team has confirmed that both versions will continue to be supported. There are differences in functionality between the two versions v1 & v2, and customers can use either version as needed.
Yes @omd, it is.
Hello Byron,
While Media Acquia DAM does not retain asset versions and external IDs, Acquia DAM does. As a result, a cron job has been scheduled to call the API, retrieve the version ID and external ID, and store them in the table.
Could you please apply the solution suggested by Chandan and confirm if there are any errors preventing you from continuing with the migration?
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
The end of life (EOL) is scheduled for February 2026. Therefore, we expect the customer to complete the migration of the site from Media:Acquia DAM → to Acquia DAM → by that time.
Solution: Please follow the steps outlined below:
- Navigate to /admin/structure/media/manage/acquia_dam_image_asset/display/media_library.
- Replace the existing field with the “Asset Reference field.” and set image style along with.
- Finally, click “Save.”
Hello Caspar,
Could you please provide the exact steps to reproduce the issue? I want to ensure I'm not missing anything, as I haven't been able to replicate the problem on my end. Thanks!
Hello Zack,
I'm not sure if any fixes are required on the module's end. Increasing the xdebug.max_nesting_level in php.ini to a higher value can help to investigate further, but this is just a temporary workaround.
Your issue might be resolved by switching PHP versions, as this could have cleared the opcode cache (like OPCache), which may fix issues caused by stale or corrupted cached data.
Yes Jakob, I’ve been able to replicate the issue. While we hadn’t considered this specific case earlier, I’m still trying to understand the real-world scenario where a customer would want to serve the same media source for both embed and download within a single application. That said, we do have the flexibility to serve different media sources for each option if needed.
Hello @ibullock, Could you please outline the exact steps to reproduce the issue?
Hello @capysara, Could you please outline the exact steps to reproduce the issue?
Hello James,
I'm not entirely sure I fully understand your point. Before responding based on assumptions, I'd appreciate a bit more clarification. It would be helpful if you could update the ticket with more details about the URLs you're navigating, along with some relevant screenshots.
Hello @bhagyalakshmi,
Currently, there is no feature that allows image type conversion during asset attachment to the content. The assets displayed in the content are shown exactly as they were uploaded to the Acquia DAM (formerly Widen) system.
I'm trying to understand the scenario where you would want to upload different image type to Widen, and you plan to serve different versions of those images on Drupal applications. Also, if you make any modifications to the image in Widen, how would that updated version be automatically converted and synced with the Drupal application? Could you please describe your use case in more detail?
I faced the same issue, but applying the patch resolved it and unblocked me from creating content.
Hello Pavlos,
The deprecation message has been removed from the Media:Acquia DAM module page.
The migration path from Media:Acquia DAM → to Acquia DAM → is already underway. A beta version has already been released 2.1.0-beta1 → , and the stable version is expected to be available by this month with improved migration dashboard experience. Most of the issues and challenges that customers face with Media: Acquia DAM have already been resolved in the Acquia DAM module. Instead of maintaining two separate modules, our goal is to focus on a single module that offers a broader range of integration options for customers.
There is no specific timeline for Media: Acquia DAM customers to migrate; however, once the migration path is established, we recommend migrating as soon as possible. This will allow customers to take advantage of the enhancements and bug/security fixes available in the Acquia DAM module.
It is possibility that no additional fixes will be made for the issues related to Media: Acquia DAM that have already been resolved in the Acquia DAM module.
That's good to hear and will help me release it as soon as possible.
Sure @zoeblair, I will be releasing soon as validating some other changes too. In the meantime, you can run at https://www.drupal.org/project/user_redirect/releases/2.0.x-dev →
Hello @tostinni,
Could you please confirm if you are able to replicate the issue from https://www.drupal.org/project/user_redirect/releases/2.0.x-dev → as I am planning to have another release with Drupal 11 compatible.
Hello vbalsys, What I meant to say is that this module is not designed to log into the Drupal system and then redirect to an external site. However, I’d be happy to implement this feature if any customers are interested in it. Any code for this would also be appreciated.
Hello @ishan.gupta,
I'm trying to understand the scenario where you'd want to serve same asset from the same media source in two different media types for both the embed and download options.
Hello Ishan,
The expected behavior is that assets will be served from the Drupal file system when both media types, "Download & sync assets," are checked. To serve assets from an embedded URL, ensure that the "Download & sync assets" option is unchecked.
I applied the patch, but the issue still persists.
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
vipin.mittal18 → created an issue.
vipin.mittal18 → changed the visibility of the branch 1.0.x to hidden.
vipin.mittal18 → changed the visibility of the branch 1.1.x to hidden.
vipin.mittal18 → created an issue.
vipin.mittal18 → made their first commit to this issue’s fork.
vipin.mittal18 → created an issue.
At present, when a ZIP file is uploaded to the Widen Digital Asset Management (DAM) system, it does not appear in the Drupal application. This is because the compressed_archive format_type is not yet supported by the module.