Problem: 1. The Cart page and upsell section are not translated in German, French, Lithuanian, and Portuguese despite being marked as fully translated in WPML. 2. Custom glossary terms are not respected in various site locations such as headers, footers, and category names.
Solution: For Issue 1: - Confirm no missing setup warnings in WooCommerce → WooCommerce Multilingual & Multicurrency → Status. - Ensure WooCommerce pages and endpoints are correctly translated in WooCommerce → WooCommerce Multilingual & Multicurrency → Store URLs. - If using WooCommerce Cart/Checkout blocks, enable 'Detect strings in JavaScript files', scan WooCommerce, and translate strings from WPML → Translation Dashboard → Other texts (Strings). For more information, visit https://wpml.org/documentation/related-projects/woocommerce-multilingual/how-to-translate-woocommerce/. - Resend the Cart page for translation for affected languages and save the translation again.
If these solutions do not resolve your issues or if they seem 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 at WPML Support Forum.
Problem: The client is experiencing issues with links in the header not correctly changing to /en and other languages after adding a WPML menu for language switching. Some links still redirect to the Polish version instead of the intended language. Solution: We recommend two approaches depending on how you manage your site's translations: 1. If you prefer manual translation/editing, switch to using the 'WordPress Editor' instead of the WPML Translation Editor for the translated template. This allows you to manually manage links separately for each language. 2. If you use the WPML Translation Editor (recommended), ensure in the default language Elementor template to use dynamic/internal Elementor links. This setup helps WPML automatically adjust the URLs correctly for all languages when translations exist. For more information on dynamic links in Elementor, visit https://biglinden.com/support/what-are-dynamic-links-or-smart-links-in-elementor/.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with WPML not translating certain elements on a page created with Elementor, including a form and some headings. Additionally, there is a problem with the links in the header not correctly changing to include language-specific subdirectories (/en) after a new WPML menu for language switching was added.
Solution: For the issue with the Elementor form and headings not being translated, it appears there might be a confusion due to using the same slug for the translated category. We recommend: 1. Changing the slug of the EN category to ensure it is unique and not used elsewhere on the website. 2. Re-adding and saving the translated description. 3. Saving/updating the category. This should help in displaying the correct translated content for the category.
For the issue with the header links not correctly changing to include /en or other language subdirectories, we have opened a new ticket to investigate this matter further as it seems to be a separate issue related to the configuration or translation of the menu/header links.
If these solutions do not resolve your issues or if they seem 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 reported two main issues with their multilingual WordPress site using WPML and Elementor. First, the Elementor Single Product template was not registering all strings for translation, showing only 9 strings out of an expected 957 words. Second, a WooCommerce category description translated in WPML was still displaying in Polish on the English version of the site.
Solution: For the first issue, it was discovered that the use of emoji/special characters in the content was causing the database entries to break during saving/translation due to the database collation not fully supporting these characters. We recommended two solutions: 1. Remove the emoji/special characters from the affected content. 2. Request the hosting provider to update the database collation to a fully supported UTF8MB4 collation, such as
For the second issue, separate tickets were opened to address it and related concerns.
Please note that the solution provided 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.
