Skip Navigation
Updated
October 11, 2021

If you have a theme that uses some custom made page builder modules, you will not be able to translate them without registering those modules first.

If you need to register modules from Elementor, Beaver Builder, or Cornerstone, please follow out documentation about registering page builder widgets.

Finding the Name of Your Page Builder Modules

Each page builder uses elements for building pages. Depending on the builder, these elements are called something different: elements, blocks, modules, widgets, etc.

Regardless of what they are called they need to be registered before they can be translated. In this example, we will show how to register WP Bakery module called mkdf_custom_font.

The first thing you need to do is to find the name of your module. Open a page where you have inserted the module and click the Classic Mode button.

Open Classic Mode

Search for the module that you want to translate. In our example it is this module:

[mkdf_custom_font font_family="Roboto" font_size="134" line_height="140" font_weight="700" letter_spacing="-0,5" text_align="left" content_custom_font="Wir vere nfachen Ihre Prozesse im Marketing, unabhängig und flexibel." color="#000000"]
Classic Mode

A name of the module that we are looking for and we want to register is mkdf_custom_font.  Be careful that you do not include other parts of the shortcode. For example, do not try to register “mkdf_custom_font font_family

Registering Shortcodes

To register a shortcode you have to go to the WPML Settings page and click the Custom XML Configuration tab. In our example, we use the following code to register the shortcode:

<wpml-config>
        <shortcodes>
                <shortcode>
                    <tag>mkdf_custom_font</tag>
                    <attributes>
                        <attribute>content_custom_font</attribute>
	        		<attribute>color</attribute>
                    </attributes>
                </shortcode>
        </shortcodes>
</wpml-config>

Notice that the module’s name is located within <tag> and </tag>.

Also, you can see that there are two attributes that will be translated, content_custom_font and color. You can add additional attributes if needed but in our example there is no need for translating attributes letter_spacing, text_align, etc. When done, click the Save button.

Registering the module

Before you can see your module in the Translation Editor you need to do the following:

  1. Open the original page with the module on the front-end. This will trigger the module registration.
  2. Update your original page. You can do a small change like adding a period and deleting it. Just be sure that once you click the Update button the translation has the round icon and not the pencil one. If you still see the pencil icon it means that the translation was not updated and the new module was not added to the Translation Management.
The update icon indicates that the module was registered successfully