Problem: The client is experiencing an issue with the Advanced Custom Fields (ACF) flexible content where deleting a flexible content layout causes the fields from the deleted layout to display in the next section instead of being empty. This happens because the WPML translation editor does not handle empty fields as expected, leading to old values being displayed instead of empty ones. Solution: If you're experiencing this issue, we recommend trying one of the following solutions: 1. Add the following filter to your
inside your ACF value to prevent it from being empty.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We 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. If the issue persists, please open a new support ticket with us.
Problem: The client reported an issue where the Advanced Custom Fields (ACF) flexible content field wasn't syncing with translations after adding a new flexible item. The translations were dropped because the keys weren't synced. The client also inquired about the checkbox option 'Keep repeater and flexible sub-fields in the same order as the default language' and whether it should be checked or unchecked. Solution: We advised the client to ensure that the ACF flexible field is set to COPY, not Copy-once, according to our documentation. We provided a link to the relevant documentation: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/ We also suggested that the client: 1. Change the ACF flexible field setting to COPY. 2. Check if the issue persists on a new page. 3. Provide WPML debug information as described in our documentation: https://wpml.org/faq/provide-debug-information-faster-support/
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 with us.
