The other site has no XLIFF file for that domain and language under translations/, so the key prints itself. Then: the call names no domain and falls back to the admin interface's domain; the interface language is chosen from the cdna_locale cookie, then the account default, then the browser, so a site that never sets the cookie shows the default language; or the site is Twig and the templates use a Smarty modifier, where Twig needs __.translate(key, params, domain).
Answer
Templates and engines
Translation works in one site and not another
More in Templates and engines
- A partial shared between two page types sees different variables in each
- Which engine is this site using
- A snippet from the documentation does not work in my templates
- A variable assigned before the inheritance tag does not reach the parent
- A variable set inside an include does not survive outside it
Was this page helpful?
Your answer goes to the docs team.