WPML

Translation from second language are loaded when MO files are used

Published 2016-09-09 · Updated 2016-09-21
Status
Resolved
Reported for
WPML Multilingual CMS 3.5.1.1
Resolved in
WPML Multilingual CMS 3.5.2

Overview of the issue

The problem manifest itself when:

  1. Using WordPress 4.6.0 and higher.
  2. There is more than one language defined
  3. Option Don’t use String Translation to translate the theme and plugins is chosen in WPML > Theme and plugins localization
  4. MO file corresponding to the second language is uploaded
  5. MO file corresponding to the default language is not uploaded (as it usually happens).

Issue: strings belonging to a plugin or a theme might be shown translated to the secondary language.

For instance:

  • A site with English as default language and Bulgarian as a secondary language.
  • The site uses the WooCommerce plugin.
  • A product is created and added translated in Bulgarian.
  • When visiting the English page of this product, texts belonging to the WooCommerce plugin are shown in Bulgarian.

If the product is not translated, this does not happen.

Workaround

To prevent this problem, you have to upload the plugin’s MO file corresponding to the default language or downgrade to WordPress 4.5.4 (the version previous to 4.6).

All known issues →