In this guide: Frequent problems when importing JSON and how to avoid them.
Contents
- Invalid JSON
- Incorrect target language
- Strings that no longer exist
- Untranslated texts
- Modified HTML or shortcodes
- Incorrectly modified URLs
Invalid JSON
This is the most common error. It can happen if incorrect commas, comments, text outside the JSON, or markdown formatting have been added.
Solution: ask the external tool to return only valid JSON and validate the file before importing it.
Incorrect target language
The file must correspond to the correct target language. Do not try to import translations into the source language.
If the language does not appear in the selector, review the WPML configuration.
Strings that no longer exist
This can happen if you exported a JSON file, then changed the page in Oxygen, and later try to import the old file.
Solution: scan again and export again before translating.
Untranslated texts
Some tools may leave values identical to the original language. The plugin may not count them as a useful translation.
Review the texts marked as identical to the original and translate them properly.
Modified HTML or shortcodes
If the external translation modifies tags, attributes, or shortcodes, the result may break design or functionality.
Solution: keep HTML and shortcodes intact except for the visible texts that need to change.
Incorrectly modified URLs
Not all URLs should be translated. Some should remain the same, and others should be adapted to translated pages.
Review internal links, buttons, and visible URLs before publishing.