Problem: The client is experiencing 404 errors on the order confirmation page and the endpoint 'order-paid' in translations. The issue temporarily resolves by saving the permalinks but reoccurs the next day. Deactivating the WPML String Translation plugin stops the error. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML → String Translation and ensure that the endpoints are set to their original English values (not translated). 2. Save the permalinks again to resolve the current 404 errors. 3. Return to WPML → String Translation and translate the endpoints as needed. Important: After translating the endpoints, please do not save the permalinks again. We are aware of this issue and are actively working on a permanent solution.
We already have a development ticket for this problem and are actively working on a permanent solution in future releases.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket here.
Problem: If you're experiencing issues with WPML Automatic Translation where updating content in the primary language does not load for translation and shows the error message 'Unable to retrieve job details', this might be due to Gzip compression enabled on your server. Solution: We recommend asking your hosting support to disable Gzip compression. You can find more details on this issue in our errata page: Translation jobs not synchronised when Gzip compression is enabled. After disabling Gzip compression, restart your server. Once your site is up again, edit the original content, save the page, and try to translate it again. If the problem persists, please do not hesitate to contact us for further assistance.
Please note that this solution might be irrelevant if it's 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 continues, please open a new support ticket at WPML support forum.
Problem: You are using Yoast SEO with WooCommerce and have set a product to NoIndex in the default English version. However, this setting is not synchronized to the translated versions of the product, where it still shows as Index. Solution: We recommend following the workaround provided in our errata for this known issue. Please visit the following link and apply the suggested steps: Yoast SEO meta field synchronization does not work for fields set as copy. This solution has been tested and worked correctly on our test site.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with the translation of Next Bricks elements on their website using WPML. The default language is Croatian, and when switching to English, most of the content remains in Croatian. Additionally, there are issues with translating ACF option page content.
Solution: For the Next Bricks translation issue, we recommend the following steps: 1. Navigate to the
For the ACF option page content translation issue, follow these steps: 1. Open the Field Group for the option page and set the translation preference to "Same fields across languages." 2. Go to "Option Pages" from the dashboard. 3. Switch to English using the language switcher in the admin top bar. 4. Add content in the Email and Telephone fields.
This should resolve the translation issues. If these solutions do not work or become outdated, or if they do not apply 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported multiple issues: pages not appearing in the translated language, content inside Spectra tabs not translating correctly, and images not displaying correctly in translations. Solution: 1. For pages not appearing in the translated language, we recommended removing ghost entries and re-translating the pages. This involves: - Navigating to WPML > Support > Troubleshooting. - Clicking on "Remove ghost entries". - Editing the page in the original language, making a minor change, and saving. - Updating the translation page.
2. For translating Spectra tabs, we provided an XML configuration to make the tab titles/labels translatable. The client should: - Add the provided XML configuration to the WPML configuration file. - Update the original page and translate the tab content in the Advanced Translation Editor.
If these solutions do not resolve your issues or if they seem outdated, 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.
Problem: If you're experiencing blank or white pages on product pages using WoodMart custom layouts when WPML is active, and this only occurs with products having many variations (10-15+), while products with fewer variations display correctly, we can help. Solution: We recommend updating a specific function in your WPML plugin files. Please locate the file
After applying this change, please clear any caches on your site to see if the issue resolves. This modification addresses template display failures due to the PHP setting
pcre.backtrack_limit
being exhausted. A permanent fix is anticipated in WPML 4.9.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: El cliente enfrenta problemas con la traducción automática de la imagen destacada y otros textos de imágenes (alt, título, pie de foto) en un CPT creado con PODS y Elementor al usar WPML. Las imágenes destacadas no se asignan automáticamente al traducir el contenido y no aparecen en el frontend en el idioma traducido. Solution: 1. Verificar la traducción de la imagen destacada y otros textos de imagen manualmente en WPML -> Traducción de multimedia. 2. Si el problema persiste, editar manualmente la obra en el idioma secundario y añadir las imágenes en francés. 3. Si se utiliza el plugin 'DynamicConditions', asegurarse de que está configurado correctamente para mostrar las imágenes en los idiomas traducidos. 4. Ajustar las dimensiones de las imágenes destacadas mediante CSS para mantener la consistencia en todos los idiomas:
Si la solución proporcionada no resuelve el problema o parece irrelevante debido a actualizaciones o diferencias en el caso, recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable 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.
Problem: You are experiencing an issue where variation swatches display as image/button swatches on the original language page, but show as dropdown selects on the translated version. Solution: We found that the translated terms don't have the text swatch enabled. To resolve this, please edit the translated terms and enable the text swatch. Afterward, update the product in the default language by making a minor edit and then update it. This should ensure consistency across both languages.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to translate a specific block from English to German on your site, but the section below the pictures remains in English and refers to English language pages. Additionally, the German version of the homepage differs significantly from the English version. Solution: We suspect that the emojis at the beginning of each heading might be causing the translation issues. We recommend removing the emojis from the headings and attempting the translation again. For example, we duplicated the page on your site as a new draft without the emojis, and the translations worked correctly. If removing emojis is not an option for you, please let us know so we can further investigate and possibly escalate the issue. Regarding the use of formal German, not all translation engines support it. If you are using DeepL, you can set up WPML to use formal German by navigating to WPML > Settings. Here is the documentation on how to change automatic translation engines: https://wpml.org/documentation/automatic-translation/how-to-change-automatic-translation-engines/
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 reported a critical error on their site, experiencing a PHP 8.3 infinite recursion issue leading to a 503 error. This was traced back to a potential bug in the WPML plugin with the newer WordPress version. Solution: 1. We asked the client to check if the issue persists after following the steps described on the erratum page for PHP 8.3.x errors, which can be found here: PHP 8.3.x Fatal Error. 2. We requested a detailed description of the issue, including steps to reproduce it and any error messages, to better understand the problem. 3. We asked for access credentials to the site to investigate the configuration and reproduce the issue. 4. We inquired if the client would prefer to continue troubleshooting the issue or remain on the older WordPress version (v6.8.9) that did not exhibit the problem.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we 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 further assistance is needed, please open a new support ticket at WPML Support Forum.
