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
I'd like to learn more about options to handle payments in Backdrop: Ubercart and Commerce vs. standalone solutions and integrations with modules like Webform or Registration...
Backdrop Live November 2025
The accepted answer refers to Drupal and has weird formatting (missing capitalization at the beginning of paragraphs). Seems to me it was either copied from a Drupal post, or AI generated...
Ckeditor 5 click to activate
For the Dev meeting: I would like to discuss whether we should have a policy in the Forum that AI provided solutions should be attributed to AI and which model it is from. We have started...
October 16th 2025 Weekly Meetings