The text was overridden but suddenly reverted back to the original.
However, the overridden text is still there, it just doesn’t show.
Reverting and reapplying the change does not resolve the issue.
Discourse 3.3.2 stable.
AI-generated summary
A user reports an issue in Discourse 3.3.2 where overridden text reverts to the original despite being saved. The problem occurs when searching for text by its content (e.g., “sign up”) rather than its key (e.g., “js.sign_up”). RGJ notes that the overridden text remains but isn’t displayed. Moin observes that searching by the key instead of the content reveals the correct text, and the “only show results in selected locale” checkbox helps. RGJ clarifies this checkbox is missing in 3.3 stable. tobiaseigen confirms the issue and suggests the UI behaves differently depending on the search method, recommending the problem be added to the development list.
2 Likes
What happens if you search for js.sign_up instead of “sign up”?
1 Like
Interesting. And I see that the button text did change after reverting and reapplying.
Do you understand what is happening @moin ?
2 Likes
Not really.
I selected German and even without an overwritten translation, I see “Sign up” as long as I don’t search with the name of the string.
The “only show results in selected locale” checkbox seems to help:
3 Likes
That does not exist on 3.3 stable 
2 Likes
@hugh can you add this to your list? I was able to replicate the problem as stated by RGJ in the OP and also the different behavior as stated in Moin’s reply.
tl;dr the UI behaves differently when searching for “Sign up” (content of the text field) vs “js.sign_up” (name of the text field), then changing the content of the field, then going back to the search.
- expected and correct:
/admin/customize/site_texts?locale=en&q=js.sign_up - unexpected and broken:
/admin/customize/site_texts?locale=en&q=sign%20up
3 Likes