Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing an issue where WPML does not recognize HTML tags like breaks or P tags in the ACF WYSIWYG editor.

Solution:
We recommend turning off the 'big segments' preference in ATE, as this has resolved the issue in our tests. If the problem persists, try enabling the option 'Use the previous version of the Advanced Translation Editor' in ATE, make a small change in your ACF field content, save it, and attempt to translate again. For more details, please refer to the errata page at https://wpml.org/errata/disabling-i-prefer-bigger-segments-is-not-working-properly/.

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. Should you need further assistance, please open a new support ticket at WPML support forum.

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.

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by haraldK-9 4 months ago.

Assisted by: Waqas Bin Hasan.

Author Posts
August 21, 2024 at 10:15 am #16089729

haraldK-9

Background of the issue:
I added an ACF WYSIWYG editor in my post to make some kind of excerpt. I use automatic translation. WPML does translate the content of the ACF field and it does show in the English version.

Symptoms:
WPML does not recognize the HTML tags like breaks or p tag.

Questions:
Why does WPML not recognize HTML tags in the ACF WYSIWYG editor?

August 21, 2024 at 12:49 pm #16090444

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Reference to our recent chat, I'm still working on this and 'll update you accordingly.

Regards.

August 22, 2024 at 6:31 am #16092782

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Thank you for your patience and cooperation.

I tried to reproduce the issue in my sandbox site at hidden link (one-click login), with only WPML, String Translation, ACF, ACFML and 2021 theme.

At first I was able to see the issue but when I turned off "big segments" preference in ATE, it started working fine (see attached).

I then tested one more with automatic translation, and it also worked just fine.

However, later turning on those "bigger segments" preference, the issue was back with the automatic translation.

So after some digging, I found that the issue has already been reported at https://wpml.org/errata/disabling-i-prefer-bigger-segments-is-not-working-properly/. This errata provides a temporary solution, like:

> Enable the option “Use the previous version of the Advanced Translation Editor.”

in ATE, then, make small change in your field's content, save and translate again.

I've tried this in the above mentioned sandbox site. Please check before trying in your own site and let me know if this works for you or not.

Screenshot 2024-08-22 111251.jpg
Screenshot 2024-08-22 111238.jpg
August 27, 2024 at 7:20 am #16107699

haraldK-9

Hi,
i followed your guide:
i enabled the option: “Use the previous version of the Advanced Translation Editor.”
Then i changed a small thing in my ACF field in my blog post => saved it and tried to translate.

Still the same problem. Should i try to delete the translation?

Thanks in advance for your help.

Best regards
Harald

August 27, 2024 at 7:38 am #16107747

haraldK-9

I changed the option i prefer big segments to off. Now it works.

Will there be a fix for that?

Thanks again