Problem: The client has a staging site with languages configured for English and Icelandic. A button in the header links to the English site's shop, but when switching to Icelandic, the link incorrectly redirects to the production site's shop instead of the staging Icelandic version. Solution: We recommend checking if the button was added using the Theme's Customizer at Appearance → Customize → Header Builder. If this is the case, the URL and button text should be translatable via WPML > String Translation. It's important to ensure that these strings are registered and correctly translated to reflect the appropriate staging URLs for each language.
If this solution does not resolve the 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After migrating the server and restoring the backup using the all-in-one WP Migration plugin and re-registering WPML, the client encountered the 'WPML didn't manage to translate this page' problem and an installer support error. Solution: We recommend ensuring that the following domains are whitelisted on your server or firewall:
wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net
Additionally, check if a third-party plugin might be affecting this behavior by temporarily disabling all plugins except WPML and testing this using a default WordPress theme. Before performing any of these actions, please make sure to create a full backup of your site. If the issue persists, please check with your hosting provider to ensure that outgoing connections are not being blocked, which could be caused by firewall rules, security policies, or other server-side restrictions.
This solution might be irrelevant if it's 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 continues, please open a new support ticket at WPML support forum.
Problema: El cliente desea recuperar su dinero. Solución: Si estás experimentando esta situación, te recomendamos que sigas los pasos para solicitar un reembolso completo, siempre y cuando estés dentro de los 30 días posteriores a la compra. Puedes revisar los detalles y procedimientos en el siguiente enlace: Política de reembolso de WPML.
Si esta solución no es relevante para ti porque la información está desactualizada o simplemente no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos en problemas conocidos de WPML, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Problem: The client is facing an issue where unique HubSpot forms added to contact pages in different languages are overwritten by WPML each time translations are updated. Solution: We recommend using the WordPress Editor to manage the content of the pages where unique forms are required, as the WPML Editor and the WordPress Editor are independent. Content created with one cannot be edited with the other. You should set the WordPress Editor on a page/post level basis, for a post type, or for the entire website, specifically for pages that need different designs or custom HTML per language. It is crucial to have a backup before testing any settings.
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.
Problema: Si estás experimentando problemas con la sincronización de enlaces personalizados en tu menú principal que no se actualizan o graban correctamente en los idiomas español e inglés, y estos enlaces pertenecen a las secciones 'About the lab' e 'Initiatives'. Solución: Para resolver este problema, necesitas añadir las traducciones de todos los elementos de menú en WPML > String Translation. Aquí te proporcionamos los pasos a seguir: 1. Accede a la sección de String Translation de WPML. 2. Añade las traducciones para los elementos de menú en las siguientes áreas:
Después de añadir las traducciones, podrás sincronizar los menús correctamente.
Es posible que esta solución pueda ser irrelevante si ya está desactualizada o no se aplica a tu caso. Te recomendamos 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. Si el problema persiste, te sugerimos abrir un nuevo ticket de soporte en nuestro foro de soporte.
Problem: You are looking for a simple method to translate a Divi page, specifically asking if you can export the content into some table, translate it, and then import it back into the Divi builder. Solution: We recommend using the XLIFF export/import functionality. This allows you to export the page content into a translation file, translate it using a translation tool or by sending it to a translator, and then import it back. WPML will automatically apply the translated content to the correct page and maintain the connection with the original. You can find more information on configuring XLIFF file options here: https://wpml.org/documentation/translating-your-contents/using-desktop-cat-tools/configuring-xliff-file-options/ Divi also offers an export/import functionality for page layouts. However, after re-importing, the page will typically be in the default language. You would need to manually set the language and connect it to the correct translation in WPML.
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. If further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client wants to configure the WPML language switcher to appear as a simple icon in the header, similar to the design used by Weglot, with specific features such as a small flag icon with the language abbreviation, visible directly in the header, and a dropdown menu that appears on hover without requiring a click. Solution: We recommend using the manual mode for customizing the WPML language switcher. This mode allows for specific design adjustments that are not typically available through standard WPML settings. For detailed guidance on implementing manual mode, please refer to our documentation: Using Different Translation Editors for Different Pages.
If this solution does not fully address your needs, or if it 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. Should you require further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is working on a multilingual project using ACF Options Pages and is facing issues with translating them. They want each language version of the ACF Options Pages to behave like regular posts in WPML, with each having its own version and linked as translations of each other without affecting the content of another language when one is saved.
Solution: We explained that ACF Options Pages behave differently with WPML and cannot be edited directly via the WordPress admin editor. The correct process involves: 1. Setting up the options page in ACF. 2. Populating the values via WordPress admin. 3. Translating the page via WPML > Translation Dashboard. For more detailed guidance, we recommend checking the documentation on translating sites built with ACF, specifically for ACF Options Pages at https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#acf-options-pages.
If this solution does not resolve your issue or 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 the WPML support forum.
Проблема: Клиент хочет включить создание версии на русском языке для кастомного типа записи togo_trip. Решение: 1. Перейдите в WPML → Settings → Post Types Translation. 2. Найдите тип записи togo_trip. 3. Установите для него опцию Translatable – only show translated items. 4. Сохраните изменения. После этих шагов записи данного типа можно будет корректно переводить и отображать на соответствующих языках. Подробнее об этом можно прочитать в нашей документации: https://wpml.org/documentation/getting-started-guide/translating-custom-posts/
Если данное решение окажется неактуальным или не подходит под ваш случай, мы рекомендуем открыть новый тикет поддержки. Также рекомендуем проверить связанные известные проблемы на https://wpml.org/known-issues/, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problem: You are using WPML with WooCommerce, Elementor, and the XStore theme and want to translate product category names into Arabic while keeping the products only in English. However, when you translate a product category into Arabic, it shows 0 products in the category carousel on the Arabic version of the site. Solution: First, ensure that you have translated all product categories by creating a dummy product, assigning all categories to it, and sending it for translation. For more details, visit https://wpml.org/faq/how-to-translate-all-taxonomy-terms-at-once/.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client translated the footer template using Elementor into Italian and Spanish, but the English version continued to display on the multilingual site. Additionally, the flags for language switching were not appearing on the menu. Solution: We identified that the issue was due to the same Elementor template ID being used across all languages, which was stored in the Customizer setting (footer_template). To fix this, we: 1. Went to WPML → String Translation → Admin Texts and searched for the default language Elementor template ID (589), then added this option for translation. 2. Returned to String Translation and set the ID of the translated Elementor template for the secondary language. This adjustment allowed WPML to load the correct footer template for each language. For further guidance on translating theme options, you can visit our documentation here: https://wpml.org/documentation/getting-started-guide/string-translation/how-to-translate-theme-options/
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 at WPML support forum.
Problem: Nach der Migration der Website von mugarecycling.com zu muga.ch können einige Seiten wie 'Impressum' und 'Aktuell' nicht übersetzt werden. Es erscheinen Fehlermeldungen, dass WPML die Seite dreimal zu übersetzen versucht hat und gescheitert ist, sowie kritische Fehler aufgrund von Speicherproblemen. Solution: 1. Wenn ein Übersetzungsauftrag vor der Migration noch in Bearbeitung war, sollten Sie den originalen Inhalt bearbeiten, die Seite erneut speichern und dann die Übersetzung durchführen. Sollte dies nicht helfen, brechen Sie den aktuellen Auftrag ab und beginnen Sie erneut. Weitere Informationen finden Sie hier: https://wpml.org/de/faq/translation-status-stuck-or-displaying-the-error-wpml-didnt-manage-to-translate-this-page/ 2. Erhöhen Sie das PHP MEMORY LIMIT auf Ihrem Server und in der WordPress-Konfiguration auf mindestens 256M, um Speicherprobleme zu vermeiden.
3. Fügen Sie folgende Zeilen in Ihre wp-config.php ein, um auch das WP MEMORY LIMIT zu erhöhen:
Überprüfen Sie die aktuellen Werte unter WPML > Support.
Falls diese Lösungen Ihr Problem nicht beheben oder nicht zutreffen, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: WPML Support-Forum.
Problem: Der Kunde möchte, dass die übersetzten Seiten im Avada Theme die gleiche Formatierung wie die Originalseiten behalten. Es gibt Probleme mit der automatischen Umformatierung und der Definition des originalen Inhalts. Solution: 1. Um die Theme-Optionen für alle Sprachen gleichzeitig zu setzen, sollte man in den Avada-Theme-Optionen die Sprache in der oberen Admin-Leiste auf "Alle Sprachen" umstellen. Weitere Informationen finden Sie hier: Wie man Theme-Optionen für Sprachen in Avada setzt. 2. Um den deutschen Inhalt als Original zu definieren und die Formatierung zu behalten, muss eine Anpassung vorgenommen werden, nachdem eine Sicherungskopie der Website erstellt wurde. Danach kann der Inhalt im WPML-Übersetzungseditor neu übersetzt werden. 3. Um bereits übersetzte Seiten zu verbinden oder die Verbindung aufzuheben und neu zu definieren, welche Sprache die Ausgangssprache sein soll, folgen Sie dieser Anleitung: Wie man bereits übersetzte Seiten verbindet.
Falls diese Lösungen veraltet sind oder nicht auf Ihr Problem zutreffen, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Überprüfen Sie auch die bekannten Probleme, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
