Problem: The client was facing an issue with the Advanced Translation Editor (ATE) where certain items on their menu page were not being translated correctly, specifically those containing emojis. Initially, replacing emojis with text seemed to resolve the issue, but the client wanted a solution that allowed the use of emojis. Solution: We investigated the issue and found that it was related to the database collation settings. The database was using the
utf8_general_ci
collation, which does not fully support emojis as they require 4 bytes per character. We recommended changing the database collation to utf8mb4_unicode_ci or utf8mb4_general_ci to properly support emojis. After the client converted their database to
utf8mb4_unicode_ci
, the issue was resolved, and emojis were displayed correctly in translations.
If you're experiencing a similar issue, we recommend checking your database collation and updating it to utf8mb4_unicode_ci to ensure full support for emojis. However, this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, please open a new support ticket. We also 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.
Problem: The client stopped using WPML and encountered an issue with a large number of duplicated images in the media library, even after using the reset option to delete the icl tables. Solution: We recommend trying the following SQL query on a staging site to remove duplicate images:
DELETE p1
FROM wp_posts p1, wp_posts p2
WHERE p1.guid = p2.guid AND p1.ID > p2.ID AND p2.post_type = 'attachment'
It is crucial to back up the database and website before executing this query. Alternatively, the client can use the Media Cleaner plugin to clean up the media library. We also informed the client that WPML 4.6.3 was released recently and advised checking the changelog for more details.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket for further assistance.
