Overview of the Issue
When using Divi Pixel with WPML on pages built with Divi 5, some newly added modules might not appear in the WPML Advanced Translation Editor. Because of this, content from modules such as the Timeline module cannot be translated properly.
Workaround
This issue is fixed in Divi Pixel 2.50.0. Updating solves it on your site, so you only need this workaround if you can’t update yet.
- Go to WPMLSettingsCustom XML Configuration in your WordPress dashboard.
- Add the following XML configuration and save:
<wpml-config> <gutenberg-blocks> <gutenberg-block type="dipi/timeline-item" translate="1"> <key name="module"> <key name="advanced"> <key name="link"> <key name="*"> <key name="value"> <key name="url" type="link"/> </key> </key> </key> </key> </key> <key name="ribbon"> <key name="innerContent"> <key name="*"> <key name="value"/> </key> </key> </key> <key name="title"> <key name="innerContent"> <key name="*"> <key name="value"/> </key> </key> </key> <key name="content"> <key name="innerContent"> <key name="*"> <key name="value"/> </key> </key> </key> <key name="button"> <key name="innerContent"> <key name="*"> <key name="value"> <key name="text"/> <key name="linkUrl" type="link"/> </key> </key> </key> </key> <key name="url"> <key name="innerContent"> <key name="*"> <key name="value"/> </key> </key> </key> <key name="url_new_window"> <key name="innerContent"> <key name="*"> <key name="value"/> </key> </key> </key> </gutenberg-block> </gutenberg-blocks> </wpml-config> - Update the original page and reopen the translation
Still Seeing This Issue?
If updating doesn’t fix it, ask a support question and we’ll look into it with you.
Ask a support question