Some ACF fields doesn´t appear on the translator editor

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing issues where some ACF fields do not appear in the translator editor, it might be due to using the same field name, such as "subtitle", across various groups. This can prevent all field values from being available for translation in the Advanced Translation Editor.
Solution:
We recommend that you assign a unique name to each field. This change should make all your field values visible and translatable in the translator editor.

Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, 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 do not hesitate to open a new support ticket at WPML support forum for further assistance.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: Bug

This topic contains 37 replies, has 2 voices.

Last updated by Paola Mendiburu 2 months, 3 weeks ago.

Assisted by: Paola Mendiburu.

Author	Posts
June 12, 2024 at 8:51 am #15729918
lauriJ-2	Ok, thanks. I will wait for your reply.
June 12, 2024 at 9:07 am #15730073
Paola Mendiburu Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Madrid (GMT+02:00)	I will let you know when I have news.
July 3, 2024 at 9:59 am #15882998
lauriJ-2	Hi, haven't heard from you for a long time. Just wanted to kindly remind about our issue and learn if there are any updates? We've also faced with complete break of the fields translation on this demo page: hidden link Origin page: hidden link
July 4, 2024 at 2:44 pm #15892884
Paola Mendiburu Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Madrid (GMT+02:00)	Hi there! We need to access the database or to download a copy of the staging site so second tier can investigate the issue. I see that installing php adminer is not possible in your site and also I had problems downloading a copy with duplicator. I see that I cannot access now the staging site hidden link Could you please allow us to install plugin adminer to have access to the database or to be able to download a copy?
July 11, 2024 at 8:17 am
July 12, 2024 at 8:50 am
July 12, 2024 at 12:52 pm #15942590
lauriJ-2	Hi, I've finished the migration, but it doesn't seem to migrate the website because I can see the basic twentytwentyfour theme activated and dummy data by the link you've provided. Please, check from your side and let me know if something went wrong. Also, there was other setting options for the migration, for example: Where do you want to migrate your site? "Cloudways Flexible" or "Cloudways Autonomous" The full list of the values that are required you can find on the screenshot attached. Maybe it has some updates, and you would like to update your message template or manuals. Thanks.
July 15, 2024 at 10:51 am #15953755
Paola Mendiburu Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Madrid (GMT+02:00)	Thanks. I see the website migrated. I will work on that in order to escalate to the second tier.
July 16, 2024 at 4:18 pm #15961464
Paola Mendiburu Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Madrid (GMT+02:00)	The issue has been escalated to the second tier. The only way that it works is changing the name of the subtitle field so we are investigating.
July 17, 2024 at 8:04 am #15964608
Paola Mendiburu Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Madrid (GMT+02:00)	The problem is that you use "subtitle" on various groups as a field name. If you use the same Field Name with more than one custom field, you may not see all your field values available for translation in the Advanced Translation Editor. Each field name needs a unique value to be translatable with the translator editor. So you will need to change the name for the field name.
July 17, 2024 at 11:24 am #15965810
lauriJ-2	Hi, thank you for your fast reply! Could you please specify the field we should rename? Are you about the Block: Text, "key": "group_5f16774bdd841" 1. Layout field: "key": "layout_5f96f59dec0df", "name": "subtitle". 2. Text Field: "key": "field_5f96f5a8ec0e0", "name": "subtitle". ? In case if we'll change the layout name to "subtitle_layout", for example, it will work? But it worked previously and still work for other fields like (the same group): 1. Title: 1.1 "key": "layout_5f96f56ba96e1", "name": "title", 1.2 "key": "field_5f96f57eec0de", "name": "title", and 2. Button: 2.1 "key": "layout_5f9700c0009e8", "name": "button", 2.2 "key": "field_5f9700c6009e9", "name": "button", Should we also rename those fields to "field-name_layout" for example? Thanks.
July 17, 2024 at 12:36 pm #15966234
Paola Mendiburu Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Madrid (GMT+02:00)	I have changed for the subtitle field from acf and it works (as it was the one having problems), but it will be great if you can have an unique value for each field.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.