Items translated in ATE but not on front end

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

Problem:
The client reported that two Divi modules were not being translated on the front end, despite the translations being present in the Advanced Translation Editor (ATE). The issue was observed after adding translations for Arabic, Japanese, Portuguese, and Korean.
Solution:
We investigated the issue and discovered that the problem was caused by an emoji (🌿) within the text. This emoji interfered with the translation display. We removed the emoji from the text and re-translated the page into Japanese, which resolved the issue. Additionally, we noticed that the database collation sequence had reverted to utf8mb3_unicode_ci, which could potentially cause issues with character encoding. We corrected this by changing the collation back to utf8mb4_unicode_ci.

If you're experiencing similar issues, we recommend checking for any special characters or emojis in your translations that might be causing display issues. Also, verify the database collation settings to ensure they support extended character sets. For more detailed guidance, please visit our documentation on WPML documentation.

Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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. If necessary, do not hesitate to open a new support ticket with us for further assistance.

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

This topic contains 0 replies, has 0 voices.

Last updated by John-Pierre Cornelissen 4 days, 1 hour ago.

Assisted by: Osama Mersal.

Author	Posts
February 13, 2025 at 2:23 pm #16702271
John-Pierre Cornelissen	Background of the issue: New ticked as requested here https://wpml.org/forums/topic/how-to-accept-all-ate-translations/page/3/#post-16700718 Ok, thank you for helping here and splitting the other issue into a new ticket. As for this ticket, I now also added 3 other languages, so now we get ATE translations for Arabic, Japanese, Portuguese and Korean. The translations are published now, but I still see that there is an issue. Not entirely sure if that's also be a new issue. The problem is that there are two Divi modules that are not being translated on the front end. But of I search for the sentences in the ATE, the translations are there. See attached screenshot and this screen recording hidden link Symptoms: Two Divi modules are not being translated on the front end, even though the translations are present in ATE. Questions: Why are the Divi modules not showing translations on the front end? Is this a new issue related to the additional languages added?
February 16, 2025 at 9:35 am #16710274
Osama Mersal Supporter Languages: English (English ) Arabic (العربية ) Timezone: Africa/Cairo (GMT+02:00)	Hi, Thanks for contacting WPML forums support. I'll be glad to help you today. First of all, sorry for the late reply; it was due to a higher workload. I would need to look closely at your site, so I would need to request temporary access (WP-Admin and FTP) Preferably to a test site where the problem has been replicated. Your answer will be private, meaning only you and I can access it. ❌ Please backup your database and website ❌ ✙ I need your permission to deactivate and reactivate the plugins and themes and change site configurations. This is also why the backup is critical. ✙ I also need your permission to take a local copy of your site to debug the issue without affecting your live site. Best regards, Osama
February 16, 2025 at 12:48 pm #16710696
Osama Mersal Supporter Languages: English (English ) Arabic (العربية ) Timezone: Africa/Cairo (GMT+02:00)	Hi JP, Thanks for the access details. I checked the issue on the two Blurb modules and found that the issue happened because of the emoji in this string. (🌿 vegetarisch mogelijk) I deleted this emoji and re-translated the page into Japanese, which worked as expected. Kindly check the hidden link">Japanese page. Best regards, Osama
February 16, 2025 at 3:09 pm #16710881
John-Pierre Cornelissen	Good catch, thanks! That's weird though. Emoji's have been a problem in the past due to a wrong database collation sequence. I have fixed that back then by changing the collation to utf8mb4_unicode_ci. I just saw that the collation of most tables was incorrect again at utf8mb3_unicode_ci, while the default "Collation of server connection" in phpmyadmin was still utf8mb4_unicode_ci. I changed the collation of the tables back to utf8mb4_unicode_ci and the problem is fixed. Do you have any idea what could have caused the collation change? Thanks JP
February 16, 2025 at 3:16 pm #16710887
Osama Mersal Supporter Languages: English (English ) Arabic (العربية ) Timezone: Africa/Cairo (GMT+02:00)	Hi JP, I'm afraid I don't know why the collation has changed, but you can check the server log to see if you can determine when it changed and what triggered the change. Best regards, Osama
February 16, 2025 at 3:36 pm #16710930
John-Pierre Cornelissen	Not feasible as I have no idea when it has changed. Thanks for helping and have a nice rest of the weekend. JP