Group & Clone

Group#

A Group field bundles sub-fields under a single name, useful for values that belong together, like a call-to-action with a label and a url. Editors see the sub-fields as one visual block; templates read them as one array.

Storage follows the prefix pattern: a group named cta with sub-fields label and url stores its values as cta_label and cta_url.

Clone#

Clone is part of Ultivo Toolkit Pro; Group above is in the free version. A field group that already uses a Clone field keeps its content untouched and shows a locked field until Pro is active. See pricing.

A Clone field pulls existing field definitions into the current group, so shared fields (SEO settings, button options, spacing controls) are defined once and reused everywhere. Its settings:

• Fields / Groups to clone: one or more field groups (all their fields) or individual fields.
• Display: Seamless renders the cloned fields as if they were defined in place; Group wraps them in a visual block.
• Prefix Field Names: store the cloned values under {clone_name}_{field_name} instead of the original names, so the same set can be cloned more than once into one group without collisions.
• Prefix Field Labels: prepend the clone's label to each cloned field's label in the admin.

Clones stay live: change the source field group and every place that clones it picks up the change.

Reading values in templates#

A group value is an array keyed by sub-field name:

$cta = ultivo_get_field( 'cta' );
if ( $cta ) {
    printf(
        '<a href="%s">%s</a>',
        esc_url( $cta['url'] ),
        esc_html( $cta['label'] )
    );
}

A clone reads the same way: request the clone field by its own name and you get an array keyed by the cloned field names: ultivo_get_field( 'hero' )['seo_title'] for a clone named hero. In the database, Prefix Field Names decides whether the underlying meta keys are the original field names or hero_-prefixed ones.