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
Hello. Welcome to Backdrop Some of the things you are asking for can be done with Ubercart. Ubercart out of the box supports buying a role, which could satisfy your paid memberships...
How to monetize a Backdrop site
Hi..., And welcome to our Backdrop community. Do you mean modules to help someone monetise their own website, or the official backdrop website?
How to monetize a Backdrop site
Title: Simplenews 1.x-1.2.2 removes subscribers when using anonymous checkout with Ubercart Hello, I experienced an issue when updating Simplenews to version 1.x-1.2.2. My site...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled