Problem: The client was unable to translate certain custom fields using Advanced Custom Fields (ACF) and WPML's Advanced Translation Editor (ATE), despite setting the fields as translatable. The issue was due to multiple fields having the same name across different field groups, which caused WPML to apply the same translation settings to all similarly named fields. Solution: 1. Verify that the field groups in ACF are set to 'translatable' under ACF -> Fields groups. 2. Ensure that in WPML -> Settings, the field groups for ACF are set to 'untranslatable' if they should not be translated. 3. For fields that need to be translated, ensure each field name is unique across all field groups to avoid conflicts in translation settings. 4. If the issue persists with existing content, make a minor edit in the default language and update the page. Then, access the translation editor where the field should now be available for translation.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, please open a new support ticket at WPML support forum for further assistance.
