Background of the issue:
I am trying to send pages for translation to a translation service using WPML. We are using ACF, and the button in our blocks are using the Link field type. Our blocks are using 'same fields across languages' but I have also tried 'different fields across languages'.
Symptoms:
The buttons/links are not being sent for translation, while all other fields are being sent correctly.
Questions:
Why are the buttons/links not being sent for translation?
Is there a specific setting in WPML or ACF that needs to be adjusted for button/link translation?
Thanks for contacting us. Based on your screenshot, I can see that you've configured this correctly.
I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
Thanks for your patience. I've reviewed your website and tried several methods, including adjusting the translation settings for the ACF field group, but the issue still persists. It could be related to something else in your setup.
Given the complexity of the setup, could you please try replicating the issue on our sandbox site below? hidden link
You can install the required plugins and theme, then create a test page to help us troubleshoot further.
Thanks for your patience. I have some feedback from our 2nd Tier Support, and they found out that the issue is caused by the button field name conflicting with another button field name. Please use a unique name for all your fields to avoid conflicts. I've attached a screenshot for our reference. Let me know how it goes.
Thanks for your reply. Our 2nd Tier Support also mentioned the below. Could you try the solution we shared above and let me know if this works for you?
As this is a repeater field, I suggest checking for other instances of the button subfield - as this can conflict.
