Skip Navigation

Home › Support › English Support › [Closed] WPML is not correctly registering and translating a WYSIWYG field that is deeply nested within multi...

[Closed] WPML is not correctly registering and translating a WYSIWYG field that is deeply nested within multi...

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
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+02:00)

This topic contains 1 reply, has 0 voices.

Last updated by Dražen 3 months, 1 week ago.

Assisted by: Dražen.

Author Posts
February 26, 2025 at 9:40 pm #16753503

peter-rF

Background of the issue:
I am trying to translate a page containing content built with ACF flexible content and clone fields. The structure includes a flexible content field ('content_blocks') with a layout ('rich_content_block'). Inside this layout, a clone field ('rich_content') pulls in fields from another field group. Within that field group, another clone field ('intro_block') pulls in fields from a third field group. The third field group contains the WYSIWYG field ('intro') that needs translation. All fields are set to 'Translate' in WPML's settings. This project is currently only local, so I'm unable to provide a link to a specific page. Here's an example of the XLIFF output that I see: <code> <trans-unit resname="Content Blocks 0" restype="string" datatype="html" id="field-content_blocks-0-0" extradata="{"unit":"Content Blocks 0","type":"custom_field","group":"Custom Fields","group_id":"Custom_Fields-0"}"> <source><![CDATA[rich_content_block]]></source> <target><![CDATA[rich_content_block]]></target> </trans-unit> </code>

Symptoms:
The content of the 'intro' field is not included in the XLIFF file when exporting the page for translation. The XLIFF file only shows the layout names, but not the actual content of the 'intro' field. The field is also missing from the list of translatable custom fields in WPML's settings (WPML -> Settings -> Custom Fields Translation).

Questions:
Why is the 'intro' field not included in the XLIFF file?
Why is the 'intro' field missing from the list of translatable custom fields in WPML's settings?
February 27, 2025 at 7:45 am #16754256

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

thanks for contacting us.

1)

- Make sure you have a backup.
- Disable all other plugins and leave active only WPML plugins and ACF
- Switch to WP default theme
- Check if the issue still happens
- Check if the issue still happens on a new test page

2)
What is the translation mode for these ACF field groups? If it is expert try setting to the same field across languages mode and check if the issue still happens.

Let me know how it goes.

Regards,
Drazen

The topic ‘[Closed] WPML is not correctly registering and translating a WYSIWYG field that is deeply nested within multi…’ is closed to new replies.