Problem: You are using WPML to translate articles on your website and have switched to the Pay-as-you-go plan. After reaching the €100 limit, the translation stops, and you receive an 'Insufficient funds' message. Solution: If you're experiencing this issue, it's important to understand that there are two safety limits in place when using the Pay-as-you-go plan. These limits are set at $100 and $4,000 to prevent accidental overspending and protect against fraud. Once you reach the first limit of $100, you will be prompted to make a payment before you can continue translating. The amount you pay will then be deducted from your monthly invoice. To check for any open amounts and make a payment, please visit your WPML account.
If this solution does not apply to your situation, or if it seems outdated, we highly recommend checking the related 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.
Problema: El cliente está intentando configurar su sitio web con el idioma principal en Español y el idioma secundario en Catalán. Ha notado que las URL canónicas del apartado de servicios apuntan hacia la versión en Catalán (/ca) y desea que la canónica sea la versión en Español. Solución: Hemos revisado la página en ambos idiomas y confirmado que las URL canónicas están configuradas correctamente, apuntando a sí mismas en cada idioma, como es esperado. Los atributos
hreflang
y
x-default
también están correctamente implementados. Las URL canónicas deben apuntar a la propia página en su respectivo idioma para evitar contenido duplicado en los motores de búsqueda, no es necesario que apunten a otra versión en otro idioma.
Si esta solución no resuelve tu problema o si la información parece desactualizada o no aplicable a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
The client needed editors on their WordPress site to be able to translate their own posts and edit the translations of any other posts using WPML. The editors were encountering a pop-up indicating that they didn't have the necessary permissions to use WPML on posts they initiate.
Solution:
We recommended that the client should assign the editor as both a Translation Manager and Translator under WPML>>Translation Management>>Translator tab. This setup would allow the editor to translate their posts and manage translations of posts initiated by others.
For detailed guidance on setting up and understanding the capabilities of different WPML roles, we advised checking the following documentation:
If this solution does not resolve your issue or 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where some elements in the WordPress admin area are displayed in Serbian instead of English, despite the user's language being set to English. Solution: 1) We recommend checking if the issue persists in a minimal environment. Please follow these steps: - Deactivate all plugins except for WPML CMS and String Translation. - Switch to a default WordPress theme, such as Twenty Twenty-One. - If the issue resolves, reactivate the plugins one by one to identify the one causing the issue. Please ensure to back up your database before performing these tests. 2) After the above test, the problem was caused by the "WP Data Access Premium" plugin.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues where repeater field rows disappear in translations when the source language of a post is updated, this might be due to the translation settings of your fields. Specifically, if the field settings were changed from 'Copy once' to 'Translate' in WPML, updates to the original post require retranslation to maintain the repeater fields in the translated versions. Solution: We recommend using the 'minor edit' option when updating posts that have been translated. This approach helps in preventing the disappearance of repeater fields in translations when the source post is updated. If the translation still does not reflect the changes correctly, you may need to manually update the translation through WPML's Advanced Translation Editor (ATE) or adjust the field's translation preference settings back to their original state if feasible.
Please note that this solution might not be applicable if it's outdated or not relevant 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: You are using WPML to translate your website and are experiencing issues with the Arabic and Hebrew languages. The related product slider works fine in English but breaks when switching to Arabic or Hebrew. The issue persists even after disabling all plugins, including WPML, leading you to suspect an incompatibility between WPML and the mini cart or the theme. Solution: Since the problem occurs even when WPML is disabled, it suggests that the issue is not related to WPML. We recommend contacting the theme support to investigate further, as the issue might be related to theme compatibility with RTL (Right-to-Left) and LTR (Left-to-Right) languages. Show them that the issue happens without any additional plugins and ask for their assistance.
If this solution does not resolve your issue or seems irrelevant due to 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 at WPML support forum for further assistance.
Problem: The client updated to RankMath Pro and noticed that in RankMath Analytics, the Keywords tab only shows keywords for the Dutch version of the site and not for the German and English versions. Solution: We explained that this behavior is expected because the section displays keywords based on popularity, regardless of the keyword language or the destination URL. All data comes from the same Google Search Console tag, tracked under a single website property. To find keywords for specific language versions, use the "Search Post URL" bar at the top and paste the URL of the desired language version. Additionally, it's important to understand that Google customizes search results based on factors like browser language and search history, which can affect which keywords and pages appear in searches.
If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.
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.
Problem: El cliente ha traducido las cadenas de meses y días de la semana del inglés al español y al euskera para el core de WordPress, pero estas cadenas siguen apareciendo en inglés cuando selecciona el idioma euskera. Solution: 1. Verificamos la URL proporcionada y confirmamos que todas las cadenas se muestran traducidas correctamente. Sugerimos al cliente verificar si el problema persiste cuando no está autenticado en el sitio. 2. Recomendamos incrementar el límite de memoria de WordPress a un mínimo de 128Mb para mejorar el rendimiento y la gestión de traducciones. Esto se puede hacer añadiendo el siguiente código en el archivo
Este código debe colocarse encima de la línea /* That's all, stop editing! Happy blogging. */. Puede verificar el límite de memoria actual en WPML -> Soporte.
Si esta solución no resuelve el problema o si parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Проблема: Клиент использует зарегистрированные версии W3 Total Cache и WPML и пытается использовать конвертированные в WebP изображения, которые не заменяют имеющиеся PNG изображения на сайте. Решение: Мы подтвердили, что WPML совместим с W3 Total Cache и не должен вызывать описанную проблему. Рекомендуем обратиться в службу поддержки W3 Total Cache для получения более точного разъяснения и решения. Если выяснится, что проблема связана с WPML, просим сообщить нам для дальнейшей помощи.
Данная проблема проблема была связана с хостингом. Необходимо было отключить обработку статики на уровне nginx.
Мы настоятельно рекомендуем проверить список известных проблем, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов. Если проблема сохраняется, пожалуйста, откройте новый тикет поддержки.