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
Bee's great. But if you don't want to install bee, or can't, or you already have a bunch of scripts you're used to using in D7, then the method I posted is quick and easy and all you really...
How to create a command-line (cli) routine or script (bee not required)
This was tricky, so i tried to stay minimal and try to snatch the very first procedure after file upload and inject rehashing there. The file is tinymce.pages.inc under the function...
File hashing uploads made through TinyMCE
Or you can install bee, get the benefit of all the included functions and either include your script using: bee php-script ../my-scripts/scratch.php https://github.com/backdrop-...
How to create a command-line (cli) routine or script (bee not required)