In this document, you will find instructions on how the individual Layout Sections of a single Layout in Avada can be translated for different languages using WPML. Avada gives you an option to set individual layouts for each language as well as to translate the layout sections of the layout into different languages.

You can download and install Loco Translate plugin by going to WordPress Dashboard > Plugins > Add New Plugin section.

The Loco Translate plugin can be updated independently outside of an Avada update. The update notification will be visible when an update is available, and can be accessed via the WordPress Dashboard > Plugins section.

Select Avada from the list and you will be taken to a page, from where you can add a new language.

While selecting the language, make sure that you also select the location of files in the lanuage folder, so that your language files are placed inside wp-content / languages / themes folder for the Avada Website Builder and wp-content / languages / plugins folder for the Avada Core and Avada Builder plugins.

This makes sure that files are not wiped out during an Avada update. The Loco Translate plugin will append the required language ISO code itself.

The process of Language Selection, Language Location and Translation is exactly same as for the Avada Website Builder files.

In this document, you’ll find everything you need to translate the Avada Builder Plugin assets into your language. The process of translating the Avada Builder plugin is very similar to translating the Avada theme itself, except for some naming conventions. Let’s take a look at translating the Avada Builder plugin!

To further understand how translating the plugin works, we’ve included this section to explain where you can find the files needed for translation and what these files are for. Avada Builder comes with a steadily growing number of available languages, which can be downloaded from our public GitHub Repo. These are pre-defined translations, powered by our user base. You can see usage details here: Included Language Files

If your language is not already part of our repository, you can easily create your own translation files. At wp-content/languages/plugins you will find this file: fusion-builder.pot – This file is basically a list of all the text strings used in the Plugin files. These text strings are in the English language, and can contain a translation for each text string.

This file can be used as a starting point to create your own translations, using e.g. a free third party tool like POEdit.

In order for WordPress to recognize the resulting language files, you must name them accordingly using the ISO Language Codes. For example, if you wanted to translate Avada Builder to the Deutsch language, the filenames would be Avada-de_DE.po and Avada-de_DE.mo. Please see the next sections for detailed instructions on how to do so.

Using the correct language code is an important factor to successfully translating the plugins. If you look on the System Status page, you can easily see which language code you’re using. Please continue reading below for more information on how this is done.

Step 1 – Go to the Avada > System Status tab.

Step 2 – Under the WordPress Environment section, you will find a field called Language. the code located in this field is your language code. For example, en_US.

If your language is not already included, the only thing you have to do is to create a new .po file from the original fusion-builder.pot located in the languages folder, translate all text strings, then save the .po file with your language code and make sure the corresponding .mo is created, which can be read by WordPress. The next subsection will explain this in detail. If you only want to change translated strings in an included .po file, the same steps apply.

Either you are setting up a completely new language file or you just want to edit translated pre-built language files, the steps to take are easy and more or less the same.

The language files can also be used if you only want to translate a small portion of the theme, or one specific area. You do not have to translate the entire plugin, you can choose what you translate inside the Avada.po file. This is the preferred method for translation.

There are different editors out there for the purpose of editing .po files, but POEdit is easy to use, it is available for all platforms and it is freeware. To download POEdit, follow this link.

Step 1 – Open the fusion-builder.pot in POEdit by selecting ‘New from POT/PO file…’. Once it has loaded, you will find all English text strings in the left column called Source Text. Once you add translations, they will show up in the right column under Translation.

Step 2 – Choose the line you want to translate. In the lower right section of the POEdit window, you will find a text area where you can add the correct translation.

Step 3 – When you are done translating all the needed text strings into your desired language, save the file with the theme name and your language code. For example, if you were translating to the Deutsch language, you would save it as fusion-builder-de_DE.po. The corresponding .mo file will be auto created.

Step 1 – Open the .po file of your preferred language in POEdit and search for the line you want to change. To do this in Windows, select the Edit button, then select the Find option. To do this in OSX, select the Edit button, then select the Search option.

Step 2 – In the Search Window, type the text string you are looking for. Once it is selected, replace the text in the Translation text area in the lower part of the window with your prefered translation.

Step 3 – If you’d like to edit another text string, just repeat Steps 1 to 2.

Step 4 – Once you’re happy with your translations, Save the file. The updated .mo file will be auto created.

