Follow this tutorial to learn how to create multilingual WordPress sites using the Avada theme and WPML.
- Getting started
- WPML translation tools
- Translating pages
- Translating pages built using the Avada Builder
- Translating pages built using the Avada Builder Live Editor
- Translating Avada Builder global elements, columns, and containers
- Translating Avada layout sections
- Translating Portfolio pages and categories
- Translating Avada sliders
- Translating texts from Avada theme, plugins and other places
- Translating Avada’s menus
- Setting theme options for languages
- Adding translation support for Avada Builder elements
- Known issues with Avada
- Getting help – WPML Forum
- Get help with building and maintaining your site
- Get WPML
Make sure to activate the Avada theme on the Appearance → Themes page.
You will need the Multilingual CMS version of WPML. Install the WPML core plugin plus String Translation, Translation Management, and Media translation add-ons.
Want to see how Avada and WPML work together? Check the multilingual demo created by Avada team.
Besides translating your site content yourself, you can also:
- Send your content for translation to a professional translation service.
- Create your own team of local translators from the Translation Roles tab in Translation Management and assign translation jobs to them.
With WPML, you can translate any types of contents on your site, including pages and posts. For an easy start, read our Getting Started Guide.
WPML allows you to translate content in three ways: you can translate yourself, send content to your own translators, or send jobs to a translation service. Please visit our documentation page for exact steps on how to translate contents built with page builders.
To manually translate a page built using the Avada Live editor, follow the steps below:
- After building your page using the Avada Live editor, you need to publish the page to be able to translate it. Simply, click the publish icon then click Save.
- Click the Exit to page back-end option to navigate to the default page editor.
- Click the plus icon in the language box to translate the page.
Avada Builder allows you to save Elements, Columns, and Containers as Global Elements. Global elements are saved to your Avada Library and you can insert the global item into any page you want. Updating any instance of a global item will update all the items inserted into the different pages on your website.
Here is a quick video that demonstrates the global emenets, columns, and containers translation process:
Translating the Avada Builder global items is a simple two-step process:
- Translate the global item text by clicking the plus icon in the language box on the global item editing screen.
- Translate the page that includes the global item that you have already translated. Note that WPML will not load the global item text into the Translation Editor page. This is normal as we have already translated the global element text.
You can insert the translated global element, container or column into any page on your website without worrying about translating its texts. Simply, click the plus button to translate the page content. The translated global element text won’t be loaded into the Translation Editor page as they are already translated. Translate other elements on the page and mark all the translated fields as Translation is complete.
With layouts, you can design your header, page title bar, content, and footer sections. Translating layouts is similar to translating the Avada Builder global elements. Simply, go to the layout section editing screen, click the plus icon corresponding to the language you want to translate your layout into, and translate the section content.
To translate Portfolio items or any custom post type items, you need to follow the same steps as for translating any other types of pages. Visit our documentation page for exact steps on translating the contents yourself.
You can translate Portfolio Categories while translating your pages, on the Translation Editor screen. There, you can translate the Portfolio elements as well as your Portfolio Categories.
Additionally, you can translate your Portfolio Categories on the WPML → Taxonomy Translation page. Select the Portfolio Categories from the drop-down menu and a list of your categories will appear. Click the plus icon to translate a category for the respective language and use the dialog box that appears to add your translation.
Keep in mind that the translations of categories are universal: if you make a change, they will be updated everywhere.
Avada comes with its own custom slider called Avada Slider. It is also bundled with the Slider Revolution and Layer Slider.
To translate sliders created using Avada Slider, follow the steps below:
- Navigate to Avada → Sliders and then click on the Slides Page link.
- To translate a specific slide, click the plus icon under the language you want to translate your slide into. You are taken to the Translation Editor page. Translate the slide content and save the translation. Repeat this step to translate all the slides belonging to a specific slider.
- The last step is to translate the page where you have added the slide.
This is how the translated slider looks like on the front-end:
Besides contents coming from posts and pages in your site, there are usually some texts coming from other places. The most common examples are themes and plugins.
To learn how to translate these texts, read our documentation page about translating strings.
With WPML, you can easily synchronize your language menus. For more information, please check our page about translating menus.
With Avada, you have to set theme options for each language in your site. You can do it manually, or you can import existing settings.
If you want to use the same settings for all the languages on your website, follow the steps below:
- Go to Avada → Options.
- Use the Language Switcher in the top Admin Bar and select All languages.
All languages will now use the options that you have set for your default WPML language. Any changes that you make will apply to all of your languages.
If you want to have different settings for each language, follow the steps below:
- Go to the Avada → Options page
- Use the Language Switcher in the top Admin Bar and choose the language for which you want to set options.
You can repeat these steps for all of the languages that you have on your site.
You can also export theme options that you are using in one language and import it to another. For this, use the following steps:
- In the Language switcher choose the language from which you want to export the settings.
- Go to the Avada → Options page and in the menu, click Import / Export.
- In the Export Options section click the Copy Data button and copy the text with the settings.
- Use the Language Switcher in the top Admin Bar and choose the language for which you want to import the settings.
- In the Import Options section click the Import Contents from File button and paste the text with settings.
- Click the Import button.
You can repeat steps 4 to 6 for each language that you want to use those same settings.
WPML allows you to manually enable the translation of additional Avada Theme and Builder elements along with thier attributes.
To translate any textual element in any these shortcodes, you must add them to the Custom XML Configuration tab found on the WPML → Settings page.
Let’s consider an example of a Person element which includes texts that require translation. In this case, you would add the following code on the Custom XML Configuration page.
The following is the list of all shortcodes you can add manually, along with their attributes:
- Portfolio (fusion_portfolio) | Attributes: cat_slug, exclude_cats
- Post Slider (fusion_postslider) | Attributes: excerpt, category
- Recent Posts (fusion_recent_posts) | Attributes: cat_slug, exclude_cats
- Column (fusion_builder_column) | Attributes: background_image, link
- Container (fusion_builder_container) | Attributes: background_image, video_preview_image
- Content Boxes (fusion_content_box) | Attribute: image
- Countdown (fusion_countdown) | Attribute: background_image
- Faq (fusion_faq) | Attribute: featured_image
- Flip Box (fusion_flip_boxes) | Attribute: image
- Image (fusion_image) | Attribute: image
- Image Frame (fusion_imageframe) | Attribute: lightbox_image
- Person (fusion_person) | Attributes: picture, social links
- Sharing (fusion_sharing) | Attribute: pinterest_image
- Testimonial (fusion_testimonial) | Attribute: image
- WooCommerce Carousel (fusion_products_slider) | Attribute: cat_slug
<wpml-config> <shortcode> <tag>fusion_person</tag> <attributes> <attribute>picture</attribute> <attribute>social links</attribute> </attributes> </shortcode> </wpml-config>
We have a dedicated page that explains the process of updating the language configuration file in order to maintain compatibility between Avada Builder and WPML.
In case you need help translating your site built using Avada and WPML, visit WPML’s support forum.
If you need help with building or maintaining your site, take a look at the list of WPML Contractors. They are experienced developers specialized in developing multilingual sites.
Don’t have WPML yet? You can test WPML for 30 days and see if you like it.
If you are not happy with our plugin, we refund you without any questions in the 30 days.Buy and Download