Group and Clone fields hold other fields. WPML copies the container and translates each sub-field by its own preference: text is translated, images and numbers are copied. For a Group, the preference sits on each sub-field. For a Clone, it comes from the field group you clone, also when the clone prefixes the field names. This guide shows where to set the preferences, what the translation gets, and what Copy once does to a cloned field.
With Private Translation Cloud (PTC) (opens in a new tab), WPML's AI translation, the sub-fields are translated when you publish the post, and you do not need to review anything.
For the types of fields and the translation options, read the ACF documentation hub. Repeater and Flexible Content fields have their own guide.
What You Need
- Advanced Custom Fields PRO. Group and Clone are PRO fields.
- WPML and WPML String Translation.
- ACF Multilingual (ACFML), the add-on that connects ACF fields to WPML.
In our example, a tour site has a Tour details field group on its tours:
- A Group called Price and dates holds a Price (a number), a Currency (a select), a Season (text) and Notes (a text area).
- A second field group, Call to action block, holds a Button text, a Button URL and a Note. The tour's page sections clone it with a Clone field, shown as a group, with Prefix Field Names on.
What WPML Translates in a Group or Clone Field
With a field group on Same content in every language, translated, the recommended option, every field gets the preference of its type. The container is copied. Each sub-field follows its own type:
| Type of sub-field | Preference | What the translation gets |
|---|---|---|
| Text, Text Area, Wysiwyg Editor, URL, Link | Translate | The text in the visitor's language |
| Number, Select, Checkbox, Radio, True / False, Date | Copy | The original's value, kept in sync |
| Image, File, Gallery | Copy | The original's media, kept in sync |
| Group, Clone (the container) | Copy | The same sub-fields, each by its own preference |
In our example, the season and the notes are translated, and the price and the currency are copied. In the cloned block, the button text and the button URL are translated, and the note too.
Where the Preference of a Sub-field Is Set
- Group field: on the sub-field itself, in the field group that holds the Group. With Same content in every language, translated, it follows the type. With Expert, each sub-field shows a Translation preferences control.
- Clone field: on the fields of the field group you clone, in that group's own settings. The clone has no WPML setting of its own. Set the cloned group once, and every post that clones it follows, with or without a prefix.
A cloned group is often inactive, so that its fields show only through the clone. Its Multilingual Setup box still rules its fields. Open it from ACFField Groups under Inactive.
What You Need to Do
Check the field groups once. Go to ACFField Groups and open the group that holds your Group field, then the group you clone. Each Multilingual Setup box should show Same content in every language, translated. If not, click Change option and choose it.
With Translate Everything On: Nothing
If you use PTC and your site is on Translate Everything, WPML translates each tour when you publish it, the Group's and the Clone's text sub-fields included. You do not need to do or review anything. A later change is translated too.
You set it up in the Translate Everything Automatically box at the top of WPMLTranslations. Read how to translate everything automatically.
With Translate Everything Off: Send the Post from the Translation Dashboard
- Fill in the fields and publish. In our example, the tour Dolomites hiking week has its price, currency, season and notes, and a call to action in its page sections.
- Open the Translation Dashboard. Go to WPMLTranslations. Expand the section of your post type and check the box next to the post.
- Choose automatic translation. Under Translate your content, choose Translate automatically for each language.
- Choose Publish without review. Under What would you like to do when WPML finishes translating your content automatically?, keep Publish without review (Recommended).
- Send it. Click Translate content. A popup confirms Sent for translation.
The translation completes in minutes and is live. Read more about the Translation Dashboard.
See the Translated Fields
Open the translated tour in the WordPress editor, from the post list in that language:
- The Group shows its season and notes in that language, with the original under each.
- The price and the currency are the original's, with a lock icon. They are copied from the default language and kept in sync.
- The cloned block shows its button text, button URL and note in that language, each with the original under it.
The Expert Option: One Sub-field with Its Own Preference
Use Expert when one sub-field must behave differently from its type. For a Group, put the group that holds it on Expert. For a Clone, put the cloned field group on Expert; the clone follows it.
- Open the field group in ACFField Groups and choose Expert in Multilingual Setup.
- Open the sub-field and choose its Translation preferences: Translate, Copy, Copy once or Don't translate. The legend under the choices says what visitors see and where you edit the value.
- Save the field group. When posts already have translations, WPML asks what to do with them. Only apply to new translations leaves them as they are. Also update the existing posts marks their translations as needing an update, so the next translation applies the new preference.
What Copy Once Does to a Cloned Field
A sub-field on Copy once starts as a copy of the original. After that, each language keeps its own value. When you change the original, the translation keeps what it has, also after the next translation. You change it yourself, in the translated post.
If You Want to Change a Translation
You do not need to check anything. If you want to change a translated sub-field, do it this way:
- Open Translation Jobs. Go to WPMLTranslationsTranslation Jobs.
- Click the pencil on the job's row. Its title is Edit Translation. The Advanced Translation Editor opens with an Advanced Custom Fields (ACF) box and one inner box per field group. The Group's sub-fields sit in their field group's box, tagged Price and dates / Season. The cloned sub-fields sit in a box titled by the cloned group, Call to action block, tagged with their own labels, without the clone's name or prefix. Copied sub-fields have no segment.
- Edit what you want. Change the segment in the editor.
- Click Save and Complete. Always finish this way, even with no change. Otherwise the job stays In progress.
When you use PTC, it learns from your edits, so you do not need to keep making the same corrections.
If It Looks Wrong
- A cloned text shows the original in every language. The field in the cloned group is on Copy. Open the cloned field group and set that field to Translate; with Also update the existing posts, the next translation fills it.
- A sub-field is missing from the translation editor. Its preference is Copy, Copy once or Don't translate. Only Translate sub-fields have a segment.
- A Copy once sub-field did not change with the original. By design: after the first copy, each language keeps its own value. Edit it in the translated post.
For Developers
ACF stores a Group's sub-field under <group>_<sub-field>, in our example price_and_dates_season. A Clone with Prefix Field Names on stores <clone>_<field>, here cta_button_text. Without the prefix it stores the cloned field's own name.
WPML reads the preference from the cloned group's field either way.
For a field group registered in PHP or Local JSON, set wpml_cf_preferences on the cloned group's fields, as on the hub page. To change what WPML does with a field, use the ACFML hooks.