Problem: After installing WPML and activating automatic translations from French to English and Spanish, the client encountered issues with the language switcher module not displaying correct pages and English-translated text widgets showing 'widget body' followed by a serial number instead of the translated text.
Solution:
There was another temporary issue in client's site which they fixed and it resolved the said issue.
We recommended checking for conflicts with other translation plugins, as this was identified as the cause of the issue. Additionally, we advised following our Elementor tutorial, particularly the sections on templates and widgets, which could potentially resolve the described problems.
If this solution does not apply to your situation, 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. Should these steps not resolve your issue, please do not hesitate to open a new support ticket with us for further assistance.
Problem: If you're experiencing issues where text widgets do not display translated content in English and instead show 'widget body' followed by a serial number, while other languages like Spanish work fine, this might be due to a conflict with another plugin. Solution: We recommend checking if you have another multilingual plugin activated, such as TranslatePress. If so, deactivate the other multilingual plugin. In this specific case, deactivating the 'TranslatePress - Multilingual' plugin resolved the issue. It's important not to activate two multilingual plugins at the same time as they can conflict with each other.
If this solution does not apply to your case, or if it seems outdated, 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. For further assistance, you can contact us directly through our support forum at WPML support forum.
Problem: You are translating a site from German to English and encounter an issue where Consent messages in Everest Forms do not appear in the string translation.
Alternatively, client changed the Consent fields to a Checkbox field and this now appears in the String translation.
If the solution provided here becomes irrelevant due to updates or if it does not apply to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client reported an issue with the Croatian version of a WooCommerce product page showing an ERR_TOO_MANY_REDIRECTS error and having a URL with double slashes. Additionally, the featured image and attribute images were not displaying on the translated product page.
Solution: We advised the client to first take a full backup of their site and database. The steps included: 1) Checking in String Translation for the problematic URL and correcting it for the Croatian translation. We also suggested running the process to scan and auto-adjust links under WPML -> Settings -> Translate link targets. 2) Deactivating all plugins except for WPML, String Translation, WooCommerce, and WCML to check if the issue persists. 3) Switching to a standard theme like 2024 or 2021 to rule out theme-related issues. 4) Re-activating plugins one by one to identify any conflicts, and then switching back to the original theme to check for issues.
Alternatively, client found that plugin SEO press was causing the url to look like this, resetting the plugin fixed the issue.
If these steps do not resolve the issue or if the solution seems outdated or 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. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Problema: El cliente ha creado varias páginas y sus traducciones en su sitio usando el módulo de banderas para Elementor. Mientras que las banderas de las traducciones aparecen cuando está logueado, algunas no se muestran cuando no lo está, a pesar de que las páginas están traducidas. Solución: Primero, verificamos que no hubiera idiomas ocultos y que el contenido traducido estuviera publicado. Luego, identificamos que algunas traducciones de la página 'En la retina' estaban en modo borrador. Publicar estas traducciones solucionó el problema de visualización de las banderas en el frontend. Además, sugerimos utilizar el shortcode del selector de idiomas de WPML para asegurar la correcta funcionalidad del módulo de banderas. Para más detalles sobre cómo agregar selectores de idiomas, visite esta documentación.
Si esta solución no resuelve su problema o si la información parece desactualizada, le recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tiene instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visite nuestro foro de soporte.
Problem: The client reported that the English version of their WooCommerce shop page was displaying fewer products compared to the Bulgarian version, despite both versions being set to automatically translate. Solution: We discovered that the issue was related to the WooCommerce Wholesale Prices Premium plugin. We recommended deactivating and then reactivating the plugin, which resolved the problem. Additionally, we advised the client to check and publish any English products that were still in draft status.
Please note that this solution might be outdated or not applicable to your specific 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is trying to use WPML's Advanced Translation Editor and Automatic Translations for translating content from English to French, but not from English to Canadian English. They are concerned that the Advanced Translation Editor might automatically translate English (Canada), which is mapped to the default language of the site and should not be auto-translated according to WPML documentation. Solution: We advised the client to manually control the translation process to avoid automatic translation for English (Canada). This can be achieved by: 1. Activating the option in WPML -> Settings to control which content is sent for automatic translation. 2. Using the WPML -> Translation Management to filter content by the original language (English) and manually sending it for automatic translation in French. For English (Canada), since automatic translation is not supported due to its mapping to the default site language, it is not necessary to map it for automatic translation unless desired by the client.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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. If further assistance is needed, please open a new support ticket.
Problem: The client is trying to translate the message 'No products in the cart.' displayed in the mini cart top menu icon when the cart is empty. Although the string is translated in String Translation, it still appears in English on the live site.
Solution: We recommend checking if the issue persists when only WPML, String Translation, and Elementor are active, and all other plugins are deactivated. This step helps in identifying if any other plugin is causing a conflict that prevents the translation from displaying correctly. Before proceeding, ensure to back up your website and database completely. It's advisable to perform these checks on a staging or development site to avoid affecting the live site.
If after these steps the translation still does not appear, or if this solution seems outdated or not applicable to your case, please visit our support forum to open a new 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 is experiencing issues when trying to translate English pages into Arabic on their website. Specifically, when clicking the plus button to add translations, some pages appear as new instead of translations. Solution:
Client fount that the translator for those pages was set to use WordPress Editor instead of WPML, so changing it back to WPML editor fixed the issue.
If these steps do not resolve the issue, the 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client created a Gravity Form using the Gravity Forms Survey Add-On plugin and encountered an issue where the form sends all data correctly in English via email, but not in Arabic. When the form is submitted in Arabic, the data is not being sent in the emails.
Solution: We first verified that the issue was not related to email content being different between languages by using the "Log Emails" plugin. Both English and Arabic emails had the same content, and form entries were created correctly in both languages. We then identified that the Gravity Form had not been translated, and the notification emails were missing the
{all_fields}
tag. To resolve this: 1. We translated the Gravity Form and added the
{all_fields}
tag to the existing notifications. 2. We added another notification with the
{all_fields}
tag for testing. 3. We created a new test page, added the form, and translated this page as well. After these adjustments, the form submitted correctly in both languages, and the received emails contained all the information in the respective languages. However, there was a note that the HTML formatted email had a design problem, which is not related to WPML but may affect how content is displayed.
If this solution does not resolve your issue or seems outdated, we 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. If problems persist, please open a new support ticket.
Problem: The client is unable to switch from the Dutch version to the French version on the homepage of their multilingual site using the WPML language switcher. The switcher works on other pages but not on the Dutch homepage. Solution: We recommend trying the following steps to identify and resolve the issue: 1. Deactivate all plugins except for WPML CMS. 2. Temporarily switch to a default WordPress theme, such as Twenty Twenty-One. 3. Check if the language switcher issue on the homepage is resolved. Please ensure to back up your database before performing these steps. The issue was caused by the cache in the "Object Cache Pro" plugin.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and check for any related issues. Also, verify that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.