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
Thank you very much for your fast answers and clear explanations ! I understand that the site is not corrupted and that there is no danger in leaving the code and the database in their...
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}
Until the official new release (coming soon), the error will ALSO show up when you clear caches, unless you fix this manually as above.
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}
If you want to try to fix it yourself now, I think you can manually set the schema version for the book module (in the system table) to 7000, and then try running the updates again. Test on a...
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}