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
Hi I added the 2 additional settings in settings.php, did a restart - and the error disappeared! Thanks for the support! (but the issues with the conversion still remain .....
Problem with utf8mb4 Format when importing database
With JQuery, simple and fast. Or put all possible links in one menu, and hide unnecessary with CSS mediaquery.
Different primary menus depending on the viewport size?
I wonder if what is happening here is the default database settings are for utf8mb4 if the database server supports it. In settings.php or settings.local.php if that's where you put your...
Problem with utf8mb4 Format when importing database