Problem: You are experiencing an issue with ACF (v6.6.2) conditional logic when using taxonomy fields on a multilingual site with WPML (v4.8.5) + ACFML (v2.1.5). The visibility rules based on taxonomy terms work correctly only in the site’s default language. When editing a translated post, the conditional logic checks the term ID from the default language, not the translated term in the current language, causing the condition to fail. Solution: We have published a workaround for this problem. We recommend you visit the following errata page for a detailed explanation and steps on how to implement the workaround: Advanced Custom Fields (ACF) Conditional Logic not working for Taxonomy or Post Object fields in secondary languages.
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.
Problem: The client was experiencing an issue where the notification 'Your default language, Italian, must be mapped to a supported language in order to use automatic translation' kept reappearing even after mapping the language and saving the settings. This issue persisted despite the WP memory limit being set to 512MB and clearing the WPML cache. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML → Settings → Translation Engines settings and ensure at least one translation engine is activated. 2. Save the changes and check if the error persists. If the problem continues, it might be due to outdated information or a unique case not covered by this solution. 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 remains unresolved, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing a Fatal Error with the Advanced Custom Fields Multilingual (ACFML) plugin version 2.1.4.1, it might be due to a compatibility issue with the plugin's latest update. Solution: We recommend updating the ACFML plugin to version 2.1.4.2. This update addresses the Fatal Error issue and should restore functionality to your site. To update, simply go to your WordPress dashboard, navigate to the 'Plugins' section, and select the update option for ACFML.
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 problems persist, please open a new support ticket with us.
Problem: You need help resolving an issue with the product sitemap generated by Yoast on a WooCommerce site using WPML, WPML SEO addon, WooCommerce Multilingual & Multicurrency, and Yoast SEO plugins. The product sitemap includes a non-existent URL that redirects to a correct URL. Solution: The issue you're experiencing is known. Yoast has merged the necessary changes for a new filter to refactor the code, which is a prerequisite for us to work on a fix. Meanwhile, we recommend deactivating the Yoast sitemap option in the settings via the toggle to generate a new version of the sitemap.
If this solution does not resolve your issue or seems outdated, 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 the problem persists. For further assistance, you can contact us through the WPML support forum.
