[Closed] Post is not translated.

I logged in to your site.

I want to be careful as it is a live site, so can I get some more information from you.

When editing posts it's not the normal editor, the content section appears to be replaced by a "Body text" block that has sub-sections.

Where is that from?

Your theme? A plugin? Custom coding?

OK, can you confirm if you have prepared the custom blocks for translation as described in this document?

https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-acf-blocks-with-wpml/

If so, can you let me know where you have added the code to register your custom blocks?

I'll want to take a closer look and possibly set up a test site that uses your custom block so I can go through the steps of translating content made with it.

Thanks for that. The block is registered with code, but the ACF fields are added within the UI, not registered programmatically.

I tried a test translation of a draft blog entry, and the initial translation worked as expected, but then when I went to edit the translation, the updated title was preserved but the updated text was not.

The user you have created for me doesn't seem to be an administrator, I cannot see the UI for ACF in the back end to review the settings.

Is it possible to change that?

That worked, thank you.

The earlier screenshot you shared of the field group was for the wrong field group (assigned to the block BG Image and Text, the actual block in question is Body text).

Looking at the correct field group and comparing it to the field group you shared does highlight what I think is the problem, though.

The field groups contain fields with the same names (generic field names like title, and text).

In the screenshot I'm highlighting a warning from the documentation I linked to before. (The problem that arises is not exactly the same as warned of, but I think the cause is the same.)

I suggest you review the fields in your field groups to ensure they have unique field names. I suspect you will have to re-save posts before translating them.

Can you please try that and let me know how it goes.

I'm not sure, so I'm asking the ACF specialists in our compatibility team.

But in the meantime I'd recommend you have a staging site prepared where you can try this before attempting the same on your production server.

That's not going to be a problem.

I have some clarification from my colleague.

The issue when using the same field name for different fields across different field groups only relates to saving the translation preference.

If you have different translation preferences for the same field, whichever one happened to save last will apply to all of them.

I can see that the Block: Accordion field group contains a "title" field, whose translation preference is set to Copy, while in other field groups the same field is set to Translate, so that is not going to work correctly everywhere.

You have a lot of field groups so I didn't go through checking them all, but you should review them and double-check that where you have re-used the same field name across different field groups, that they all have the same translation preference.

If some of them should have different translation preferences, then you will need to re-name the fields.

That should not have any effect on your actual content (original or translated), but will affect what happens during translation.

Pay particular attention to the "text" field, which seems to be the one causing trouble in my testing.