Because of the name of my community, it’s ideal that when reference in site texts I append "the " before %{site_text} in some cases. Great, the incredible feature of site texts exists and I can go through and update all references! Until…
There are more than 50 results. Please refine your search.
I realize that there may be an unbelievable amount of site text options, but surely in 2025 there has to be an efficient method of retrieving all results.
A post was split to a new topic: Access Denied error when trying to customize some site texts
I second this. I want to show all changed site texts but it’s impossible now because there are more than 50 texts. I can accept scrolling or pagination or exporting them to a text file, or the limit should be a configurable number.
In addition to seeing all texts, I also want to be able to export all texts of chosen locales and mass-edit them in my text editor, and then import my modification. My locale has poor translations (ಥ_ಥ).
If they’re changes that would benefit everyone using the locale, you could consider contributing! Contributing translations to Discourse
Welcome to Meta 
You can try using Data Explorer to find all entries in the translation_overrides table.
I’d like to, but after a period of usage and tinkering. And then, I need to export my modification, review and pick those that are suitable for every site, and then I need to figure out how to submit them to your translation platform (I hope I don’t need to copy-and-paste by hand).
This appears to be a UX issue so I have moved this to UX. I believe we’ve fixed this type of thing in other places (eg when looking at site settings) and it makes sense to do the same here.
This table has only changed entries. Unchanged texts seem to be scattered in various .yml files on the filesystem.
I know, but I was replying to @oldherl who asked for seeing all customized texts.
I am trying to customize the name of my forum’s “like” button (to “appreciate”). I’m having a hard time figuring out if I have gotten all the strings because there’s only so many variations of “like” to search for.
I’ll add: if there were a checkbox to limit results to non-customized strings, that would be an acceptable solution also.