[Resolved] Adding base64 encoded fields to XML does not resolve

I am using latest WPML and latest Newspaper theme.

When trying to add a page to translation queue, I get the following error:

WPML cannot send some of the content to translation
Some of the content that you selected for translation includes fields that are encoded. Translators will not be able to work on this kind of content, so we removed it from the job.

Наши контакты: There are base64 encoded fields in this document
vc_raw_html: content: JTNDaWZyYW1lJTIwc3JjJTNEJTIyaHR0cHMlM0ElM

I have modified vc_raw_html in XML configuration as follows below. But it does not help.

<shortcode>
<tag>vc_raw_html</tag>
<attributes>
<attribute encoding="base64">content</attribute>
</attributes>
</shortcode>

Am I doing something in the wrong way?

This base64 encoding does not let me live a normal life as I have to dig inside the page raw html every time I face this issue.

Also, there are some fields that are base64 encoded in Cloud Templates but not encoded in Pages. So every time switch translating from page to template and vice versa, I have to modify the XML file.

I am a bit tired of this.

Is there an option to let WPML just pass through these base64 encoded fields? At least I would be able to translate it using a free online encoder/decoder. But for some reason WPML just blocks these fields and it wants me to do some "debugging" and "coding" every time.

In general it is strange that WPML detected a base64 encoded field and it still needs me to manually tell him it is base64. But you've already detected that it is base64! 🙂