Sometimes, you may encounter an encoding issue with fields sent for translation. WPML warns you about this and prevents sending jobs with such fields for translation, until you fix their encoding. This page explains how to easily do this.

When WPML prompts you about an encoding issue with fields, you can click to get a list of exact fields in question.

Warning about field encoding issues
Warning about field encoding issues

Once you know which fields are affected, you can use the following steps to their encoding.

  1. Go to the WPML -> Settings page and click the Custom XML Configuration tab. In the editor, find the field in question, as shown in the following example.
In the XML editor, find the field with an encoding issue
In the XML editor, find the field with an encoding issue
  1. Add encoding=”base64″ to the attribute of the field in question, as shown in the following image.
Add the encoding argument to the attribute of the field in question
Add the encoding argument to the attribute of the field in question

That’s it! Now, you can send content containing this field to be translated.

Encoding issue with fields coming from Avada Fusion Builder

Sometimes, an encoding issue can be related to fields coming from the Avada Fusion Builder. In this case, the fix is a bit more complex because this plugin features a global option to disable encoding.

This means that WPML should only try to decode the affected field if this option is set to true (i.e. “1”). The following code will add this conditional encoding to the field in question:

Add conditional encoding to Avada field
<tag encoding="base64" encoding-condition="option:avada_disable_encoding=1">fusion_code</tag>

And the following image displays an example of this, in the Custom XML Configuration editor.

Adding the conditional encoding attribute for an Avada Fusion Builder's field
Adding the conditional encoding attribute for an Avada Fusion Builder’s field