Problem: The client is experiencing issues with price rounding in different countries/currencies on their WooCommerce site. Prices are rounded correctly when viewed from the Netherlands, but not when viewed from countries like the UK, where different tax rates apply. Solution: We recommend configuring the WooCommerce Tax Settings to display prices excluding tax. This approach helps in managing the display of prices consistently across different countries, despite the variations in tax rates. For detailed guidance on adjusting these settings, please refer to the WooCommerce documentation on tax settings: Setting up taxes in WooCommerce.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where product addons disappear when switching languages on your multilingual website. Solution: If you're facing this problem, we recommend you follow these steps: 1. Navigate to Products -> Extra options. 2. Edit the "Extra balletjes". 3. From the top admin bar, select "All Languages". 4. Add the category in all languages. 5. Update the rule. After completing these steps, the product add-on should appear correctly in all languages.
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.
Problem: The client added a new language for Austria and mapped it to the German language. Most of the site was translated, but the checkout and cart pages were still showing in English, and some strings were not appearing in the 'String translations' tab.
Solution: We reviewed the String Translation section and located all the static strings for the Cart and Checkout pages. We advised the client to navigate to "WPML > String Translation" and use the search function with the exact match option to find the strings that appear in English on these pages. If found, they can be translated by clicking on the "+" icon under the country flags.
For the strings that were not available for translation, we scanned the WooCommerce plugin through "WPML > Theme and Plugins localization" to make them accessible in the String Translation section. We also advised on how to handle texts with dynamic values by searching for the initial word and retaining placeholders in the translation.
If you're experiencing similar issues, we recommend trying the steps mentioned above. However, please note that the solution might be irrelevant due to being outdated or not applicable to your case. If these steps do not resolve your issue, we highly recommend checking 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.
Problem: The client created a custom language for Austria and mapped it to German. However, the Austrian site still displays in Dutch, the default language. Additionally, 'Austria' only appears in the language switcher on product pages and is missing on other pages. Solution: We recommend the following steps to ensure the correct setup: 1) Create a new Post or Page in Dutch for testing purposes. 2) Navigate to WPML >> Translation Management Dashboard. 3) Select the newly created Post/Page. 4) Add it to the Translation Basket. 5) Go to WPML >> Translation Management >> Translation Basket. 6) Send the content for translation in German (Austria) by choosing yourself as the translator. 7) Access WPML >> Translations queue and translate the page by clicking the Translate button. For more detailed instructions, please refer to our documentation on translating your contents.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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. If you still need assistance, please do not hesitate to open a new support ticket in our support forum.
Problem: The client was experiencing styling issues on the translated pages of their website, where several style elements appeared differently compared to the original Dutch version. Solution: We recommended checking if the page builder or theme stores the styling in a custom field, which might contain words like "style", "css", "layout", or "styling". This custom field should be set to "copy" to ensure the styling is carried over to the translated pages. The client should then make a small change in the default language, save the page, go to the translation, and re-save it for the CSS to be copied over. For more detailed instructions, we provided a link to our documentation: https://wpml.org/documentation/getting-started-guide/translating-custom-fields/.
Please note that the solution provided might be outdated or not applicable to your case. If you're still facing issues, 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 necessary, please open a new support ticket for further assistance.
Problem:
If you're experiencing issues with your header translations not being displayed on the front-end of your site, particularly with elements created by Elementor, even after trying all the troubleshooting options. Solution:
First, ensure that you have translated the header template. Then, verify that the translated template has a unique title and slug, different from the default language page. Next, translate the header ID through WPML-> String Translation. Finally, check if the translated string appears correctly on your site.
If the solution provided here does not resolve your issue, or if it seems outdated or not applicable to your case, we recommend opening a new support ticket. We also 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. If further assistance is needed, please contact us on the WPML support forum.
Problem: The client was experiencing issues with links in the product descriptions of translated product pages. These links were supposed to refer to certain collections but were redirecting incorrectly on the Italian and Spanish versions of the site. The client had already attempted to 'Scan now and adjust links' in the WPML settings and cleared the cache, but the problem persisted. Solution: We recommended that the client recheck the URLs when translating the product and use absolute URLs for each language version:
NL:
https://gelwapen.nl/collections/gel-blasters/
IT:
https://gelwapen.nl/it/collections/gel-blasters/
We also noticed that the client was using the WordPress editor to manually translate products and in the Spanish version, the absolute URL was pointing to the default language. We suggested changing it to the correct language-specific URL:
ES:
https://gelwapen.nl/es/collections/gel-blasters/
Or use the relative URL as in other languages:
/collections/gel-blasters/
After changing one of the URLs to the relative version, it worked properly in the frontend.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
