I have added a new ACF repeater field, but when edit a field and save the post in the original language, the field is not translated, or copied (I tried both options), to the secondary language. I have the field group set to "same fields across all languages". It was not initially set, as I added ACF Multilingual after adding the field initially.
Here are my steps:
1. Field added (original language only)
2. Posts updated with content
3. Added WPML multilingual (not sure if this matters)
4. Duplicated field (secondary language)
5. Field does not force translation
Also, I did notice that despite the field group set to "same fields across all languages", in the "WPML -> Definitions" the field is set to "copy" and cannot be changed (the "copy" function doesn't seem to work either).
Based on the WPML Debug Info, I've noticed that the translation preference for the ACF File Group post type is currently set to "Translatable," which we don't recommend. Having duplicated/translated field groups can lead to complications in the translation process. If you're considering altering the translation preference for the field, please follow the steps below, which should assist in addressing the issue.
- Delete the translated field group and set the translation preference for the "acf-field-group" post type to "Not Translatable" by following the information outlined here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/#field-group-translation-settings
- After that, navigate to "ACF → Field Group" and open the Field group which includes the specific field.
- At the top, there is an option to modify the Translation mode. Click on the "Change Option" link there.
- Choose the "Expert" mode from the available options.
- After selecting "Expert" mode, scroll down to the field you want to change the translation settings for.
- Change the translation preference for the field to "Translate' and save your changes.
Please let me know if that helps to solve the issue or if you need further assistance in this matter. I will be happy to help.
Thank you. I followed the steps and removed the field groups in the secondary language, and set field group post type to "do not translate". I changed the field group translation mode to "expert mode" and set the field to "translate".
The result is as you can see in the images. As you can see, when I look at the field in the primary and secondary language, they are different. It doesn't seem to matter whether I set the field to "translate" or "do not translate".
What I want is for the field to always be the same across languages. It doesn't even need to be translated. But for some reason, whatever change I make to the primary language on that field doesn't seem to be affecting the secondary language.
If you want the selection to be the same in translation as well, the translation preference for the field has to be "Copy". Otherwise, the value will not be copied to the translation.
After looking at the screenshots you shared, I noticed that within the "Project Image" repeater field, there is a Taxonomy Type field named "Tratamentos" used for selecting the taxonomy terms.
Please note, that we have traced an issue with the Taxonomy type field where the terms selections are not being copied to the translations. This issue has been forwarded to our development team for detailed examination and resolution.
Currently, the temporary solution to address this issue involves marking the taxonomy as translatable and then translating the meta-information. During the translation process, it's necessary to include the ID of the translated taxonomy, instead of saving the ID of the default taxonomy in the translation. Please check the solution explained here: https://wpml.org/forums/topic/acf-field-type-taxonomy-translation-option-copy-not-working/#post-8173547
I'm going to add this ticket to our development ticker to prioritize the issue. While we cannot provide an ETA for a permanent solution at this moment, rest assured, you will be promptly informed as soon as there are any updates.
Please let me know if you need further assistance or clarification in this matter. I will be happy to help.
I've attempted to set the field type "gallery image" to Copy. That doesn't seem to do anything. Is the expected functionality that the data is copied instantly when publishing in the original language, or do you need to go through translation process? Either way, this is what I did:
1. In ACF, I set Gallery Image field to Copy
2. In ACF, I set Tratamentos field to Translate
3. Note that the repeater field group is set to "do not translate"
4. In the post, I added a new Gallery Image, checked off Tratamentos, and published.
5. Approved translation
6. The gallery image is not added in the secondary language, nor is any taxonomy changed.
So the issue isn't just the taxonomy, but also either the repeater field, or the image. Please verify that the settings in steps 1,2,3 are correct.
As to your last point, the terms have no additional metafields to translate. Would you be able to provide documentation on adding translatable metafields?
Based on the details you've provided, it appears that the "Project Image" repeater field is set to "Do Not Translate," which might be why its information isn't being copied to the translations. Could you please change the translation setting for this repeater field to "Copy" and then see if the information carries over after you update the translation?
Regarding the issue with the Meta field not being visible, navigate to "WPML > Settings > Custom Term Meta Translation," adjust the translation setting for the term meta field to "Translatable," and save your changes. The Meta fields should become visible after this adjustment.
Please let me know how it goes. I will be happy to help if you need further assistance in this matter.
Best regards,
Prosenjit
The topic ‘[Closed] Some custom fields in field group do not translate’ is closed to new replies.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
