[Resolved] WPML cannot send some of the content to translation

Problem:

The client was unable to send a Global Header with base64 encoded fields for translation using WPML. Attempts to configure custom XML to handle the encoding were unsuccessful, resulting in errors and the removal of content from the translation job.

Solution:

We recommended updating the XML configuration in WPML settings to properly handle base64 encoded fields. Here is the correct XML configuration:

<wpml-config>
  <shortcodes>
    <shortcode>
      <tag>fusion_button</tag>
      <attributes>
        <attribute type="link">link</attribute>
        <attribute>title</attribute>
        <attribute encoding="base64">dynamic_params</attribute>
      </attributes>
    </shortcode>
    <shortcode>
      <tag>fusion_imageframe</tag>
      <attributes>
        <attribute encoding="base64">dynamic_params</attribute>
      </attributes>
    </shortcode>
  </shortcodes>
</wpml-config>

This configuration should be added under WPML->Settings->Custom XML Configuration. Additionally, we provided links to relevant documentation and known issues:

• Known issue with Avada
• Documentation on creating XML configurations for Avada

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML support forum.