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.
This topic contains 3 replies, has 2 voices.
Last updated by 3 months, 3 weeks ago.
Assisted by: Waqas Bin Hasan.
 |
Background of the issue: Symptoms: Questions:   |
 Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00) |
|
|
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.   |
|
|
|
|
|
