Problem: The client is experiencing issues with ACF Field Groups being translated by WPML despite setting them as not translatable. They have used the constant
to prevent translation, but the WPML backend still shows messages indicating that ACF Field Groups might be translated, causing confusion.
Solution: We advised the client to ensure that the ACF Field Groups are set to 'Not translatable' in WPML's settings. If they have already created translation jobs before adding the constant to the wp-config.php file, they should cancel these jobs and create new ones. This can be done under WPML > Translation Management > Jobs. Additionally, if the strings were already translated in the WPML Translation Editor, they might still appear due to being saved in the editor's translation memory. For further guidance on setting translation preferences for ACF fields, we recommended checking the documentation at https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/.
If this solution does not resolve the issue or seems irrelevant due to being 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 problems persist, please open a new support ticket at WPML support forum.
Problem: If you're using WPML with WooCommerce and have enabled automatic translation, you might encounter an issue where duplicating a published WooCommerce product causes it to start translating immediately, even though you want the duplicated product to remain as 'drafts' and not be translated until it is published. Solution: Currently, there isn't a direct option in WPML to prevent automatic translation for duplicated products that are still in 'draft' status. A potential workaround is to disable automatic translation for the product post type until the product is ready to be published. 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. Should you need more personalized assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with ACF link titles not being translated on your website, it might be because the ACF link fields are set to "Copy" by default. This setting ensures that internal linking works automatically but prevents the translation of the link text. Solution: We recommend setting the field group to "Expert" mode and changing the link field to "Translate". After making these changes, edit the link field on the original content, save the page or post, and then update the translation. This should allow the ACF link titles to be translated.
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. If the problem persists, please open a new support ticket.
Problem: You are experiencing an issue where WooCommerce emails sent after completing an order are partially in the default language (NL), despite having translations available for another language (FR). This occurs even though all email texts have been translated into FR.
Solution: We have identified this as a known issue and have published a temporary workaround. We recommend visiting the errata page for detailed instructions: https://wpml.org/errata/wc-order-update-emails-may-contain-mixed-language-texts/. Additionally, subscribing to the comments on this errata page will keep you updated on any developments.
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 at WPML support forum for further assistance.
Problem: You are managing a client's website with WPML in three languages (NL, NL-BE, FR-BE) and encountering issues with variable products in WooCommerce Bundle Products showing as 'Out of stock' or 'Temporarily unavailable', despite correct stock settings. You have tried troubleshooting through WPML and WooCommerce Multilingual without success. Solution: The issue might not be related to WPML but could be a known issue with WooCommerce itself, especially if it occurs with the original content. We recommend testing the site with an original content while having WPML and WooCommerce Multilingual (WCML) disabled to confirm if the problem persists. This step will help determine whether the issue is indeed with WooCommerce and not WPML.
If the problem is related to WPML or WCML after testing, please do not hesitate to contact us for further assistance. 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 still persists, please open a new support ticket at WPML support forum.
Problem: You are using WPML and ACF and are trying to automatically translate texts from the ACF options pages but cannot find how to do so. Solution: Unfortunately, it is not possible to automatically translate texts from the ACF options pages using WPML. An ACF options page is not treated as a regular page in your database. As a result, it always needs to be translated manually and cannot be automatically translated like a standard post or page. If this solution does not resolve your issue or 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 our support forum.
