Skip to content Skip to sidebar

Home › Support › English Support › [Resolved] Encoded content

[Resolved] Encoded content

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 2 replies, has 2 voices.

Last updated by Diego Pereira 1 year, 9 months ago.

Author Posts
September 30, 2023 at 7:54 pm #14491971

sergeyD-7

I am using Newspaper theme and WPML, which are promised to be compatible.

I was successfully using them at my other site, which is in production for more than one year.
But with my another site I really face a lot of problems with the below error. I faced the same error before with templates. And I face it now with pages.

So, my question is who's problem is that? WPML or Newspaper Theme?

The description of the problem:

When I try to translate a page, it just stucks on the page hidden link...
So, I am trying to add the page to the translation queue manually. And then I get the below enclosed error message.

Please see this video for details:
hidden link

I also see that the error log contains two records with ATE Server Communication event:
Gateway Timeout
Service Unavailable

But the time of errors seems to not coincide with my actions.

The full error text is the following:

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: JTNDaWZyYW1lJTIwc3JjJTNEJTIyaHR0cHMlM0ElMkYlMkZ3d3cuZ29vZ2xlLmNvbSUyRm1hcHMlMkZlbWJlZCUzRnBiJTNEITFtMTghMW0xMiExbTMhMWQ4MTYuNDI5OTQ2Nzc2ODU2ITJkMzAuNDc5NjU0ODI0NjczNTUhM2Q1MC4zOTEwODE5ODYxMjg5OTUhMm0zITFmMCEyZjAhM2YwITNtMiExaTEwMjQhMmk3NjghNGYxMy4xITNtMyExbTIhMXMweDAlMjUzQTB4Y2UxYzZjMmYxMWQ3NmMxYiEyek5URENzREl6SnpJM0xqa2lUaUF6TU1Ld01qZ25ORGt1TUNKRiE1ZTEhM20yITFzZW4hMnN0ciE0djE2NzM5NDUxMDE1NjYhNW0yITFzZW4hMnN0ciUyMiUyMHdpZHRoJTNEJTIyMTAwJTI1JTIyJTIwaGVpZ2h0JTNEJTIyNDUwJTIyJTIwc3R5bGUlM0QlMjJib3JkZXIlM0EwJTNCJTIyJTIwYWxsb3dmdWxsc2NyZWVuJTNEJTIyJTIyJTIwbG9hZGluZyUzRCUyMmxhenklMjIlMjByZWZlcnJlcnBvbGljeSUzRCUyMm5vLXJlZmVycmVyLXdoZW4tZG93bmdyYWRlJTIyJTNFJTNDJTJGaWZyYW1lJTNF
To fix this problem, you need to tell WPML how these fields are encoded, so that WPML can decode them before sending for translation.

How to indicate to WPML that it needs to decode fields.
September 30, 2023 at 8:08 pm #14492051

sergeyD-7

I want to mention that I have added base64 to the XML configuration file as per below code. But it did not help. The same error appears.

<tag>vc_raw_html</tag>
<attributes>
<attribute encoding="base64">content</attribute>
</attributes>
October 2, 2023 at 12:14 pm #14497831

Diego Pereira
Supporter

Languages: English (English ) Spanish (Español ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello, welcome to the WPML support Forum!

While you are waiting for one of my colleagues to take this ticket and work on it, let me provide you with first debugging steps or if I can perhaps help with the issue quickly.

Please try the following:
- Add the following code to WPML > Settings > Custom XML Configuration:

<wpml-config>
<shortcodes>
  <shortcode>
    <tag>vc_raw_html</tag>
    <attributes>
      <attribute raw-html="1" encoding="base64">content</attribute>
    </attributes>
  </shortcode>
</shortcodes>
</wpml-config>

- Do a small modification on the page content and save
- Translate the page

If it does not work, please try with this XML:

<shortcode>
            <tag raw-html="1" encoding="base64">vc_raw_html</tag>
</shortcode>

Please let us know if it worked for you.

PS: As a workaround, you can edit this widget on translation using the manual editor. However, these modifications will be lost if you translate the page again using ATE/CTE:
- Go to the edit screen of the page (original language).
- Change the language using the Language switcher at the top admin bar
- if it display a warning, click on "Edit Anyway"
- Edit and save
October 3, 2023 at 6:37 am #14501475

sergeyD-7

Hello,
I tried your solution before and now. But it did not work.
The guys from Newspaper/Tagdiv recommended me to use classic editor instead of advanced translation editor. I don't know how but I managed to translate the affected pages.