[UX] Allow the label (perhaps machine name too?) of fields to be edited straight from the "Manage fields" and "Comment fields" tab.

We'd save users a few clicks if all they need to change is the label:

backdrop-make_field_labels_editable_from_manage_fields_tab

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/1443

GitHub Issue #:

1443

Log in or register to post comments

Recent topics

Importing the staged config throws an error: another field with the same name already exists

Posted 5 days 7 hours ago by Francis Greaves (themetman) in How-To and Troubleshooting

Comments Enhanced

Posted 2 weeks 13 min ago by (izmeez) in How-To and Troubleshooting

Why not add a Github star?

Posted 2 weeks 1 day ago by (izmeez) in How-To and Troubleshooting

Recent comments

@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...

Posted 5 days 43 min ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Thanks, I have to go out now, I will try later on and report back

Posted 5 days 6 hours ago by Francis Greaves (themetman) on:

Importing the staged config throws an error: another field with the same name already exists

Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....

Posted 5 days 6 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

[UX] Allow the label (perhaps machine name too?) of fields to be edited straight from the "Manage fields" and "Comment fields" tab.

Weekly office hours

Recent topics

Importing the staged config throws an error: another field with the same name already exists

Comments Enhanced

Why not add a Github star?

Recent comments

Importing the staged config throws an error: another field with the same name already exists

Importing the staged config throws an error: another field with the same name already exists

Importing the staged config throws an error: another field with the same name already exists