Problem: After updating WPML, the language switcher no longer appears for users who are not logged in. This issue was initially thought to be related to the WPML upgrade, but it was later identified as possibly being linked to server issues or a compatibility problem with other plugins or themes. Solution: 1. Ensure that WPML and all other plugins are updated to the latest versions by navigating to Plugins > Add new > Commercial > click "check for updates". 2. If the problem persists, perform a compatibility check: - Create a full website backup. - Disable all plugins except for WPML and its add-ons. - Check if the issue still occurs. - If not, reactivate plugins one by one to identify the problematic plugin. - If the issue persists with only WPML active, switch to a default WordPress theme like TwentySeventeen to test further. 3. It is recommended to perform these tests in a staging environment if possible. If these steps do not resolve the issue, we suggest visiting the related forum topic for additional guidance.
Please note that this solution might be outdated or not applicable to your specific case. 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 the issue persists, please open a new support ticket.
Problem: If you're experiencing an error stating 'your account has a debt' while trying to translate content using the pay as you go service, it might be due to an unpaid invoice. Solution: We recommend checking for any unpaid invoices associated with your account. You can find your unpaid invoice here: Unpaid Invoice Link. Once the invoice is settled, the error should no longer appear.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML 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.
Problem: The client was experiencing an issue where a post appeared twice in the Advanced Translation Editor (ATE), leading to an incorrect calculation of translation credits. This duplication only affected the Spanish translation and was not visible on the front end. The client was concerned about being overcharged for translation credits due to this duplication. Solution: We investigated the issue and confirmed that the duplication was due to strings appearing under the wrapper tag twice. We suggested that the client delete the duplicate packages in WPML->Packages by locating the packages listed by the page ID and then deleting them. After making a small change in the default language page and updating it, the client should access the translation again to see if the issue persists. Additionally, we confirmed that the client was indeed overcharged and proceeded to refund the excess credits. For future translations, we recommended keeping an eye on new content to ensure this issue does not recur. If the problem persists or if this solution does not apply due to updates or different circumstances, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket.
Problem: The client was experiencing a WordPress database error due to an illegal mix of collations (utf8mb3_general_ci,IMPLICIT) and (utf8mb4_unicode_520_ci,COERCIBLE) for operation 'like'. Solution: We recommended the client to navigate to WPML->Support->Troubleshooting and execute the 'Fix WPML table collation' function. This resolved the issue.
If this solution does not resolve your issue, or seems irrelevant due to it being 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 problem persists, please open a new support ticket.
Problem: Si estás intentando actualizar tu sitio web y encuentras que la clave del sitio no es reconocida después de ingresarla, es posible que la clave de WPML se haya generado para una URL incorrecta. Solution: Te recomendamos visitar esta página, eliminar la clave actual de WPML y generar una nueva para la URL exacta de tu sitio. Luego, intenta usar esa nueva clave. Esto debería resolver el problema.
Si esta solución no es relevante porque está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client is unable to see the translated names of WooCommerce product attributes like 'color' and 'size' on the Danish version of their site, despite setting translations in WooCommerce Multilingual & Multicurrency. Solution: 1. Ensure that the WooCommerce plugin is updated to the latest version. 2. Recognize that local attributes added from the product edit screen are only translatable using the WPML Translation Editor. 3. Enable the WPML Translation Editor for the product, and use the Advanced Translation Editor to complete the translations. 4. After applying these steps, check the frontend to see if the translations appear correctly.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where the carousel in the French and German versions of your website displays the second photo twice instead of showing both photos individually. You are also having trouble using WPML's Media Translation feature to translate photos for different language versions. Solution: First, to avoid affecting your live site, we have set up a sandbox environment for you to replicate the issue. Please install the necessary theme and plugins there.
If the issue persists, you can try the following workaround:
If this solution does not resolve your issue or 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 contact us through the WPML support forum.
Problem: The client is unsure whether to make translation changes manually within their site or send them to memoQ. Solution: If you're experiencing similar confusion about where to make translation changes, we recommend the following steps: 1. If you want to change some of the translations, you can do it yourself directly in WPML. This allows you to manage and apply changes immediately without needing to contact memoQ. 2. However, if you prefer that memoQ handles the changes, you should contact them directly. This is not managed through WPML.
Please note that this solution might be outdated or not applicable to your specific 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 this does not resolve your issue, please open a new support ticket.
Problem: If you're experiencing issues with the & character being removed when translating strings in the Advanced Translator, you're not alone. Solution: We are aware of this problem and it has been escalated to our developers for a fix. In the meantime, we recommend using the previous version of the Advanced Translator. This should help retain the & character in your translations.
Please note that this solution might be outdated or not applicable to your specific 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.
Problem: If you're experiencing issues with WPML where translated text from English to Portuguese loses paragraph formatting and appears as a single block, making it difficult to read and maintain the intended structure, this is a known issue with the new Advanced Translation Editor. Solution: We recommend trying the workaround provided in the errata page: https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. If you prefer, you can switch back to the older Advanced Translation Editor without affecting your existing translations. After switching, you should manually resync the page by making minor edits and retranslating to ensure proper functioning of line breaks. This change will only affect new translations, and you can switch back to the new editor once the issue is resolved.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific 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 needed, please open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues with WPML not connecting to the server in a local environment and are concerned about performing updates due to this connectivity problem, here's what we recommend. Solution: First, ensure that there is nothing on your local host that could be blocking the communication between WPML and the server. This could include a local firewall. We suggest checking the WPML connection status by navigating to WPML → Support and clicking on Installer Support. Then, click on 'Check now' next to Installer System Status to see if all checkmarks are green. For more details, visit WPML Plugin Cannot Connect to WPML.org. If the issue persists, try manually registering WPML through your wp-config.php file using the
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your specific 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the WPML language switcher on their site. When switching to Arabic, the URL incorrectly shows /ar/fr instead of just /ar. Additionally, search results do not match the set language, always defaulting to Spanish. Solution: We have identified that the issue with the language switcher URL showing /ar/fr instead of /ar is due to a redirection that eventually leads to the correct /ar URL. This behavior suggests that the problem might not be directly related to WPML but could be due to a compatibility issue with another plugin. We recommend setting up a staging environment or providing a Duplicator package of your site so we can further investigate this issue in isolation from other plugins.
For the issues related to search results not appearing in the selected language, please open a separate support ticket with detailed examples so we can address this specifically.
If this solution does not resolve your issue or seems irrelevant, 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. Should the problem persist, please open a new support ticket.
Problem: The client is unable to download menus in languages other than the default in WordPress and is asking if there is an official solution to this issue. Solution: We informed the client that there is currently no official solution for downloading localized menus via WPML GraphQL. However, we have a feature request to implement this functionality in our WPML GraphQL Add-On. We also provided a link to a GitHub project that might be of help, with a disclaimer that it is not our project and we cannot guarantee its full functionality: https://github.com/rburgst/gatsby-source-wordpress-menus.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If this is the 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 you still need assistance, please open a new support ticket with us.
Problem: The client is trying to translate three child pages, but after translation, they all incorrectly have 'parent-a' as their parent instead of 'parent-b'. This issue occurs only in the secondary language. Solution: First, ensure you have a backup of your site. Then, we recommend trying the workaround suggested in a related support ticket, which you can find here: WPML support forum post. Additionally, navigate to WPML>>Settings and verify that the 'Posts and pages synchronization' options are enabled, especially the 'Set page parent for translation according to page parent of the original language' option.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. You can do so here: WPML support forum.
Problem: You are trying to re-register your website on WPML after it had been unregistered for some time. In the WPML support section of the WordPress backoffice, you keep receiving a message to prolong your account, despite having a lifetime account. Solution: First, please follow these steps: 1. Navigate to WP Dashboard Menu >> Updates. 2. Click the "Check again" link. 3. Go to Plugins >> Add New Plugin > Commercial tab and click on the “Check my order status” button (if available). If the issue persists, try the following steps: 1. Edit the 'wp-config.php' file in your WordPress installation. 2. Insert the following line of code right above the line that reads "/* That's all, stop editing! Happy publishing. */":
Make sure to replace 'your-site-key' with the actual site key from your wpml.org account. 3. Visit the Plugins >> Add New Plugin > Commercial tab again to see if the message has been resolved. For more detailed instructions, please visit: https://wpml.org/faq/automatic-wpml-registration-using-php-for-easy-moves-between-production-development-and-staging/ Additionally, ensure to add the newly generated site key in Plugins >> Add New Plugin > Commercial tab to store it in your site's database and avoid future issues.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 contact us through the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
