In the spirit of @jenlampton's "put things where users expect to find them" move, once #1262 is implemented, we should have it so that:
1. These tabs reflect the current setting. Something along the lines of "Comments are currently [closed|hidden] for the [content_type_name] content type.".
2. Either provide a link to the configure page and jump to the "Comment settings" tab (/admin/structure/types/manage/page#edit-comment) ...but then we'd need to figure a way to redirect the user back to the "Comment fields" or the "Comment display" tabs where they originally came from.
3. ...or open those settings (content type comment settings) in a modal so that the user does not have to leave the page they are at in the first place.
GitHub Issue #:
1274
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