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.
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.
