Ranabikram Field Copy for ACF

FAQ

Does it work with ACF PRO?

Yes. It works with both the free Advanced Custom Fields plugin and ACF PRO. It detects ACF at runtime, so it does not block activation if you run the PRO build.

Does copying a field also copy its saved values?

No. It copies the field definition into the target group, the same way ACF’s own Move and Duplicate work. Existing post/page values are not transferred.

Does it copy sub-fields?

Yes. Repeater, Group and Flexible Content fields are copied together with all of their sub-fields, each getting a fresh field key.

What happens if the destination group already has a field with the same name?

The copy is automatically given a unique field name within that group (for example email becomes email_2) and its label is suffixed with ” (copy)”, so the two fields never overwrite each other’s values on save. The original field is left untouched.

Could a copied field still clash with a field in a different group?

Uniqueness is enforced within the destination field group. If you copy a field into a group that is displayed on the same edit screen as another group that already uses that field name, the two can still share a meta key and overwrite each other on save — this is a property of how ACF stores values by field name, and it applies to ACF’s own Move action too. If you copy a field into a group shown on the same screen as its source, review the copied field’s name afterward and rename it if needed.

Where does the Copy link appear?

In the field’s action row inside the Field Group editor, next to Edit, Duplicate, Move and Delete.

Why does a copied field’s conditional logic sometimes not work?

If a field’s conditional logic refers to sibling fields that do not exist in the destination group, those rules will have nothing to point to. Review the conditional logic on the copied field after moving it to a different group.