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
Thanks!! Easiest for me to just give permission for anon users to see the admin theme. That worked. It's just for this one page.
Link field in a Content Type is malformed for annonymous user- Permission issue?
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme. By default, such users won't have permissions to see the...
Link field in a Content Type is malformed for annonymous user- Permission issue?
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS