WPML allows you to easily translate pages you build using your favorite page builder. Read this guide to learn which page builders are supported and how to translate page builder designs.
To translate page builder content, you need to install:
- WPML String Translation
- WPML Translation Management
We are constantly working on adding more popular page builders to WPML’s list of integrations.
The following page builders are integrated with WPML:
- WPBakery Page Builder
- Divi Builder
- Avia Builder (Enfold theme)
- Beaver Builder
- Fusion Builder (Avada theme)
- SiteOrigin Page Builder
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.
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.
1. Click the plus icon for the language you want to translate the post into. The plus button is accessible either from the page either from the listing pages as you can see in the table below:
|The plus located in the Language box when editing my page.||The plus located under the flag in Pages -> All pages|
2. You are taken to the WPML’s Translation Editor. 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.
3. Make sure to mark each part of the content as Translation complete:
4. When you are done translating, click Save & Close.
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.
1. Choose the type of your content (page, post, etc.), select it, and click Add to translation basket.
2. 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.
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 WPBakery Page Builder, 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.
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 was added.
When updating the default language page content make sure not to update the text and the position of an element inside the page as this will result in losing the translated text. Read more about preserving the existing translations when editing the default language page.
In this example, I added a Text Box element to the “About Us” page:
Note: Remember to Update the page after adding the module. This is important because it will load the textual elements of the module to the Translation Editor screen.
In the Language meta box, you will see an arrow instead of a plus button. This indicates that the translation needs to be updated since you recently added some new content to your default language page. Click on the arrow to update the translation in your secondary language page.
You will see the WPML Translation Editor with new fields that need to be filled in. Also, note that the translation completion percentage is back to 75%.
Translate and mark the translations as complete, and then Save and Close.
Toolset plugins allow you to design Content Templates for displaying single posts of any post type. Usually, you use one template for all languages and translate only the texts inside, for example, labels or headings.
Alternatively, you can select to create separate Content Templates for each of your site’s languages. In this case, you should not send such templates for translation. Instead, you should edit the template in each language separately and translate them like that.
Toolset allows you to design Content Templates using the following page builders:
- WPBakery Page Builder
- Beaver Builder
If you use a page builder to design your Content Templates you have to translate your templates. To enable the translation of a specific Content Template go to the WPML -> Translation Management page and on Multilingual Content Setup tab find the Post Types Translation section. Here, mark your Content Template as translatable.
Now you can send your Content Template for translation. Translation process is the same as described above on this page.
However, if you have previously selected to use different Content template for each language you can not use this workflow. Instead, you have to use your page builder to individually add content to each language’s Content template.
To check the status of the Create different Content Templates for each language option, go to the Toolset -> Settings page and click the WPML integration tab.