- 🇩🇪Germany Anybody Porta Westfalica
Eventually this could be closed as duplicate of 🐛 Locking field.storage should not lock field instance settings (field.field) Active but I'm not totally sure.
The locked attribute of a field (not instance!) is much too strict. You might want to allow the user to edit the instance field Label, but not delete it (enter fieldinstance.editable and fieldinstance.deleteable). Currently it's all or nothing:
* All: user can delete and edit the field instance and the field itself (too much power)
* Nothing: user can't delete or edit field instance nor field (no power at all)
If you want the user to be able to edit the instance (eg Label), you must set locked to 0 and then 'manually' prevent all other actions with nasty meaningless form alters.
The infrastructure for this practically exists. A small database update and a small code update in core/field_ui should do it.
Active
10.1 ✨
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Eventually this could be closed as duplicate of 🐛 Locking field.storage should not lock field instance settings (field.field) Active but I'm not totally sure.