Problem: The client is trying to translate the block-based cart and checkout pages in WooCommerce while maintaining the new design. However, the Finnish translation is not working, and the pages remain in English, whereas other languages translate without issues. Solution: We recommend changing the locale settings to match the translation file. This can be done by navigating to the WPML languages settings page in your WordPress admin area. Here is a step-by-step guide: 1. Go to your WordPress dashboard. 2. Navigate to WPML > Languages. 3. Adjust the locale settings to match your Finnish translation files. After making these changes, your Finnish translation should work correctly, and you can maintain the new design of the block-based pages.
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 for further assistance.
Problème : Vous utilisez des 'Loop Grid' de Elementor avec le widget de filtre de Elementor sur des pages en français, créées avec Jetengine. Après avoir activé la fonction AJAX de WPML, qui crée un cookie avec la langue d'affichage, l'utilisation des filtres recharge les éléments en anglais. Solution : Nous vous recommandons d'ajouter le snippet suivant à votre thème pour forcer le rechargement AJAX à respecter la langue sélectionnée :
Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: The client was experiencing issues with modified translations not displaying correctly on the frontend, despite the backend showing them as fine. This problem was particularly evident with the header and footer elements created using ElementsKit and Elementor. Solution: 1. We suggested checking if the issue matched a known problem listed on our errata page: https://wpml.org/errata/elementor-translated-pages-show-stale-content-after-being-updated/ and applying the workaround provided there. 2. We advised the client to make a small change in the content of the header and footer in the original language, save these changes, and then update the translation. 3. We confirmed that the translations for the header and footer were correct after the client updated the translation of the menu and the footer.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening 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, please visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: The client is using WPML on a WooCommerce site with the default language set to Italian, but the WooCommerce endpoints are defaulting to English. Solution: 1. To address the issue of WooCommerce endpoints defaulting to English, we recommend translating the endpoints through WPML's String Translation. Here's how you can do it: - Navigate to WPML -> String Translation. - Search for the endpoints and select them. - Use the button under the results table to change the default language of the selected strings to Italian. For a detailed guide on these steps, please visit https://wpml.org/documentation/getting-started-guide/string-translation/how-to-change-the-source-language-of-strings/. 2. Additionally, be aware of a known issue related to translating endpoints when the default language is not English. For more information, check the errata page at https://wpml.org/errata/incorrect-content-displayed-when-woocommerce-endpoints-are-translated-from-non-english-to-english/. 3. Ensure your WordPress memory limit is sufficient by adding the following code to your wp-config.php file:
Add this above the line /* That's all, stop editing! Happy blogging. */. You can verify the WordPress memory limit in WPML -> Support.
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.
Problem: The client has a multisite setup with WPML plugins network activated and is trying to translate custom code strings into English ('en'), Spanish ('es'), and French ('fr'). The base language for the strings is Portuguese ('pt_pt'). While the Spanish and French translations display correctly, the English page does not show the translated string but instead shows the original Portuguese text. Solution: We recommended applying a workaround described on our errata page. The client should visit https://wpml.org/errata/wpml-string-translation-strings-registered-in-english-even-if-it-is-not-default-language/ and follow the instructions provided there to resolve the issue.
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: After moving to a new server and activating the WPML plugin, you are experiencing PHP warnings related to open_basedir restrictions on every page load. This issue started after the server migration, despite using WPML String Translation 3.2.18. Solution: We recommend clearing your logs and cache to ensure that no old server paths are being cached erroneously. It's also important to double-check the logs after performing these steps. If the problem persists, it might be related to specific server settings or configurations that were changed during the server migration. For detailed guidance, please refer to our documentation on this issue: open_basedir restriction issue.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problema: El contenido traducido no aparece en el frontend; en su lugar, se muestra el idioma original. Solución: 1. Aplicar el workaround descrito en la página de errata de WPML para problemas con Elementor y contenido traducido que no se actualiza correctamente. Puede encontrar más detalles aquí: https://wpml.org/errata/elementor-translated-pages-show-stale-content-after-being-updated/ 2. Incrementar el límite de memoria de WordPress a un mínimo de 128Mb. Agregue el siguiente código en su archivo wp-config.php:
Colóquelo encima de la línea /* That's all, stop editing! Happy blogging. */ 3. Si el problema persiste, crear un sitio staging y compartir las credenciales con nuestro equipo para una revisión más detallada. 4. Si después de seguir estos pasos el problema continúa, recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tiene instaladas las últimas versiones de temas y plugins.
Problem: You are trying to use a one-click translation solution with WPML for a WYSIWYG Editor Advanced Custom Field named 'description', which is set to 'Translate'. Previously, this field was set to 'Don't translate' and was manually translated in the WordPress editor. After changing the setting and using Automatic Translation, the field does not translate unless you modify the English version, save it, and resend for translation. Additionally, you encountered PHP errors related to 'post_content' and 'post_type' being null. Solution: We recommend applying the workaround detailed in our errata page. Please visit Changing Translation Preferences for Custom Fields. Alternatively, you can try editing the original 'description' field on the original content, save the page, and then let the translation process run again.
If this solution does not resolve your issue or seems outdated, please check for 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. If problems persist, we highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing an issue where WooCommerce emails sent after completing an order are partially in the default language (NL), despite having translations available for another language (FR). This occurs even though all email texts have been translated into FR.
Solution: We have identified this as a known issue and have published a temporary workaround. We recommend visiting the errata page for detailed instructions: https://wpml.org/errata/wc-order-update-emails-may-contain-mixed-language-texts/. Additionally, subscribing to the comments on this errata page will keep you updated on any developments.
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 for further assistance.
Problem: You are trying to translate a notification text in WPForms from English to German, but the German translation has formatting issues, specifically missing line breaks. Solution: We recommend checking the WPML errata page for known issues related to WPForms and line breaks in email notifications for secondary languages. You can find the relevant information here: WPForms Line Breaks Removed in Email Notifications for Secondary Languages. After reviewing the documentation, make sure to add some new content or modify the form, and then resave the translated form to ensure the changes take effect.
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 at WPML support forum for further assistance.
