Images and repeater fields are not displaying in secondary languages

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.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	9:00 – 14:00	-
-	15:00 – 18:00	15:00 – 18:00	15:00 – 18:00	15:00 – 18:00	15:00 – 18:00	-

Supporter timezone: Asia/Dhaka (GMT+06:00)

This topic contains 2 replies, has 2 voices.

Last updated by Prosenjit Barman 11 months, 1 week ago.

Assisted by: Prosenjit Barman.

Author	Posts
July 22, 2024 at 3:14 pm #15987650
luigiK	Background of the issue: I had my secondary languages translated independently. Initially, the images and repeater fields were showing. I am following this doc https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/, and I chose 'Same fields across languages' on the ACF field option. I want to be able to edit the repeater fields and images across the secondary language. Symptoms: Images and repeater fields are not displaying in secondary languages. It shows a padlock sign on top and when you hover, it shows 'This field value is copied from the default language and will be kept in sync across languages.' Questions: How do I edit the repeater fields and images across the secondary language?
July 23, 2024 at 3:17 am #15990003
luigiK	I have attached an example of an image and repeater fields in its primary language and secondary language. This affected all the pages, they were editable previously. I want to be able to edit repeater fields and image alt in all languages. I upgraded Advanced Custom Fields Multilingual plugin to 2.1.3 yesterday because i was trying to edit the image alt text of secondary languages which led to "Fatal error: Uncaught TypeError: Illegal offset type in isset or empty" and was fixed by following this link. https://wpml.org/errata/advanced-custom-fields-fatal-error-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in/
July 24, 2024 at 4:38 pm #15999638
Prosenjit Barman WPML Supporter since 03/2023 Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00)	Hello There, Thanks for contacting WPML Support. I understand that certain fields aren't manually editable in other languages. This issue occurs because the Translation option for the field group is set to 'Same fields across languages'. This setting ensures that the custom field data are synchronized across languages, preventing manual editing of the fields in other languages. For more details about the setting, please check this link: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#using-same-fields-across-languages To be able to use a different image per language, please check this guide and I hope you'll get a clear idea of the process. However, if you want the repeater field data to be different in each language or if you want to manually set them for each language version, you can change the translation mode for the field group to 'Different fields per language' or 'Expert'. Please refer to the guides below for more details. - Different field per language: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#using-different-fields-across-languages - Expert: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/ If you choose the expert mode, you'll have the option to manually change the translation preference for each field. To manually update the fields in other languages, set the translation preference for the fields to 'Translate' and proceed to translate the page again. I hope the information above helps. Please feel free to let me know if you need further assistance or clarification on any particular point. I will be happy to help. Best regards, Prosenjit

The topic ‘[Closed] Images and repeater fields are not displaying in secondary languages’ is closed to new replies.