- Issue created by @danflanagan8
- Status changed to Needs review
5 months ago 12:04pm 24 July 2024 - 🇮🇳India Rajan Kumar@2026
Hii @danflanagan8
I have fixed the "Acquia DAM Asset Importer needs D11-compatible" in the patch I created. I have also attached a screenshot for reference. Please review it promptly. Thank you.
- Status changed to Active
5 months ago 1:16pm 24 July 2024 - 🇺🇸United States danflanagan8 St. Louis, US
That's a useless patch because the entire difficulty here comes from the dependency. Setting back to active.
- Status changed to Needs review
4 months ago 1:35pm 13 August 2024 - 🇺🇸United States danflanagan8 St. Louis, US
Good news! The dependency now has a D11-compatible release: https://www.drupal.org/project/media_acquiadam/releases/2.0.13 →
That means we can do a D11-compatible release of our own.
I made an MR that fixe the one deprecation (watchdog_exception) and correctly updates all the version requirements.
Oh, but that composer build is failing because media_acquiadam has a dependency on fallback_formatter, which itself does not have a D11 release. D'oh!
📌 Automated Drupal 11 compatibility fixes for fallback_formatter Needs review
- 🇮🇳India rajeshreeputra Pune
@danflanagan8, fallback_formatter is now released with D11 support.
Please proceed with the CI re-run, merge and release.
Thanks! - 🇺🇸United States danflanagan8 St. Louis, US
Thanks for the heads-up, @rajeshreeputra!
I'll merge this and tag a new release. Cheers!
-
danflanagan8 →
committed 1d3c2b5f on 2.0.x
Issue #3460247 by danflanagan8, rajeshreeputra: Acquia DAM Asset...
-
danflanagan8 →
committed 1d3c2b5f on 2.0.x
- 🇺🇸United States danflanagan8 St. Louis, US
Tagged a new release
https://www.drupal.org/project/acquiadam_asset_import/releases/2.0.0-beta2 →
Automatically closed - issue fixed for 2 weeks with no activity.