My non-technical co-worker seems to find translated blocks difficult to work with, he would continually follow the "Configure block" contextual link to translate it, but then end up editing the source translation.
I would suggest a contextual link to translate the content and/or that the block configuration popup be more obvious about the content being the source translation (although my co-worker probably wouldn't have much of an idea what source translation means). Perhaps disabling (or with an option to disable) editing the source content directly from the configuration popup would produce fewer mistakes.
Discuss. :-)
As a stop-gap I wrote a small module that adds the contextual link.
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