Updating the Translations Catalogue usually isn’t required. However, if you want to retain your customized Language file, and new strings have been added to a new version of the plugin, then you can choose to update from the .pot file to include the new strings to your current Language file. Another reason why updating the Translation Catalogue might be a good idea is if text strings have been added or edited through a Knowledgebase fix. You may need to update the catalogue of your existing .po file to reflect these changes.

Step 1 – Open the .po file of the desired language in POEdit.

Step 2 – Choose ‘Catalogue’ from the options in the toolbar, then select ‘Update from POT file’ option.

Step 3 – In the opening file dialog, choose the fusion-builder.pot file in fusion-builder/languages/ folder. The catalogue will then be auto updated with all the new text strings, and your custom ones will be preserved.

Step 4 – Don’t forget to Save the file once you are done updating and adding translations.

Step 1 – After applying patches, open your existing language file in POEdit and click ‘Catalogue’ in the toolbar, then select the Properties option.

Step 2 – In the opening file dialog, click the Sources Paths tab. Click the New Item icon. After that, Set the path to “../” (two periods and a backslash) as illustrated in the screenshot below.

Step 3 – In the Sources Keywords tab, click the New Item icon. First add “__” (two underscores) and then “_e” (an underscore and the letter e) as illustrated in the screenshot below.

Step 4 – Click OK to close the window. Once you’re in the main screen, click Update icon. Now POEdit will search for all new strings in Avada. Once they are imported, you can translate them to your desired language.

Before attempting to make your own translations, we suggest checking the pre-created language files that ship with Avada. All these files have been contributed by our amazing users, and the amount of translated strings might vary for each language.

Step 1 – Head to the GitHub Localization Repo.

Step 2 – Click the ‘Clone or download’ button in the upper right corner, and choose ‘Download ZIP’ to download the language files.

Step 3 – The download contains three sub folder: Avada, fusion-core and fusion-builder. The Avada folder contains the main translation files for the theme, while the other folders contain those for the corresponding required plugins.

Step 4 – Copy the .po and .mo files of your selected language to your WordPress install. For Avada language files, paste them to the wp-content/languages/themes folder. For plugin language files, paste them to the wp-content/languages/plugins folder. For detailed explanation of the storage locations, take a look here: Storing Translation Files.

Step 5 – Login to WP-admin dashboard and navigate to the Settings > General tab.

Step 6 – Find the Site Language option and select the language you’ve just added from the dropdown. For example, if you’ve added Avada-de_DE.po and .mo, you would select ‘German’ (Deutsch) from the dropdown.

Storing translation files in the right directory is very important to make sure the translations you’ve downloaded, created or edited remain functional and intact. The best way to do this is store them inside the languages folder located inside the wp-content folder.

Place your theme translation files inside wp-content/languages/themes folder. If you don’t have the languages and themes folder, simply create the languages folder, and the themes folder inside it.

Updating the theme will not overwrite the wp-content folder. Storing your translation files here will ensure they stay intact during updates.

When storing your language files, remember that the file structure is different and must include the theme name, as well. For example, if the language files are in the Deutsch language, the file names would be Avada-de_DE.mo and Avada-de_DE.po.

Place your plugin translation files inside wp-content/languages/plugins/ folder. If you don’t have the languages and plugins folder, simply create the languages folder, and the plugins folder inside it.

Updating the plugin will not overwrite the wp-content folder. Storing your translation files here will ensure they stay intact during updates.

When storing your language files, remember that the file structure is different and must include the plugin name, as well. For example, if the language files are in the Deutsch language, the file names would be fusion-core-de_DE.mo and fusion-core-de_DE.po.

We aim to make Avada convenient and available to as much users as we can, which is why Avada is RTL (Right to Left) ready. Avada contains all the necessary styles you’ll need to make your website RTL, and it’s as easy as 3 steps to set up! Once you finish these steps, your site will automatically be in RTL format. In addition, for testing you can also use a language plugin like RTL Tester. To download RTL Tester, follow this link.

Step 1 – Install an RTL version of WordPress, such as the Arabic or Hebrew version.

Step 2 – Have the proper Language files installed in the languages directory, which you can locate by following this path: wp-content > themes > avada > languages.

Step 3 – Specify the language you’d like to use in the wp-config.php file.