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.
Problem: You are a website designer using WPML and have connected all your sites to share a single pool of credits, which results in shared translation memory and glossary across all sites. You are looking for a way to share credits but keep the translation memory separated by website. Solution: Currently, there is no option available to share credits while keeping translation memories and glossaries separate for each website. All connected sites to a specific automatic translation account will share the glossary, credits, and translation memory. We have noted your request and will mention it to our developers as a potential feature for future updates.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is using website management software that lists all available updates with links to the repository, but these links don't work for WPML because it is commercial software. The client requested adding links to the WPML release notes in the WordPress repository. Solution: We explained that WPML uses an installer plugin embedded within WPML itself, which manages updates. This process is complex and involves WordPress hooks and our remote server that provides the updates. The links in the Dashboard -> Updates section are generated by these hooks, and the update information is fetched periodically from our site and stored in the client's database based on their subscription.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening 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. For further assistance, please visit our support forum at WPML Support Forum.
