WPML allows you to easily translate pages you build using your favorite page builder.
The following video outlines the basic setup and shows how to use WPML to translate pages built with page builders.
Required plugins and setup
For this to work, you need four plugins in your site:
- Page builder of your choice (Visual Composer, Divi, etc.)
- WPML plugin
- WPML Translation Management add-on plugin
- WPML String Translation add-on plugin
After activating WPML and the add-on plugins, you need to perform the initial WPML setup.
To be able to translate contents created with page builders, you will also need to enable WPML’s Translation Editor. WPML will prompt you to do this after activating the add-on plugins, but you can also do it manually.
Go to the WPML -> Translation Management page and click the Multilingual Content Setup tab. There, select the Use the translation editor option in the How to translate posts and pages section.
Adding WPML support to page builders
Any page builder that uses shortcodes can be easily configured to be translatable with WPML. All that is required is a WPML language configuration file added to the plugin. To learn how this is done, visit our page about integrating page builders that use shortcodes with WPML.
How to translate page builder contents
There are two ways contents created with page builders can be translated:
- Manually, by you
- By sending them to be translated by other translators
Use the following steps to translate the contents yourself.
- Click the plus icon for the language you want to translate the post into. You are taken to the WPML’s Translation Editor. All translatable parts of your page appear there.
- Contents in the original language are on the left. Put your translations into the boxes on the right. Please note that you can also style the translations just like with the original WordPress editor.
- Make sure to mark each part of the content as Translation complete.
- When you are done translating, click Save & Close.
Sending translation to other translators
To send contents created using page builders to be translated by other translators, you need to go to the WPML -> Translation Management page and use the following steps.
- Choose the type of your content (page, post, etc.), select it, and click Add to translation basket.
- Click the Translation Basket tab, and select the translator for a specific language. Please note that you need to setup the translators beforehand.
That’s it! Now, translators will be able to go to the WPML -> Translations page and start with the translation job. They will use the same Translation Editor described in the “Manual Translation” section above.
Translation of same texts that appear multiple time
Sometimes, you might have the same text that repeats on your page. WPML automatically recognizes the duplicate contents and offers it for translation as one field. This way, you don’t need to spend time translating the same texts in the page.
Naturally, WPML will display the translation of these texts in all the places that they appear on your page.
The following image displays a design created using Visual Composer, using three instances of the very same text.
When we translate that page, we can see that the editor only shows one instance of the field to translate this text. Again, this means that we only need to translate it once.
Finally, on the front-end, the translation of the text is displayed in all the places as intended.
Updating translation when page changes
You can always update the translation of pages that were already translated. When the contents of the translated page change, you can simply translate it, or send to translation, once again. This time, you will not need to translate all the contents once again, but only the part that changed, or were added.
WPML integrations with page builders
We are constantly working on adding more popular page builders to WPML’s list of integrations.
The following page builders are integrated with WPML:
If your favorite page builder is not yet integrated with WPML, learn how to easily do this in our guide about integrating page builders that use shortcodes.