Description of the need
This is a developer experience improvement proposal: When disabling a field in a display mode, every field on the content type gets updated due to the field weights being re-numbered. Similarly, if you arrange the enabled fields, all fields (including disabled ones) get their weights updated. This results in unnecessary configuration file changes, which can more easily lead to merge conflicts for people managing configuration in version control.
Proposed solution
The weights for disabled fields should not be stored at all (IMO), they should default to the main field weight specified by the field configuration. Disabling a field should not modify any other fields' weight. (Though enabling a field almost certainly will modify weight, since it needs to be positioned).
Recent comments
Hi I added the 2 additional settings in settings.php, did a restart - and the error disappeared! Thanks for the support! (but the issues with the conversion still remain .....
Problem with utf8mb4 Format when importing database
With JQuery, simple and fast. Or put all possible links in one menu, and hide unnecessary with CSS mediaquery.
Different primary menus depending on the viewport size?
I wonder if what is happening here is the default database settings are for utf8mb4 if the database server supports it. In settings.php or settings.local.php if that's where you put your...
Problem with utf8mb4 Format when importing database