- ππΊHungary Balu Ertl Budapest πͺπΊ
Just stumbled upon into a slightly different but still very related issue:
media_acquiadam
does not always takes into consideration the Finalized version of a given asset but sometimes (for some yet unknown reasons) only a previous asset version is being referenced from the Drupal side. This malfunction (for me at least) seems very similar to the one being solved in π Look for the "finalized" asset version not the latest modified Needs review for the more modernishacquia_dam
module.I would recommend to expand the scope of this ticket and inspect asset version handling logic of this module from a more general approach. That could probably solve multiple issues in one run.
- Status changed to Closed: won't fix
2 months ago 8:22pm 30 October 2024 - πΊπΈUnited States japerry KVUO
Closing this as the change will be fixed the upcoming 1.1 release of acquia_dam, which will encourage existing media_acquiadam customers to migrate to.