I am facing an issue with website translation.

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

Problem:
The client was experiencing an issue where the English version of a page was displaying content in French, despite being fully translated. This problem was linked to the use of emojis in the content, which is a known issue with WPML and page builders.

Solution:
1. We removed the problematic emoji from the original French content, saved, and updated the translation. This action allowed new content to appear for translation, which was then completed.
2. For a permanent fix, the client can either remove emojis from the content or apply workarounds from the errata page on using emojis with page builders (https://wpml.org/errata/using-emojis-with-page-builders-might-make-the-content-not-available-for-translation/).
3. Additionally, for issues related to WP Bakery Page Builder not translating some elements, it is recommended to register these elements following the guide here: https://wpml.org/documentation/support/language-configuration-files/register-page-builder-content-for-translation/. After registering, make a minor edit in the default language content and update the translation.

If these solutions do not resolve your issue, or if they become outdated, we highly recommend checking related known issues (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 the problem persists, 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: Exception, Known issue

This topic contains 36 replies, has 2 voices.

Last updated by Waqas Bin Hasan 9 months, 1 week ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
September 7, 2024 at 6:58 am #16150823
yuanL-2	As I already mentioned in this ticket and also in my previous ticket, the translation is 100% completed, I already tried your mentioned steps and it didn't work. and I also gave you the login credentials you can see that the translation is 100% completed on the mentioned page. Why do you guys repeat the same answer again and again? it's so annoying 🙁 You can create a duplicate site by taking my website backup for testing purposes, you already have access. Please take it seriously, I already wasted too much time with you guys chatting.
September 9, 2024 at 5:21 am #16153437
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Well, you haven't mentioned or permitted about taking your site's backup previously. All you only provided access with several warnings of not changing anything. We can not make any change, and/or, take site backups without confirmation. Anyways, you have allowed to take site backup just yet, I'll try my best to create a backup and restore in a test/staging site. But please be aware, since your site has lot of plugins and content, it may take some time. That's why I've been requesting you to provide an access to your own staging/test site. So then I can create my own, as needed, by eliminated unnecessary content (including plugins and themes). Because I can't do this on a live site. I'll get back to you accordingly.
September 9, 2024 at 1:01 pm #16156547
yuanL-2	I mention this in my previous tickets, I am waiting for an update. Thanks
September 10, 2024 at 7:12 am #16159526
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience and cooperation. I've downloaded the backup of your site by using a pre-installed All-in-one Migration plugin. I didn't download the images to reduce the size of the package (to 1.1GB approx.). I'll try to setup this on my local or in a dev environment and 'll investigate further. I'll update you accordingly.
September 10, 2024 at 1:28 pm #16161791
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	I am still working on this and 'll get back to you as soon as I find something or have a solution.
September 10, 2024 at 8:52 pm #16163652
yuanL-2	Okay, thank you!
September 12, 2024 at 11:12 am #16170397
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience and cooperation. After several tries by taking your site backup (using different plugins), I was able to create a test site at hidden link. I am working on this and 'll get back to you as soon as I find something or have a solution.
September 12, 2024 at 12:44 pm #16170990
yuanL-2	Yes Please, I am in an agitated situation.
September 13, 2024 at 5:57 am #16173896
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience and cooperation. I was able to observe and fix the problem. Actually the problem occurs due to use of emojis in the content. This is a known issue and is under consideration. The linked errata provides some workarounds to deal with this. However, I didn't apply those workarounds, while I simply removed the problematic emoji from the content in original language (French), saved and updated the translation (see attached). After removing that, some new content (a few sentences) appeared for translation, which I completed using Google Translate and saved the translation. This is where it was breaking and you were seeing the mix of the content. Now, the hidden link">page in English has all the translated content displaying properly (screencast hidden link). In short, you can either try the workarounds from the said errata. Or can simply remove emojis and complete the translation. Please note that not every emoji is a problem, you can still see some emojis in the content. However, it is recommended not to use if you don't want to go for the temporary workarounds. You can use images instead.
September 16, 2024 at 10:15 pm #16185631
yuanL-2	How do I know this is the problematic emoji?
September 18, 2024 at 6:48 am #16191147
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Well apparently there's no way to tell which emoji creates the problem. It is better not to use these but if you see the similar problem with your content when translating, you may remove the one where it is breaking.
September 21, 2024 at 7:14 pm #16205188
yuanL-2	Okay thanks, let me try in this way.
September 21, 2024 at 7:54 pm #16205219
yuanL-2	I removed all emojis from this article but the issue is same, I followed the steps you mentioned in your last message. but it didn't work 🙁 I am very disappointed! hidden link
September 23, 2024 at 6:05 am #16207398
Waqas Bin Hasan WPML Supporter since 05/2014 Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for the updates. Looks like you need to register page builder elements, coming from WP Bakery Page Builder to properly recognized by WPML. This is a common case among page builders which are always evolving with new elements, as well as, changes in the existing ones. I'll recommend checking this guide https://wpml.org/documentation/support/language-configuration-files/register-page-builder-content-for-translation/ and register those message boxes and accordion elements properly. Then make changes in the page content, in default language (i.e. a word or dot) and save. Afterwards update the translation and you should see the content available in the translation editor. Please note, that since this is a different problem than previously found. I'll recommend opening a separate ticket, particularly mentioning about "the content not being translated from those particular elements or widgets". Because as per forum policy we can only handle one issue per ticket/chat. So you can get more to the point help, without mixing up several issues in one long ticket.
September 23, 2024 at 1:40 pm #16210114
yuanL-2	Hello, Thank you for your response. I don't understand what you meant by "this is a different problem than previously found. I recommend opening a separate ticket." What issue regarding my website translation have you resolved since I opened this ticket? Since I am facing the same problem, why should I open a new ticket when a solution has not yet been found?