Problem: You are working on a site under development and trying to translate Germanized Free Strings using WPML, but the translation does not work. Solution: We recommend following these steps to resolve the issue: 1. Add the following XML in WPML >> Settings > Custom XML Configuration section:
2. Navigate to the WPML >> String Translation page and search for the checkbox text. 3. If the English language is assigned to the German string, select that string and assign the German language using the "Change the language of selected strings" dropdown. 4. Add the test translation to see if it displays correctly. For more detailed guidance, please refer to the documentation on how to change the source language of strings.
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.
Problem: You are developing a site and need to add a custom currency or set different prices for different languages using the same currency. You found that the multi-currency plugin allows adding currencies like Solana or Bitcoin, and you are wondering if you can add your own custom currency to set different prices per currency. Solution: 1) Adding a custom currency is not a feature provided by WPML but by WooCommerce. You should add your custom currency to WooCommerce, and then you can use it in WPML/WCML. We recommend checking the WooCommerce developer documentation on how to add a custom currency symbol here: https://woocommerce.com/document/add-a-custom-currency-symbol/ 2) It is not possible to set different prices for different languages using the same currency in WPML. Each language version of a product is a translation of another, so the content and prices should remain consistent unless they are created as separate products.
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 translating the checkout page using WPML, specifically when the page is built using WooCommerce blocks. The checkout page displays in the wrong language for Austrian German (de_AT), as WooCommerce currently does not support translation for certain elements in custom languages when using blocks.
Solution: 1. Ensure a full backup of the website is made. 2. If using blocks on the checkout page, replace them with the WooCommerce shortcode:
1
[woocommerce_checkout]
. 3. Update the translations after changing to the shortcode. 4. This method allows the use of WPML String Translation to handle the translations effectively.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, we recommend opening a new support ticket. Additionally, 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, please visit our support forum at WPML Support Forum.
Problem: The client is developing a site and considering using WPML. They want to know if WPML supports using a CDN when configuring different domains for each language. Solution: We confirm that WPML supports using a CDN with different domains for each language. Here is a step-by-step guide to setting this up: 1. Configure WPML for Different Domains: - Navigate to WPML → Languages. - Select "A different domain per language" and specify your domains (e.g., example.com for English, example.fr for French). - Ensure each domain is correctly pointed to your WordPress site through DNS settings. - For further details, refer to our complete guide on different domains: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/ 2. Set Up Your CDN: - Add each language domain as a separate "pull zone" in your CDN. - Configure caching rules to ensure language-specific assets (such as images and scripts) are not mixed between domains. 3. Manage SSL and Cache: - If using HTTPS, ensure each domain has a valid SSL certificate. - Clear your WordPress and CDN caches to ensure all settings take effect.
If this solution does not resolve your issue, or if it 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing an issue where WPML does not recognize HTML tags like breaks or P tags in the ACF WYSIWYG editor.
Solution: We recommend turning off the 'big segments' preference in ATE, as this has resolved the issue in our tests. If the problem persists, try enabling the option 'Use the previous version of the Advanced Translation Editor' in ATE, make a small change in your ACF field content, save it, and attempt to translate again. For more details, please refer to the errata page at https://wpml.org/errata/disabling-i-prefer-bigger-segments-is-not-working-properly/.
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 open a new support ticket at WPML support forum.
Problem: You are developing a site and attempting to translate it from German to English using auto-translate. However, the form fields on the WooCommerce checkout page remain in English in the frontend, despite translating the strings. Solution: We have identified this as a known issue. We recommend applying the workaround from the following errata page: https://wpml.org/errata/l10n-php-performant-default-translated-strings-not-displaying-correctly/. A permanent fix is scheduled for the next WPML version.
Please note that 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 issue persists, please open a new support ticket at WPML support forum.
Problema: El cliente desea cambiar el idioma predeterminado de su sitio web de 'de.domain.com' a otro idioma que ya ha traducido, pero está preocupado por posibles problemas que puedan surgir al hacerlo, especialmente porque el contenido en los idiomas difiere ligeramente. Solución: Si estás experimentando esta situación, te recomendamos seguir estos pasos para cambiar el idioma predeterminado de tu sitio web sin problemas: 1. Asegúrate de realizar un respaldo completo de tu sitio web antes de hacer cualquier cambio. 2. Verifica que hayas traducido las páginas principales de tu sitio web, como la página de inicio. 3. Para cambiar el idioma predeterminado, ve a WPML → Idiomas → Idiomas del sitio. 4. Haz clic en el botón "Cambiar idioma predeterminado" y selecciona el idioma que deseas establecer como predeterminado. 5. Dirígete a WP → Ajustes → Enlaces permanentes y haz clic en "Guardar cambios".
Es posible que esta solución no sea relevante si ya está desactualizada o si no se aplica a tu caso. Si después de seguir estos pasos aún necesitas ayuda, 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 has instalado las últimas versiones de temas y plugins. Si necesitas asistencia adicional, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client is experiencing an issue where navigating to
1
www.domain.com
redirects to the homepage of the main language instead of redirecting to the correct language version of the site. Solution: We recommend informing the hosting support about the issue with WPML when using NGINX and a different domain per language and asking to review the DNS settings of the server. Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If after checking the known issues and confirming that you have the latest versions of themes and plugins the problem persists, we highly recommend opening a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client wanted to hide the main language on the front end for non-admin users because it was not ready for public viewing. They were also considering switching the main language to a translated language and were concerned about potential data loss or issues.
Solution: We informed the client that it is not possible to hide the default language using WPML's 'Hide languages' feature, as it only allows hiding secondary languages. We suggested using a Maintenance Mode plugin to hide the entire site from users until it is ready. Here is an example of such a plugin:
Additionally, we advised that if the client has original content that is not ready to be published, they should set this content as 'Draft' in WordPress. This is not related to WPML, as WPML only handles translations of the original content. For more information on drafts, please visit: WordPress Drafts
If the solution provided here is not relevant to your situation, either because it's outdated or not applicable to your case, 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. If you need further assistance, please contact us in the WPML support forum.
Problem: The client wanted to display certain products only in specific languages without translating them. Solution: We explained that our WooCommerce Add-Ons require a translation for each product. However, we suggested creating the product in the default language and then setting up a 301 redirect to the product translation in the language where the product should appear. This way, the product will only be visible in the selected language.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues, verifying the version of the permanent fix, and ensuring that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
