Maintaining the Fusion Builder (Avada) Compatibility with WPML

Mohamed Khafaja

Originally written

January 24, 2018

Updated

February 6, 2019

This documentation is intended for the Avada development team and web developers using Avada. It explains the process of maintaining the compatibility of the Fusion Builder with WPML, which is done by updating the language configuration file.

How the integration of the Fusion Builder works with WPML

To understand how the Fusion builder works with WPML, let us start by creating a simple page using the Fusion Builder. We will include a few modules, such as a Text Block, an Alert, and a Flip Box.

As you already know, these modules generate shortcodes, which wrap the content. You can see an example of this in the following image:

To translate the page we created, click on the “plus” icon found in the language meta-box on the top right.

This will take you to the Translation Editor screen, where you can translate your page. Fill in your translated text, and choose Translation is complete for each field, then click on the Save & Close button.

When we view the translated page in the Text editing mode, we can now see the translated strings wrapped with the page builder shortcodes.

Updating the language configuration file

You might need to update the page builder shortcodes in the language configuration file for different reasons:

1. adding a new shortcode to the page builder;
2. adding a new attribute to an existing shortcode; and
3. removing an obsolete shortcode.

You can download the language configuration file from our repository. Add the shortcodes or attributes to the existing shortcodes to the language configuration file

Page builder shortcode structure in the language configuration file

To extract strings from pages built using the Fusion Builder and load them on the Translation Editor screen, we need to configure WPML to identify the shortcodes and attributes containing the strings that require translation. This is done by adding a file, called wpml-config.xml, which is typically placed in the root folder of your theme. For Avada, we are hosting the language configuration file on our servers. It is set to override the local configuration file placed in Avada’s root folder, ensuring that the configuration file is always up to date.

The wpml-config.xml file is also used to configure the following elements:

1. Custom fields
2. Custom taxonomies
3. Admin texts / wp_options
4. Language switcher configuration
5. Page builder shortcodes

See our detailed documentation to learn more about the language configuration file structure and syntax.

As an example, let us see how we added the Flip Box shortcode to the wpml-config.xml file.

The structure of the above example can be broken down as follows:

• All the shortcodes are wrapped with the shortcodes
• The shortcode tag wraps all the tags belonging to one, single shortcode.
• The tag tag defines the name of the shortcode, which in this case, is the fusion_flip_box.
• Shortcodes can have one or more attributes; hence, we wrap them in the attributes (plural) tag and use the attribute (singular) tag to define the title of each attribute. In this case, we have the title_front, title_back, text_front, and the image

For shortcodes that include link attributes, you can make internal links automatically point to the translated version of that post by using the type option for the attribute. Here is an example:

Testing the language configuration file

To test the updated language configuration file, follow these steps:

1. 1. Set up an installation having both Avada and WPML activated. Activate the String Translation, Translation Management, and Media Translation add-ons.
   2. You will need to override the remote language configuration file with the updated one. To do this, navigate to WPML -> Settings page, and click the Custom XML Configuration tab. Copy the content of your updated language configuration file to the editor, and click Save.

1. 1. Create a new page, and add the new module(s) to it. In case you updated some attributes for existing modules, add these to the page as well. In this example, we will assume that the Button module was newly added to the Fusion Builder. Add it to the page, and Publish.

1. 1. Click on the plus icon to translate the page. This will take you to the Translation Editor screen.
   2. Ensure that the module textual elements are displayed on the Translation Editor screen.
   3. Fill in your translated text. Select Translation is complete for each field, then click on the Save & Close button.

1. 1. Check the translated page on the front-end.

The translated page shows all the translated strings, implying that the updated language configuration file is working properly. In case you are encountering any issues, please contact our compatibility development team. They will be happy to check issues related to the language configuration file.

Once done with the tests, please submit a merge request to our repository. Our compatibility developers will receive your requests and review it.