In this guide: Checklist to fix the case where a translation exists but is not shown on the website.
Contents
- Symptom
- Review checklist
- When only one text fails
- Tip
Symptom
You have translated the texts from the panel or imported a JSON file, but when you open the page in the target language you still see original texts or old changes.
This case is usually related to a pending scan, cache, incorrect language, untranslated page not created, or strings not actually translated.
Review checklist
- Check that the page has been scanned.
- Check that the target language is configured in WPML.
- Open View strings and confirm that the translations exist.
- Check that the translations are not identical to the original text.
- Regenerate the Oxygen cache.
- Clear external caches if they exist.
- Check that you are visiting the target language URL.
- Check that the translated page exists inside WPML.
- Check whether the text really belongs to Oxygen or to another plugin.
When only one text fails
If only one specific text is missing, that element may not be supported yet, the text may be inside a non-translatable field, or it may belong to another plugin.
In that case, scan again and check whether the string appears in View strings. If it does not appear, contact support with a screenshot and support export for that page.
Tip
Do not start by emptying the whole website without reviewing the workflow. First confirm whether the translation exists, then regenerate cache, and finally check the target language URL.