Problem: The client is experiencing issues with string translations not working as expected on their Events Calendar Page when translating from English to French. Specifically, translations revert back to English after the time expires or when the option 'Look for strings while pages are rendered' is disabled. Additionally, WP_DEBUG logs indicate that translation loading for several domains was triggered too early. Solution: We recommend enabling WP DEBUG to identify any relevant errors. This issue may not be directly related to WPML but could be due to how the theme or plugins handle text domains following recent updates in WordPress 6.7. Here are the steps to follow: 1. Enable WP DEBUG by following the instructions here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ 2. Check for errors similar to those described in the WPML errata here: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 3. Contact the support teams of the affected plugins for updates on resolving these issues. If these steps do not resolve the issue or if you need further assistance, 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.
Problem: The client was trying to translate a WooCommerce product for Event Ticket Plus from English into German. However, not all products were displayed when switching to the German version. Specifically, several event tickets were missing on the German page. Solution: We first verified that all tickets were visible on the original page and then asked the client to ensure that all translated tickets were published. We also requested access credentials to double-check the configuration and ensure that there were no issues with the translation settings or visibility of the products in the German version.
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. If the problem persists, please open a new support ticket.
Problem: Клиент хочет, чтобы по умолчанию сайт открывался на украинском языке (https://site.com.ua/uk/), а при смене языка на русский отображался основной домен (https://site.com.ua/). Solution: Мы рекомендуем следующие шаги: 1. Смените язык сайта по умолчанию на украинский в настройках WPML → Languages. Таким образом, украинская версия сайта будет доступна по адресу https://site.com.ua/, а русская - по https://site.com.ua/ru/. 2. Активируйте языковой каталог для языка по умолчанию, чтобы украинская версия сайта была доступна по адресу https://site.com.ua/uk/, а русская - по https://site.com.ua/ru/. Для более подробной информации посетите документацию WPML.
Если данное решение не актуально или не подходит под ваш случай, мы рекомендуем открыть новый тикет поддержки. Также рекомендуем проверить известные проблемы, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problem: You are developing a site with a custom post type (CPT) and a taxonomy set as non-translatable. You've noticed that when you update the English post with some terms, the translations do not update with the terms from the English post. You are unsure of the pattern or timing of these updates. Solution: We recommend not expecting WPML to synchronize non-translatable taxonomies between translations, as they are designated as non-translatable. If you need the taxonomy terms to appear or sync with the translations, consider changing their status to translatable. This adjustment will allow them to sync automatically when you update the original post. For more details on how to set taxonomies to be translatable and synchronize them, please visit our documentation:
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 open a new support ticket at WPML support forum.
Problem: You are trying to migrate automatically translated content from a development website to a live website using WPML's export and import documentation. However, after migration, images are not displayed, and some components are missing on the Spanish pages. Solution: We recommend using a migration plugin like Duplicator to move the entire site, rather than just the content. This approach helps avoid issues such as missing images and components, which can occur due to discrepancies like different page IDs between your staging and production environments. Since you are hosting on WP Engine, consider using their built-in tools to push updates from staging to production for a smoother deployment. You can find more information on this functionality here: https://wpengine.com/support/copy-site/
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 the problem persists, please open a new support ticket with us for further assistance.
Problem: Sie möchten sicherstellen, dass die Suchergebnisse Ihrer Website sauber dargestellt werden, ohne dass DE und EN Seiten vermischt werden. Die Suchergebnisse zeigen jedoch eine Vermischung von DE und EN Seiten. Solution: Google bestimmt Sitelinks automatisch, und es gibt keine Möglichkeit, sie in der Search Console manuell zu steuern oder zu entfernen. Die Option, Sitelinks zu deaktivieren, wurde von Google entfernt. Ein Sitelink kann nur entfernt werden, indem die Seite auf „noindex“ gesetzt wird, was nicht immer ideal ist. Die hreflang-Tags sind korrekt implementiert, aber Google beachtet sie nicht immer wie erwartet. Das Problem liegt nicht an den WPML-Einstellungen, sondern an Googles Indexierungsverhalten. Falls Sitelinks gemischte Sprachversionen anzeigen, gibt es keine garantierte Lösung. Google kann seine Indexierung im Laufe der Zeit aktualisieren, aber es gibt keine direkte Möglichkeit, dies zu erzwingen. Die beste Vorgehensweise ist, die Search Console zu beobachten und abzuwarten, bis Google die Indexierung anpasst.
Falls diese Lösung für Sie irrelevant erscheint, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen Ihnen auch, die bekannten Probleme 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.
The client is working on a WordPress multisite and wants to know if WPML can connect pages across different domains when switching languages, how WPML's account limits apply to multisites, and if they can set up a structure with different domains and directories for different languages.
Solution:
1. WPML cannot connect pages across different domains (like biscy.be/team to biscy.fr/equipe) when switching languages because each site is a separate WordPress installation.
2. In a WordPress Multisite, you only need to register the main site with WPML. All subsites under the main site can use the same license without additional registrations. For more details, visit WPML Multisite Registration.
3. WPML supports three URL formats for languages: different domains per language, different directories per language, or language name as a parameter. However, mixing domains and directories for different languages in the same multisite setup is not supported. For configuring different domains per language, refer to WPML's guide on using different domains per language.
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 WPML 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 WPML Support Forum.
Problem: You are experiencing issues with your XML sitemap, where there are duplicates of some English pages and missing German pages. You are unsure if this is related to WPML. Solution: We recommend trying the following steps to resolve the issue: 1. Deactivate and then reactivate the Yoast SEO plugin. This action can force the plugin to rebuild the sitemap. 2. Clear the cache if you are using a caching plugin, as sometimes the sitemap may need to refresh.
If these steps do not resolve your issue, or if the solution becomes 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
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.
