Problem: The client is unable to change the language using the header language switcher on their website. Solution: We recommend recreating the header language switcher. You can follow the step-by-step method described in the WPML documentation on setting up language switcher options. Please visit Language Switcher Options for detailed instructions.
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. Should you need further assistance, please do not hesitate to 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.
Problema: El cliente necesita ayuda para ingresar el código de migración en el sitio WPML para conectar sus sitios y compartir créditos de traducción automática. Solución: 1. Accede al área de administración de WordPress en el sitio que deseas conectar. 2. Navega a WPML → Translation Dashboard y haz clic en la pestaña Herramientas (Tools). 3. Despliega la sección Sitios conectados (Connected Sites). 4. Haz clic en Ingresar la clave de conexión de otro sitio. Si necesitas más detalles sobre cómo conectar los sitios correctamente, por favor sigue los pasos descritos en esta guía: https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/.
Si esta solución no resuelve tu problema o si la información parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos 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 los temas y plugins. Para más asistencia, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: The client experienced an issue where the translated page content reverted back to English after some updates, despite using both WPML and Elementor for page editing. This problem occurred when the client updated the text for the current language and then noticed that the text of the translated page reverted back to English after some time. Solution: We recommended the client to ensure that the manual translation option in WPML was enabled as described in this documentation. Additionally, it was crucial to verify that all WPML plugins were up-to-date. The client updated from version 4.7.1 to 4.8.2, which resolved the issue. We advised checking for updates via Dashboard → Plugins → Add New → Commercial tab, then clicking “Check for updates” and updating all WPML-related plugins.
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 the issue persists, please open a new support ticket.
Problème : Vous rencontrez des problèmes avec la traduction automatique de votre site du français vers l'anglais, où les liens internes restent en français malgré l'utilisation de la fonctionnalité 'Traduire les cibles de lien' dans WPML > Paramètres. De plus, les taxonomies telles que 'produit' pour les pages produits WooCommerce ne se traduisent pas correctement en 'product'. Solution : Nous avons résolu le problème en supprimant et en réajoutant le slug pour les taxonomies et les liens internes. Cela devrait normalement corriger l'erreur de traduction des liens et des taxonomies sur votre site. Si vous continuez à rencontrer des problèmes, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support. Nous vous recommandons également de consulter notre forum de support pour une assistance supplémentaire : Forum de support WPML.
Problem: You are experiencing an issue where transactional emails from WooCommerce are not fully translated when sent. The email subject line is translated correctly, but the content remains partially in French or shows only some translated shortcodes. Solution: We recommend comparing the steps you have followed to translate the emails with the guidelines provided in our documentation. Please visit How to Translate WooCommerce Emails and ensure all steps are correctly implemented. If the problem persists after following these steps, it might be due to an outdated solution or a different issue not covered here. 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 here.
Problem: The client is unable to access the glossary feature in WPML when using Microsoft Translator or Google Translate as their translation engines. They receive a message stating that the glossary isn't supported with Microsoft Translator and are given an option to switch to PTC.
Solution: We explained that the glossary feature in WPML is only supported by PTC (Private Translation Cloud) and DeepL translation engines. Microsoft Translator and Google Translate do not support glossary integration due to technical limitations. To access and manage the glossary, the client needs to switch their translation engine to PTC or DeepL by following these steps: 1. Navigate to WPML → Settings in the WordPress dashboard. 2. Locate the Automatic Translation section. 3. Select PTC as the main translation engine. 4. Save the changes. After switching to PTC, the Glossary tab will become accessible, allowing the client to view, edit, and manage glossary entries. If the client wishes to revert to Microsoft Translator for other reasons, they can switch back after managing the glossary, but the glossary entries will only affect translations made with PTC or DeepL.
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.
Problem: You are using WPML with WooCommerce and other plugins, managing a multilingual site with German as the default language and English and Spanish as secondary languages. You have 22,000 products, each with 5 images across 3 languages, resulting in 330,000 images. This large number of duplicated images for each language is consuming 90% of your disk storage. Solution: 1. To prevent duplicating product images for translations, ensure the 'Automatically detect best options for translating image texts' option is enabled in WPML. This setting allows WPML to decide how to handle image metadata based on the image's usage context: - If the image text is stored within the content (e.g., Gutenberg blocks or WooCommerce product images), WPML translates it directly without duplication. - If the image text is sourced from the Media Library (e.g., Elementor or Divi Gallery), WPML duplicates the media text only when necessary. This approach ensures translations are accurate without creating unnecessary database entries. 2. With this option enabled, images are not duplicated in the database; translated products will display the correct images using the same file across all languages, with only the metadata (alt text, title, etc.) being translated.
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 WPML Support Forum.
Problem: You are trying to ensure that the translated pages on your site use the same template as the English version after installing WPML. However, the translated pages do not use the same template as the English ones, and you are unable to change the template for them. Solution: The issue is likely related to how Elementor templates and WPML translations are linked. Here’s how you can ensure your translated pages use the same (or a translated) template: 1. Go to Templates → Theme Builder in your WordPress dashboard while in the default (English) language. 2. Locate the template used for your English pages. Ensure it’s assigned with the proper Display Conditions. 3. Switch to your secondary language using the language switcher in the top admin bar. 4. Go back to Templates → Theme Builder and click Add New to create a template for the secondary language. Design it as needed, then publish it, but do not set Display Conditions for this template. 5. Switch back to the default language, return to Templates, and edit your original (English) template. 6. In the right sidebar, find the Language box and click Connect with translations. Select or search for the new template you just created in the secondary language and assign it. If you’re unable to change the template for translated pages, it’s usually because the templates aren’t linked across languages, or Display Conditions are set incorrectly for the secondary language template. Ensure only the default language template has Display Conditions set.
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 the problem persists, please open a new support ticket.
Problem: El cliente está intentando quitar el selector del idioma del menú de WordPress en su sitio web y no ha encontrado documentación que le ayude. Solution: Si estás experimentando este problema, te recomendamos seguir los pasos que se encuentran en nuestra guía de configuración del intercambiador de idiomas. Puedes acceder a la guía aquí: Configuración del intercambiador de idiomas. Para quitar el selector de idiomas del menú, sigue estos pasos: 1. Ve a WPML -> Idiomas. 2. Accede a la sección del selector de idiomas en el menú. 3. Elimina el selector de idiomas.
Si esta solución no resuelve tu problema o parece no ser relevante debido a que está desactualizada o no se aplica a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos, 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.
Problem: Sie möchten den Sprachumschalter im Header Ihrer Website anpassen, um die Sprachen nur mit Flaggen nebeneinander anzuzeigen, statt in einem Pulldown-Menü. Solution: Wir empfehlen Ihnen, die Einstellungen im Flatsome Theme zu überprüfen, da es sich nicht um eine Funktion des WPML-Sprachumschalters handelt, der ein spezifisches Markup verwendet. Sie können verschiedene Optionen für die Anzeige des Sprachumschalters in Abhängigkeit von Ihrem Theme und Ihren persönlichen Präferenzen finden. Weitere Informationen und Anleitungen zur Einrichtung finden Sie hier: WPML-Dokumentation zum Hinzufügen von Sprachumschaltern.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The client needs to translate internal links from the start page to product pages and the menu label 'Produkter' to 'Products' on their site using WPML with WP Bakery. The internal links are not translating to English, and the Swedish URL remains. Solution: 1. Ensure that the internal links in WP Bakery blocks use relative URLs (e.g., /products/) instead of absolute URLs (e.g., https://www.hinnagard.se/products/). WPML can only auto-translate internal links if they use relative URLs. 2. Edit the homepage in the default language and update the URLs in each WP Bakery module to use relative paths. 3. To address the issue with the menu label translation, update English menu labels through WPML → WP Menus Sync and String Translation. 4. If the WP Bakery elements are not fully registered for translation, follow the guide on how to register page builder content for translation at https://wpml.org/documentation/support/language-configuration-files/register-page-builder-content-for-translation/.
If these steps do not resolve your issue, or if the solution seems 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 needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client is using a multisite installation dedicated to WooCommerce and encountered an issue with the String Translation table, which could potentially become critical in the future. Solution: We suggested that the client first try translating a string on their site to check if the String Translation table is functioning correctly. If the problem persists, we recommended cloning the site to another staging environment for further troubleshooting.
If this solution does not resolve your issue, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
