Problem: Sie hatten Probleme mit der Anzeige von englischen Übersetzungen in Ihrem Theme, die über die String Translation von WPML übersetzt wurden. Neue Übersetzungen wurden nicht auf der Webseite angezeigt, obwohl sie als "Übersetzung abgeschlossen" markiert waren. Solution: Das Problem entstand, weil Ihr Theme nicht nach WordPress-Standards erstellt wurde. Wir haben eine angepasste Version Ihres Themes erstellt, die dieses Problem beheben sollte.
Bitte beachten Sie, dass diese Lösung möglicherweise veraltet oder nicht auf Ihr spezifisches Problem anwendbar ist. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen.
Problem: Nach mehreren großen Updates werden die Übersetzungen des Themes nicht genutzt, obwohl sie in der WPML String Translation neu vorgenommen wurden. Das Problem besteht sowohl auf einer Staging- als auch auf einer Produktivumgebung. Solution: 1. Überprüfen Sie, ob das Custom Theme die WordPress Coding Standards einhält, insbesondere im Hinblick auf die Internationalisierung: https://developer.wordpress.org/themes/classic-themes/functionality/internationalization/ 2. Stellen Sie sicher, dass die Textdomain des Themes korrekt gesetzt ist und dem Theme-Slug entspricht. 3. Fügen Sie in der
functions.php
-Datei des Themes den erforderlichen Code hinzu, um die Text-Domain korrekt zu laden. Mehr Informationen dazu finden Sie hier: https://developer.wordpress.org/reference/functions/load_textdomain/ 4. Legen Sie eine deutsche Sprachdatei (POT) im Theme an, um sicherzustellen, dass benutzerdefinierte Sprachdateien von WPML geladen werden.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Überprüfen Sie auch die bekannten Probleme unter https://wpml.org/known-issues/, bestätigen Sie die Version der dauerhaften Lösung und stellen Sie sicher, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The client reported a possible compatibility issue between Divi 5.11.1 and WPML Multilingual CMS 4.9.7. When WPML is active, saving a Divi Theme Builder template removes the backslashes from Unicode escape sequences in Divi block data, affecting Dynamic Content and escaped HTML. Solution: The issue was traced back to a function in the client's child theme that aggressively replaced special characters, including backslashes in Unicode escape sequences. By deactivating the child theme, the problem disappeared. The client adjusted the function to correctly handle special characters without removing necessary backslashes, resolving the issue.
If you're experiencing a similar issue, we recommend checking if any custom functions in your theme or child theme might be altering content during the save process. If the problem persists, please visit our support forum for further assistance. 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: When duplicating a page into another language, it is set to published immediately, but you would like the duplicated page to be in drafts so that the country admins can finalize the new design. Solution: This behavior is expected because when a published page is duplicated into another language, all its information—including the published status—is copied. Unfortunately, the “Save translated posts as drafts” setting applies only to regular translations, not to pages created with the Duplicate option. There is no built-in WPML setting to make duplicated pages drafts automatically. A possible custom solution involves using the WordPress
wp_insert_post
action. This code would check if the new page has WPML’s
_icl_lang_duplicate_of
metadata and, if so, change its status to Draft. We recommend testing this on a staging environment first and adding it as a small custom plugin rather than directly to the theme. As a manual workaround, you can temporarily change the original page to Draft before duplication. After duplicating, select “Translate independently” on the new language page, then republish the original page. However, the custom-code approach would provide a smoother workflow for country administrators.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the Italian language switcher and directory URL on a bilingual WordPress site using WPML. When switching to Italian, the site either redirects back to the English version or fails to maintain the Italian language across different pages. Additionally, the Italian version's layout changes, and hero images do not appear.
Solution: We recommend the following steps to resolve the issues: 1. Enable WPML > Language > Language URL format: Different languages in directories. 2. Re-save the permalink settings in WordPress. 3. In your custom code, use the
wpml_object_id
hook to ensure WPML loads the correct attachment ID in the second language. This involves modifying the code to include translated IDs and ensure media files display correctly across languages. 4. Disable the option "Automatically detect best options for translating image texts (alt, caption, title)" in WPML > Settings > Media Translation and set up manually. Ensure all checkboxes are marked and start the process to update media entries in the media library.
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. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: Si estás intentando traducir un custom post type llamado 'services' y no ves la opción de idiomas en el panel de control general, es probable que un plugin del tema esté sobrescribiendo las columnas de los listados sin utilizar las funciones normales de WordPress. Solution: Para resolver este problema, puedes agregar el siguiente código en el archivo
functions.php
de tu tema para restaurar la columna de idiomas de WPML:
Si esta solución no resuelve completamente tu problema o si la información proporcionada se ha vuelto obsoleta, 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. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: Sie haben festgestellt, dass trotz korrekter Übersetzung und Speicherung in WPML → String Translation, die Übersetzungen für neu hinzugefügte Strings eines selbst entwickelten WordPress-Plugins nicht angezeigt werden. Die Strings werden im Plugin als fest hinterlegte Strings in einem Array definiert und nicht über gettext()-Aufrufe ausgegeben. Solution: Das Problem liegt darin, dass WPML nur Strings übersetzen kann, die über gettext() oder andere WordPress-Übersetzungsfunktionen registriert werden. Um dieses Problem zu beheben, müssen Sie sicherstellen, dass die Strings im Plugin über gettext()-Aufrufe ausgegeben werden. Dies ermöglicht es WPML, die Übersetzungen korrekt anzuwenden.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, 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.
Problem: The client needs to configure WPML in a WordPress installation running on a two-server web farm with different internal and external environments, using dynamic site URLs defined in wp-config.php. Solution: If all domains share the same database, we recommend using the Alias Domain feature in WPML > Support > Troubleshooting to connect with AMS and share the translation among them. Additionally, use site key constants generated for each domain and applied based on the current domain. For more details on setting this up, please refer to our documentation on automatic WPML registration using PHP.
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 at WPML support forum.
Problem: The client is developing an importer to create multilingual WooCommerce variable products using the WooCommerce REST API along with WPML. They aim to replicate the database structure and behavior of products created manually through WooCommerce + WPML. The main issue is that while the backend shows translated attribute labels correctly, the frontend still displays them in English instead of the respective translations (French or Spanish).
Solution: We identified that the issue was due to the way translations were being handled and displayed. To resolve this, we updated the WPML Import Helper plugin on the sandbox. Changes include: - Added a WooCommerce custom attribute label fallback. - Uses translated product
_product_attributes
as the label source. - Added safe product cache refresh helper. - Updated the attribute import endpoints. - Disabled direct WPML package update endpoint. - Adapted translation connection to rely on WPML hooks. The client should follow specific steps for importing products and linking translations, which involve creating products and variations in the default and translated languages, then linking and rewriting translated product attributes through specific API endpoints. It would be even better using global product attributes if the products are created by WC REST API requests.
If the solution provided here 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 issues persist, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with shipping method labels displaying in the wrong language during the initial page load on a WooCommerce Multilingual & Multicurrency store, but updating correctly after entering a postcode, this might be due to interference from other plugins, themes, or caching layers.
Solution: We recommend setting up a staging site with only the essential plugins (WPML, WooCommerce, WCML) and a default WordPress theme. Ensure all caching layers are disabled. If the problem persists in this clean environment, it indicates a potential compatibility issue or a need for further investigation by our developers. Additionally, compare how shipping method labels are generated on the initial load versus after the checkout update, focusing on any custom code that might affect shipping rates or labels.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, 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 for further assistance at WPML support forum.
Problem: The client is using WordPress 7.0.1 and WPML Multilingual CMS 4.9.5 with a custom block theme. They are attempting to programmatically connect a newly created English translation page to a German page using
wpml_set_element_language_details
and
$sitepress->set_element_language_details()
. However, WPML does not apply the relation, and the new page remains registered as German with a separate TRID.
Solution: We recommend ensuring the following: 1. Include
element_id
in the arguments array when calling
wpml_set_element_language_details
. This parameter is required for the action to work. 2. Ensure the action is hooked to
init
or a later action. If it fires before WPML registers its listener, the action will not be applied. 3. Avoid any save operations like
wp_update_post()
after setting the language details, as they might overwrite the settings. 4. Do not hardcode the TRID. Retrieve it at runtime from the German page using
wpml_element_language_details
.
For more information, please refer to the documentation:
If these steps do not resolve the 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing synchronization issues between WooCommerce and Unleashed inventory management software after making their website multilingual with WPML. The issue arises because the WooCommerce REST API, by default, returns products in a single language, causing issues with product mapping in Unleashed.
Solution: 1. We recommend appending
?lang=all
to the WooCommerce REST API URL in the Unleashed integration settings to fetch products in all languages. If Unleashed does not allow direct URL modification, look for a field where custom query parameters can be added.
2. If Unleashed cannot modify the URL, and since it queries products by SKU which can return multiple records for translated products, we suggest adding a code snippet to force the WooCommerce REST API to return products only in the default language. Add the following code to your child theme's functions.php file or a custom plugin:
3. If synchronization errors persist, particularly with products originally created in different languages, replace the above code with a snippet that ensures the REST API only returns original (source) products, excluding translations. This approach helps maintain consistent product IDs across different language versions.
Despite these adjustments, if issues continue, we recommend consulting with a developer to customize the REST API behavior further to meet specific integration needs with Unleashed. Additionally, ensure that all products are correctly mapped in Unleashed to their corresponding WooCommerce IDs.
Please note that the solution might be outdated or not applicable to your specific case. If these steps do not resolve the issue, 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.