Problem: You are trying to manage product translations on your site using WPML and want to prevent certain product titles from being translated while ensuring that all product details, especially colors, are translated accurately. However, WPML sometimes leaves product colors and certain details untranslated, causing inconsistencies in product descriptions. Solution: If the WooCommerce Multilingual plugin is active on your site, all product data, including taxonomies and variations, should translate easily and remain consistent. To keep the product title consistent across languages, when translating the product, copy the title from the default product into the translation. In the translation editor, translate the rest of the content and save the translation. This way, the product title will stay the same in all languages, while other data like taxonomies and variations will be translated properly. Ensure that the WooCommerce Multilingual plugin is installed and activated on your site, as it handles the translation of all product data, including variations, correctly. For more details on translating products and their data, please refer to this guide: https://wpml.org/documentation/related-projects/woocommerce-multilingual/
If this solution does not apply to your case, or if it seems outdated, we 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 you still need assistance, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing a 404 error on your WordPress site after installing WooCommerce and during updates. This issue arises because WPML sets the default language to BG, and WooCommerce rewrites the path in the .htaccess file, leading to a redirection to a non-existent /bg/ page. Solution: We recommend testing this on a clone of your site with only WPML, WooCommerce, and WooCommerce Multilingual enabled, without any other third-party plugins. This will help determine whether the issue is solely due to WooCommerce or if it arises from an interaction with an add-on.
If this solution does not resolve your issue or seems outdated, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at WPML support forum.
The client is experiencing issues with ACF Options fields not appearing on the front-end and being editable in the back-end. Additionally, when selecting a different language in the back-end, an error message 'Sorry, you are not allowed to access this page' appears.
Ensure that the ACF Options page is translated into the secondary language after performing a site backup.
Additionally, improve your site's performance by increasing the WP Memory Limit to 256MB and the MaxInputVars to 10000. For more details on these settings, visit:
If these steps do not resolve your issue, or if the solution 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 the problem persists, please open a new support ticket.
Problem: The client was experiencing issues with menu synchronization and display across different languages (ENG, ESP, FRA) on their website. Despite translations being available, menus and header templates were not appearing correctly in languages other than English and Italian.
Solution: 1. We recommended updating the WPML plugin and all related add-ons to the latest version to ensure compatibility and functionality. 2. For the header not displaying in other languages, we advised translating the Header and Footer templates using the 'Header Builder' and ensuring these templates are selected in the theme customizer. 3. To address the menu display issues, we suggested adjusting the menu order in the default language and resyncing the menus using this guide: Translating Menus. 4. For the page contents not showing in other languages, we recommended making a minor edit to trigger a translation update and ensuring all sections are fully translated. 5. If issues persist or if the solution provided here does not apply due to updates or differences in your case, please check 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 further assistance is needed.
Problem: The client needs to automate the 'Set prices in other currencies manually' option for all new and existing products in their WooCommerce store. Manually setting this for over 5000 products is not feasible. Solution: We recommend implementing a custom code solution, as WooCommerce Multilingual does not support this functionality by default. For new products, adapt the code by changing the value for
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. If further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client has a number of ACF fields, including a repeater field with an image subfield and a text subfield. The issue arises when trying to handle translations for these fields in a duplicated page. Solution: If you're experiencing this issue, we recommend setting the repeater field to 'COPY' if you want the changes in the default language to be copied or synced to the second language. This setting is necessary when the page is duplicated and you wish to add translations independently. For more detailed guidance on setting up your ACF fields with WPML, please visit our documentation on Recommended Custom Fields Translation Preferences for ACF and WPML.
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.
Problem: You are trying to translate the copyright information field in the footer using WPML, but the translated string is not displayed on the website frontend. Instead, the original English text appears. Solution: To display the translation of the Elementor Pro Templates, you need to translate the templates via translation management rather than using string translation. Ensure that the translation is 100% complete to be visible on the frontend of the website. For more information, please visit Translating Elementor Templates.
If this solution does not apply to your case, or if it seems outdated, 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.
