Problem: You are using WPML to translate content on your site, but while translations are available, they are not visible on the frontend. Solution: First, ensure that the WPML String Translation can write in the necessary folder. This issue might be due to insufficient writing permissions. Contact your hosting provider to adjust these permissions as outlined here: WordPress File Permissions. After resolving the permissions issue, apply the workaround provided on the WPML errata page here: WordPress 6.7 .mo files not loaded and verify if the translations now appear on the frontend.
If this solution does not resolve your issue or seems outdated, 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 the problem persists, please open a new support ticket.
Problem: The client is developing a site and wants to translate country names in product listings using WPML, while also looking to save credits. Solution: Currently, WPML does not support direct import of content for translation that is stored outside of the database. However, we recommend using WPML's translation memory feature, which can automatically translate strings that have been previously translated, thus helping to save credits. We are also actively working on adding functionality to better support your needs.
If this solution does not fully address your issue, 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 further assistance is needed, please open a new support ticket.
Problem: You are working on a site under development and need to understand the correct settings for translating product custom fields using WPML. Solution: When you install the WPML and WooCommerce Multilingual plugins, the default settings for WooCommerce product custom fields are configured correctly. If you are using custom fields not added by the WooCommerce plugin but have added them yourself, we recommend referring to our guide on how to translate specific custom fields. You can find the guide here: Translating Custom Fields.
If this solution does not apply to your case, or if it seems outdated, please check the 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 if you need further assistance. You can do so here: WPML Support Forum.
Problem: You are developing a site and want to use the REST API to translate categories and terms in WPML. Solution: We recommend using the WooCommerce API to create categories and terms and add translations to existing ones. For detailed guidance, please refer to our documentation on using the WordPress REST API with WooCommerce Multilingual. You can find it here: Using WordPress REST API with WooCommerce Multilingual.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are working on a site using Elementor and WPML and want to know if changes made to the design in the main language will automatically be copied to the translated pages. You've noticed that the translated pages remain in the old design. Solution: When you change the design in the default language, you need to manually update the translation using the WPML translation editor to ensure that the new design is copied to the translated pages.
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 persists, please open a new support ticket.
Problem: You are encountering a critical error when using WooCommerce Product Filters in a secondary language. Solution: We recommend setting up independent filters for each language: 1. Navigate to WooCommerce > Filters. 2. Switch to the second language and create a new filter directly in that language, then save it. 3. Obtain the shortcode for this new filter (e.g.,
[wcpf_filters id="86"]
). 4. Go to Appearance > Widgets, add a shortcode block, and insert the shortcode for the new filter. 5. Translate the necessary strings in WPML > String Translator, specifically the admin_texts_wcpf_setting_default_project string with the ID of the new filter.
This approach is necessary because the WooCommerce Product Filters plugin expects users to translate the filter ID option, as indicated in their WPML compatibility class. However, it's unclear if this is the recommended workflow or if translated filters should also function correctly. We suggest contacting the Product Filters for WooCommerce plugin authors to report this issue, as the plugin is not listed as compatible and the authors have been difficult to contact directly in the past.
Using different filters per language should serve as an alternate solution until further clarification is obtained.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at WPML Support Forum.
