ACF Fields

When you declare a field through ACF_Builder (title(), text(), wysiwyg(), link(), image(), etc.), the system decides whether to expand it into a multilang group. Reading via get_field('heading') always returns the active-language value automatically — no special helper required.

Auto-applied types (no extra config)

Become multilang automatically when Multilang is ON:

• text
• textarea
• wysiwyg
• link

// With multilang ON, this declaration becomes a multilang group automatically:
ACF_Builder::text(['name' => 'heading', 'label' => 'Heading'])

Opt-in types

Not expanded automatically — pass 'multilang' => true explicitly:

• image
• gallery
• url
• file

// Image NOT multilang by default
ACF_Builder::image(['name' => 'logo'])

// Multilang image (opt-in)
ACF_Builder::image(['name' => 'hero_bg', 'multilang' => true])

Unsupported types (passthrough)

Never expanded:

• repeater, group, flexible_content — containers (their sub-fields can be multilang)
• spacing, bg_color, tab, note — structural fields with no translatable content
• select, radio, boolean, number, date, time — values are codes/data, not text
• relationship, post_object, taxonomy — references to other posts, not content

The multilang argument

Value	Effect
true	Force expansion to multilang (useful for image/gallery/url/file)
false	Force NO multilang (useful for explicit opt-out)
omitted	Auto-apply by type

The multilang_skip_primary argument

ACF_Builder::title(['name' => 'name_ml', 'multilang_skip_primary' => true])

When true: skips the sub-field for the primary language. Used when the default-language value already lives in a native WP field (post_title, term name, _thumbnail_id), to avoid visual duplication in the editor.