Missing Translation Error after Theme Update

Technical Q&A

Topic summary

Missing translations appear after an Expanse Theme update for three section keys (header-group, popup-group, footer-group) in en-US/en locale schema.

Meaning the i18n keys are not found in the locale JSON files (locales/en.default.json and locales/en.json). The Shopify Customizer is the theme editor where labels appear.

Proposed fixes:

  • Quick workaround: In the Customizer, replace the i18n token with a literal label (e.g., Header Group) so a user-facing name shows.
  • Proper fix: In the code editor, update locales/en.default.json and locales/en.json to add or rename keys to match the theme’s new keys (possibly pluralized, e.g., t:sections.header-groups.name).

Follow-ups:

  • One participant asked whether this was solved.
  • Another asked for step-by-step instructions on replacing the token.

Status: No confirmed resolution yet; clarification on how to perform the replacement and the exact new keys is pending.

Summarized with AI on December 13. AI used: gpt-5.
1

After installing the most recent “Expanse Theme” Update I have these errors showing up

missing translation: “t:sections.header-group.name” is not present in any of the [“en-US”, “en”] schema locale files### missing translation: “t:sections.popup-group.name” is not present in any of the [“en-US”, “en”] schema locale files### missing translation: “t:sections.footer-group.name” is not present in any of the [“en-US”, “en”] schema locale files

How can, I correct these?

2

Hey @MariLynn_McClos

The easy way to fix this error is replacing this “t:sections.header-group.name” by the name that you want to show it there in Customizer of Shopify e.g:- “Header Group”
The harder way to fix this error is by making changes in en.default.json and en.json files in locales of code editor and look for the new name of t:sections.header-group.name that is updated by theme something like “t:sections.header-groups.name” and then replace in json the new name of these t:sections.header-group.name etc.

3

Did you ever get this solved?

4

Can you please explain how you would go about "replacing this “t:sections.header-group.name” " ?