Follow up to https://github.com/backdrop/backdrop-issues/issues/704:
Seems to be that locale.module remembers the path at which the translated string was first seen, then provides a path to that location? Perhaps that's so that you can try and find if a string is used on that page. However... not very useful for something like site_name which is literally on every page. If we can find a way to suppress this behavior when strings are translated through config, that would be preferable. Most config strings will probably be shown in lots of places (e.g. field labels and descriptions, view names, block titles, etc)
For reference, in D8 there's now a separate table for locale location and it better represents config strings:
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