Problem: You are trying to translate the VAT label in the WooCommerce checkout using WPML. Although the translations are available in the string translation section and are translated, they do not appear on the checkout page. Solution: First, apply the workaround described on the errata page for issues related to missing translations due to WordPress 6.7 MO files not being loaded. You can find the details here: WordPress 6.7 MO files not loaded. Next, ensure that your theme and any plugins related to the VAT string are properly scanned for translations. This can be done under WPML -> Theme and plugins localization. Then, enable auto-registering of strings as described in this guide: Finding strings that don't appear on the string translation page. Finally, use the WPML String Translation to translate all instances of the VAT string.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where attributes imported using WP ALL IMPORT and WPML are being added to incorrect languages; some attributes are added to English (EN) which is correct, and some to Dutch (NL) which is incorrect, despite having done a similar import successfully in the past. Solution: We asked the client to confirm if they followed the steps in our guide for importing multiple languages with WP ALL IMPORT and WPML, which can be found here: Importing Multiple Languages with WP ALL IMPORT and WPML. We also inquired whether the client is only importing global attributes without importing products, if they created
one import file for each language, and what they are using as a unique identifier.
We did not receive a reply to those suggestions. The client informed us that he found a different solution by using ACF fields for the values instead of attributes.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, 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. If further assistance is needed, please contact us in the WPML support forum.
