Update on Divi 4.0 and WPML Compatibility

Right now (24th Oct, 2019) Divi 4 and WPML are not fully compatible. We’re working with Divi developers to review all problems and handle them. In this post, we list the known issues, so that WPML clients don’t waste time running into problems that we are already aware of.

Known Compatibility Problems Between Divi 4 and WPML

The admin language is being translated, instead of displaying in the original language

For example, you create a French translation and the admin switches to French too. This happens even though you want the admin to remain in English. Divi 4.0 is storing a translated cache locally. This is causing the admin to remain in a translated language.

Language switcher is not saved in Divi’s custom widget area

The Divi 4.0 theme allows you to add widget areas. When WPML’s language switcher widget is added to an area, it isn’t showing on the page. The same problem happens when the WPML -> Languages -> Widget language switcher option is used.

Background images aren’t being translated

Divi 4.0 lets you set an image as the background in a module or row. The original language image is being displayed, instead of the translated image.

WooCommerce products created in Divi Builder aren’t working

The entire product listing is being duplicated inside the description area of translated products.

Custom post types created in Divi Library don’t appear in WPML’s Translation Management

Because these post types aren’t showing up in Translation Management, content can’t be sent to translation services.

Unsynced content in Divi’s Global Modules can’t be translated

In Divi 4.0 you can insert a Global Module into posts and pages. These can sync design elements from the Divi Library. Any unique text you add to a Global Module isn’t appearing in WPML’s Translation Editor.

Divi Builder isn’t loading when using one domain per language

In WPML your translations can have a different domain for each language in WPML (for example, yourdomain.es and yourdomain.fr). The Divi Builder is only loading on the original language domain. It won’t load on your secondary language domains.

When a section is saved as a Global Module in Divi 4.0 the translations don’t appear

Divi 4.0’s Global Modules can be translated by WPML. When the Global Module is inserted into another page, it isn’t being populated automatically with the translated content.

Image URLs in Divi 4.0 image modules are not changing for different language domains

This happens if you use different domains for each language. The correct translated image appears when a Divi 4.0 image module is inserted. But the image URL is not updating to reflect the language’s domain.

WPML Sticky Links in Global Modules

If a Divi Global Module contains a WPML Sticky Link, it can’t be converted to a permalink.

UPDATE – 4th March, 2020

We have resolved most of the issues in this list in 4.3.7:

– The admin language is being translated, instead of displaying in the original language
– WooCommerce products created in Divi Builder aren’t working
– Custom post types created in Divi Library don’t appear in WPML’s Translation Management
– Unsynced content in Divi’s Global Modules can’t be translated
– When a section is saved as a Global Module in Divi 4.0 the translations don’t appear

We will update here again when there is more news.