I'm not sure what to say about reproducing the issue other than; update the module from 3.2.0 to 3.2.1 and run the Drupal status report Status Report /admin/reports/status.
Our local dev environments run mysql 5.7 and php 8.2.15. Our remote test environments run mysql 5.7.4 and php 8.2. Drupal is 10.3.2.
In both our local and remote environments the module update ran successfully, but in both cases the db hook update does not appear to be applied per the status report error.
I see that hook in the module code but it does not seem to apply with updatedb?
dgilbert → created an issue.
We ran into the same exact error running updatedb after upgrading from 10.1.5 to 10.1.7. Deleted and reinstalled core and the problem was resolved.
@caspervoogt Thanks for the help, we were able to get the module working with D10.
We're currently using 1.48 but the #16 patch fails to install using composer with this error:
Cannot apply patch https://www.drupal.org/files/issues/2023-09-15/3362505-16-d10additions.patch
Any thoughts on how we can get the patch to install?
Or the other option would be to set composer to use the fork as source but we're not exactly sure how to do that? This seems to work but not sure if it's the correct method;
composer require drupal/media_acquiadam:dev-3362505-upgrade-acquia-dam-1x-to
Added to composer "repositories"
{
"type": "vcs",
"url": "https://git.drupalcode.org/issue/media_acquiadam-3362505"
}Thanks for any help!