Skip to content Skip to sidebar

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

Problem:
If you're experiencing issues with the translation of text in the Divi Text module not showing, it might be due to the presence of emojis while your database tables are using the utf8mb3 collation.
Solution:
We recommend two possible solutions:
1. Remove the emojis from the Divi Text module, re-save the page in the original language, and then complete the translation again. This is the fastest workaround if you prefer not to modify the database.
2. Convert your database tables (and relevant columns) from utf8mb3 to utf8mb4. Make a minor change to the page in the original language, and then complete the translation again. The utf8mb4 fully supports emojis and modern Unicode characters.

Please note that this solution might be irrelevant if it's outdated or not applicable 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. If the issue 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: 

This topic contains 8 replies, has 0 voices.

Last updated by Andrey 2 months ago.

Assisted by: Andrey.

Author Posts
February 23, 2026 at 4:35 pm #17843864

raminK

I would like to reopen this topic: https://wpml.org/forums/topic/translation-of-text-translated-text-module-not-shown/

February 23, 2026 at 7:49 pm #17844285

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for contacting WPML support.

I cannot reopen the support ticket, but I can request a new access within this ticket.

The following reply is private.

February 25, 2026 at 10:20 am #17850670

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for providing the details.

Unfortunately, I’m unable to log in to the staging site you shared. I’m seeing the message shown in the attached screenshot.

Please let me know the correct way to log in.

Access-protected.png
February 25, 2026 at 11:09 pm #17853161

raminK

Sorry about that, our host limits the IPs that can access the backend, I have deactivated the function, please try again.

February 26, 2026 at 2:20 pm #17856934

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thanks for updating me. I can now access the backend, but I cannot log in. I've got the following:

Error: The password you entered for the username w*** is incorrect. Lost your password?

Can you please check this too? The following message is private.

February 26, 2026 at 3:48 pm #17857356

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for providing the access credentials. That one works.

I have looked at this, but I do not see the obvious reason for the issue.

I want to ask you about the possibility of replicating your site locally to run some additional tests. I'll need to install a "Duplicator" temporarily or "All In One Migration" plugin on your site. This will allow me to create a copy of your site and your content.

Let me know how you feel about this.

February 27, 2026 at 11:11 am #17859469

raminK

Absolutely, go ahead!

March 2, 2026 at 12:53 pm #17864635

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you, I will check this and let you know.

March 2, 2026 at 2:28 pm #17865126

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

I appreciate your patience.

I’ve investigated the issue and found the cause. The problem occurs because the Divi Text module contains emojis, while your database tables are using the utf8mb3 collation.

You have two possible solutions:

1. Remove the emojis from the Divi Text module, re-save the page in the original language, and then complete the translation again.

This is the fastest workaround if you prefer not to modify the database.

2. Convert your database tables (and relevant columns) from utf8mb3 to utf8mb4. Make a minor change to the page in the original language, and then complete the

The utf8mb4 fully supports emojis and modern Unicode characters. translation again.

hidden link

Screenshot-2026-03-02-at-16-22-47.png
Días-de-Acción-por-la-Vivienda-Stay-Grounded.png