Acquia Dam sites broken with 1.16 due to issue #3611070.

Problem/Motivation

#3611070: SQLSTATE[22001] error when inserting DAM media with long alt text — acquia_dam_managed_image_alt column truncation introduces a critical bug that will break existing drupal sites.

Drupal's standard text field widget (string_textfield) only supports string and uri field types (field_types = {"string", "uri"}). It does not support string_long. string_long fields use string_textarea

Any existing site with entity form display configurations (core.entity_form_display.*) referencing string_textfield for acquia_dam_managed_image_alt will break or fail to render the form widget once the field type becomes string_long.

Note, Instead of converting the field type from string to string_long (which triggers form display breakages and schema type migrations), the string field type should have been kept, and instead increase max_length. Setting max_length: 2048 or 4096 on the string field definition will accommodate extremely long DAM metadata strings while avoiding field widget breakages, schema type shifts, and multiline text issues.

Steps to reproduce

Install a site with different media types and Acquia Dam 1.1.15. Update to 1.1.16. Site broken.

Proposed resolution

Create a new update hook to scan and update all core.entity_form_display config objects that reference this field to change their widget plugin from string_textfield to string_textarea (or another string_long-compatible widget).

or
Revert back to the string type, remove the bad update hook, and create a new update hook that correctly resets the type and sets the length to something longer.