All ideas

Clone fields not (always) translated

Below is the JSON for a simple example with 2 field groups: a clone field that clones a text field and is attached to post type 'page'. When I AI-translate the page, the text in the clone field is not translated. I also added a normal text field to the clone field group, which gets translated. In a different case it works: I also use clone fields in ACF flexible content, as I don't add the fields directly in the layout settings, but rather add a clone field that clones the needed layout fields. That's all translated without problems. But if there are sub-fields, the same problem as above appears. I use the latest versions of WordPress and the plugins. Please let me know if you need more information. [ { "key": "group_6717dc71e99cf", "title": "Text Field", "fields": [ { "key": "field_6717dc7298b95", "label": "Text", "name": "text", "aria-label": "", "type": "text", "instructions": "", "required": 0, "conditional_logic": 0, "wrapper": { "width": "", "class": "", "id": "" }, "default_value": "", "maxlength": "", "allowinbindings": 0, "placeholder": "", "prepend": "", "append": "" } ], "location": [ [ { "param": "post_type", "operator": "==", "value": "post" } ] ], "menu_order": 0, "position": "normal", "style": "default", "label_placement": "top", "instruction_placement": "label", "hideonscreen": "", "active": true, "description": "", "showinrest": 0 }, { "key": "group_6717db376eca8", "title": "Clone Field Test", "fields": [ { "key": "field_6717dc567bba0", "label": "Clone Text", "name": "clone_text", "aria-label": "", "type": "clone", "instructions": "", "required": 0, "conditional_logic": 0, "wrapper": { "width": "", "class": "", "id": "" }, "clone": [ "group_6717dc71e99cf" ], "display": "seamless", "layout": "block", "prefix_label": 0, "prefix_name": 1 }, { "key": "field_6717df71bbb6f", "label": "Normal text", "name": "normal_text", "aria-label": "", "type": "text", "instructions": "", "required": 0, "conditional_logic": 0, "wrapper": { "width": "", "class": "", "id": "" }, "default_value": "", "maxlength": "", "allowinbindings": 0, "placeholder": "", "prepend": "", "append": "" } ], "location": [ [ { "param": "post_type", "operator": "==", "value": "page" } ] ], "menu_order": 0, "position": "acfaftertitle", "style": "default", "label_placement": "top", "instruction_placement": "label", "hideonscreen": "", "active": true, "description": "", "showinrest": 0 } ]

Activity · 15
hallo
hallo2y
Robbert Vermeulen
Robbert Vermeulen1y
@hallo We just released version 3.1.4 with fixes for complex ACF fields both for posts and terms. Can you please test and let me know.
Robbert Vermeulenmarked this as under-review· 2y
Robbert Vermeulenmarked this as in-progress· 2y
Robbert Vermeulen
Robbert Vermeulen2y
@hallo we released version 3.0.1 with improvements to the clone field. Can you please test and let us know whether your issue is solved. Thank you.
hallo
hallo2y
@robbert_vermeulen thanks for the quick response! I installed 3.0.1 but unfortunately it didn't fix the issue, it behaves in the same way as before.
Robbert Vermeulenmarked this as planned· 2y
hallo
hallo2y
Hi, just wondering if this will get fixed and when. Could you reproduce it? If you can give me a hint how to solve this on my own for now (I'm quite familiar with ACF / PHP), also good. Because as of now we cannot use the plugin.
hello
hello2y
Dear Robbert, I have the same request and problem, as described I also use cloned fields in the ACF Flexible Content Field and unfortunately cannot currently use the plugin. Is there a eta for a fix?That would be really great, because I think the plugin is brilliant.Thank you for your feedback and your work.
Robbert Vermeulen
Robbert Vermeulen1y
@hello We just released version 3.1.4 with fixes for complex ACF fields both for posts and terms. Can you please test and let me know.
hallo
hallo1y
@hello @robbert_vermeulen For some reason the new version does not translate flexible content at all anymore. When I create a translation (the target page does not exist yet) the page gets created with translated title, but all content fields are untranslated. Also the process is very fast, taking 1-2 secs. When i revert to the previous plugin version, it works (but still with the untranslated clone fields issue obviously).
Robbert Vermeulen
Robbert Vermeulen1y
@hallo Hmm that is not good to hear. We are able to translate all types with this update. Can you let me know whether all ACF fields are set to "translate" and not something like "ignore", "copy", "synchronise".
hallo
hallo1y
@robbert_vermeulen Ok, I will test everything thoroughly, perhaps with a minimal setup and let you know. Thanks for your effort.
hallo
hallo1y
@hello @robbert_vermeulen regarding your question to ACF fields setting: I think those options ("translate", "ignore", etc.) are just available in Polylang Pro. I am using Polylang free. Could this be the issue?
Robbert Vermeulen
Robbert Vermeulen1y
@hello @hallo That could be the problem! I tested the translation itself and that works. I already tested with free license, but that was after I created the fields with the pro license. So maybe that is the issue. I will test today with a clean setup and only Polylang free and update the soon.
Robbert Vermeulen
Robbert Vermeulen1y
@hello @hallo I just released version 3.1.5. This update improves how field translations are handled: the system now only checks the translation status of fields when they are explicitly set (via ACF Pro). Otherwise, it proceeds directly with translation. For testing existing translated content, you have two options: Make minor modifications to each field's value to add them back to the translation queue Enable "Force mode" when translating For new content, the translation process of ACF fields should now work smoothly without any additional steps. Please let me know whether this version solved the issue for you.
Robbert Vermeulenmarked this as in-progress· 2y
Robbert Vermeulenmarked this as Completed· 1y
Robbert Vermeulenmarked this as in-progress· 1y
hello
hello1y
@robbert_vermeulen tryed also the new version on the weekend and nothing of the ACF Fields got translated anymore - also not the normal, not cloned - fields. Had the same behavior like @hallo. Thank you for looking at this again 🙏.
Robbert Vermeulen
Robbert Vermeulen1y
@hello Ok thank you for your feedback. Can you maybe provide me with a temporary login to your website so I can investigate. You can send it to info@epicwpsolutions.com thank you in advance!
Robbert Vermeulenmarked this as Completed· 1y

More ideas