Home›Support›English Support›[Resolved] Custom Fields datas are not showing in the Secondary language version
[Resolved] Custom Fields datas are not showing in the Secondary language version
This thread is resolved. Here is a description of the problem and solution.
Problem:
The client was having issues to set the correct translation preferences for his ACF custom fields.
Solution:
I recommended him to start by applying the "Same fields accros languages" multilingual mode. That mode set default preferences depending on field types and will work perfectly in most cases. Then if the client needs to adjust the translation preferences for few fields, he can do so by switching to the "Expert" mode.
- Go to "ACF > Field groups" and edit your group
- In the "Multilingual configuration" select "Same fields accros languages"
I have custom field that I created (I named it as header & Menu Settings that shows in each WP editor page) which allows me to assign different logo image and change color of the menu depending on which page I want to change
In my homepage, I use a different logo (white version, white menu text etc) then the rest of the pages (rest of the pages has default black logo, black menu text etc)
In the default language homepage, everything works fine.
But in the Turkish version, here is a LOCK symbol and I can not edit the Custom Fields.
Even the custom field gets the correct data from english version, it is not reflected to frontend..
Welcome to the WPML support forum. Just to make sure to understand the issue. You created a field group with ACF and some of the fields have a lock in the translated page right?
Few things here:
- Depending of the translation preference of your field you will have a lock. For example, if the translation preference is "COPY", you won't be able to translate/change it.
- Second, you shouldn't translate/change the value of that field in the default WordPress editor.
Let me explain:
- In "ACF > Field Groups > Your group" you have 3 multilingual options > Same fields: The most common option, WPML will automatically set your translation preferences. If one field is set as "COPY" but you want to translate it, then you should move to the "Expert" mode to fine tune preferences. > Different fields: This one has to be used when you edit your translations with the WordPress Editor. Because here you're not using our translation editor, all fields will be set as "COPY ONCE" to create them in the first place and then you will be able to translate them if needed in the WordPress Editor. > Expert: To fine tune translation preferences if you're not happy with the default ones from "Same fields". I would recommend to start with "Same fields" first and then move to "Expert" if needed.
What's next?
Now that you have a better understanding, I think you have to decide either if you want to do your translation in our editor ("Same fields" or "Expert") or if you want to translate in the WordPress Editor ("Different fields").
If it's not clear enough or if you need more help, don't hesitate to give me as much detail as possible on your workflow that way I can better understand the issue.
Thank you for this detailed explanation. I did what you adviced and change one of the field groups multilingual options to > Same fields
And now I do not see the 'lock' symbol. So it seems its resolved.
My question is;
Its been sometime since I checked these WPML settings. I have other Field Groups that I created when I created ACF.
All of them is selected as 'EXPERT'
What I do not understand is; are we talking about the 'name of the custom fields' or are we talking about 'the values of the custom fields' when we talk about the translation?
I mean what does 'translation preference of your field' means actually..
Sorry if my questions seems dumb but WPML is really difficult to understand for someone like me who is definitly not a technical person but tries to do something 🙂
I'm glad we solved the issue!
We're talking here about the translation of the field value.
To give you quick recommendations:
- "Copy" or "Copy once" for special fields "Repeater" and "Flexible".
"Copy" is you want the exact same repeaters and structure, else "Copy once"
- "Translate" for all the fields you want to translate such as texts, WYSIWYG etc...
- Use "Copy" if you don't want to translate the field but keep the same value, for example for colors, true/false, images etc...
As I mentioned already I would recommend to start with "Same fields" and then if you need to change something, you can move to expert and do the change.
For example: with "Same fields", all your text fields will be translatable but maybe you want to copy one of them because it doesn't need a translation (think of a person's name, that will be the same in all languages). In that case, switch to "expert" mode and only change the translation preference from "translate" to "copy" for that specific field.
