Php warnings after update to 1.1.0-beta5

@attilatilman → Thanks for reporting the issue. Hopefully, we will be close enough to release the first RC version of 1.1.x branch within weeks. After that, our key focus will be ironing out all these and similar issues of the upgrade path from 1.0.x versions. Therefore leaving this issue in Active status until then.

I’m experiencing this same issue. I’d just like to know if it’s something I need to worry about or if I can ignore it while it’s being resolved. Thanks.

@attilatilman, @ricardo garcía, could you please let me know from which version you upgraded to Acquia DAM 1.1.0-beta5?
Thank you!

Root cause found which is quite a lame coding mistake, actually: our 2 field definitions with different types (File / Image) both received the same field storage definition (source code):

Tomorrow morning I will open a merge request including the fix together with some minor improvements as well.

Overall changes looks ~~ just added one minor code improvement and on validating the changes on local I've found no more php warnings.

Marking this one RTBC

Feel free to change the status if anyone else having the suggestions.

Mostly looks good, except the update not only needs to be fixed, but a new update needs to be made to fix the error as well. Alternatively, you can increment the update hook number, but you may need to account for those who already ran the update.

The screenshot inserted into my comment on GitLab does not appear here on D․org, so pasting here its link: https://git.drupalcode.org/project/acquia_dam/-/merge_requests/90#note_4...

Now tested: when upgrading from 1.0.14 stable to 1.1.x dev version, after running $ drush updb no any error messages appear on the /admin/content/media page.

Automatically closed - issue fixed for 2 weeks with no activity.