Problem: If you're experiencing issues with translating a WooCommerce Bundled product where the translated product is missing settings like layout and pricing options, this might be due to the default language settings for certain variables. Solution: We recommend checking the settings for the min and max bundle size variables in your WPML settings. Here's how you can do it: 1. Navigate to WPML > Settings > Custom Fields Translations, and click on Show System Fields. 2. Set both
_wcpb_max_qty_limit
and
_wcpb_max_qty_limit
to Copy. This action will ensure that future translations copy over the value correctly.
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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Symptoms:
The form is not fully translated. For example:
- success message is not translated
- the email subject and text are not translated
- after submit it redirects to the wrong language
Solution:
The language was hidden so the success message and email texts were not showing the translations .Unhiding the language resolved that part. For the redirect, it was an issue with every dynamic internal link. It's required to flag the option "Adjust IDs for multilingual functionality" in "WPML -> Languages -> Make themes work multilingual"
Problem: You are trying to translate a page using WPML, but you encounter a PHP fatal error. Specifically, you receive a PHP Warning: Undefined array key and a PHP Fatal error related to the array_merge function in the WPML plugin. Solution: The issue you are experiencing is related to a known error documented here: WPML 4.8 Fatal Error When Translating Pages Containing Images Without Metadata. We recommend updating WPML to the latest version available, which at the time of the response was 4.8.w. This update should resolve the error and allow you to translate pages without encountering the PHP fatal error.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is configuring WPML and wants to skip or disable the 'AI translation' options during the setup process. Solution: If you're experiencing the same issue and wish to disable AI translation in WPML, we recommend you follow these steps: 1) Navigate to WPML > Translation Dashboard and ensure the 'Translate Everything automatically' option is turned off. 2) Go to the Advanced Translation Editor, click on the settings at the top right, and disable the 'Translate all content automatically when the editor is opened' option. 3) In WPML > Translation Tools > Automatic translation engines, disable all automatic translation engines. 4) Check WPML > Translation Tools > Who can use Automatic Translation? and ensure that no admin or translator is enabled for automatic translation. After completing the Setup Wizard by entering all required information, these steps will help you avoid any automatic translations.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where a WooCommerce product variation with a price set to zero is not translating correctly, and the variation price appears empty in the translated product, preventing it from being purchased. Solution: We recommend applying the workaround described in the WPML errata page. You can find the specific details on how to address this issue here: Translated Variations Appear Out of Stock When Price is Zero.
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. Additionally, please feel free to open a new support ticket with us for further assistance.
Problem: You are using ACF PRO to create custom fields in a WooCommerce product and are trying to translate a text field from Italian to English using WPML. The translation updates correctly when there is text in the primary language field. However, if the primary language field is emptied, the translation in the secondary language does not update and continues to display the previous text. Solution: Due to the way ACF and WordPress function, it is not possible to update the translation when the primary language field is empty. This is not a bug but a technical limitation inherent to these platforms. A possible workaround is to manually edit the page.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where select fields created with the Elementor Pro form widget and translated using the WPML 'classic editor' are not rendering correctly. Instead of displaying each option on a separate row, all options appear in a single row separated by '', making it impossible to select a specific option. Solution: We recommend updating to the latest version of the WPML plugin where this issue has been addressed. If after updating, the problem persists, or if this solution does not apply to your case because it might be 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 you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client reported that the English version of the "News" page was visible despite there being no direct translation. This issue was related to how WordPress and WPML handle blog pages, where if a blog page is not translated, it might still display content from the default language.
Solution: We proposed two solutions: 1. Implement a 301 redirect from
https://www.uniaudit.it/en/news/
to
https://www.uniaudit.it/news/
. This can be done using a plugin or by adding an entry in the
.htaccess
file. 2. Create a translation of the "News" page in English and then set it to Draft or Private to ensure it exists but is not publicly accessible.
Additionally, we advised clearing all caches after making significant changes, especially since the client was using the SiteGround "Speed Optimizer" plugin.
If these solutions do not resolve your issue or if they seem 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 further assistance is needed, please open a new support ticket at WPML support forum.
strings using WPML String Translations for the "WooCommerce PayPal Payments" plugin. However, the translations are not appearing on the WooCommerce checkout page in the frontend. Solution: We recommend checking the solution provided in a similar case on our forum. Please follow the link and apply the steps described:
If the provided solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we suggest 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.
