Translating Advanced Custom Fields (ACF)

Gato AI Translations for Polylang can translate any custom field created with Advanced Custom Fields (ACF) that stores data in the meta tables (wp_postmeta and wp_termmeta).

You must indicate which meta keys to synchronize and translate, as corresponding to the ACF fields you are using.

​

Defining fields to sync/translate

ACF stores 2 entries for each field:

1. Entry _{field_name} contains internal metadata
2. Entry {field_name} contains the field value

The first entry must be synchronized always.

The second entry must be either translated or copied, depending on the field type:

• Translate text fields
• Copy non-text fields

​

Meta key patterns

ACF stores field data using the following meta key patterns:

• For regular fields: {field_name}
• For repeater fields: {field_name}_{row_index}_{subfield_name}
• For flexible content fields: {field_name}_{row_index}_{layout_name}_{subfield_name}

For example:

• my_text_field
• my_repeater_0_title
• my_flexible_0_text_block_content

You can use regex patterns to match these fields:

• Match all fields: #^[a-zA-Z0-9_]+$#
• Match repeater fields: #^[a-zA-Z0-9_]+_\d+_[a-zA-Z0-9_]+$#
• Match flexible content fields: #^[a-zA-Z0-9_]+_\d+_[a-zA-Z0-9_]+_[a-zA-Z0-9_]+$#

​

Example configuration

Here's an example configuration for common ACF fields: