Description of the need
When adding a new field to a content type, it automatically generates the field's machine name by using its title prefixed with field_:
In order to distinguish similar fields and to avoid mess in database, we always manually add the content type's name:
Proposed solution
I believe if the prefix consisted of field_ and content type's machine name like so field_listing_, it would only increase the usability and comfort of developing.
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...
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
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....
Importing the staged config throws an error: another field with the same name already exists