I ran into a problem on a Drupal 7 site yesterday where the permissions for "Manage fields" and "Manage display" were not handled consistently across different entity types - creating a very confusing experience for users.
My use case: I wasn't able to determine which permission I needed to grant to allow a role access to manage fields on files entity.
Fortunately, I stumbled across this excellent module which lead me to this Drupal core issue where they are also working on the problem.
I would love to see the same fix for Backdrop.
GitHub Issue #:
1079
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