These limitations are found in edge cases when using clone fields within a repeater or flexible content field. The clone field contains a few limitations. Fields: A field group called ‘Button’ described above.Note that these settings will essentially replace the clone field with the selected fields:
This example shows how to load a clone field value with the following default settings. The ‘Button’ field group contains 2 fields called ‘text’ and ‘url’. Some of the following examples use a clone field called ‘main_button’ which is cloning a field group called ‘Button’. If using the ‘Group’ display setting, you may also load all cloned values as an array by loading the ‘Clone field’ itself. Loading the value of a cloned field is the same as loading a normal field. Eg: ‘hero_button_text’, ‘welcome_button_text’, etc. You could clone a group multiple times on 1 edit screen but have them save data with different names. Very useful when using the ‘Group’ display. Similar to the above, but will modify the field’s name. You could name your clone field ‘Hero’ and have it prefixed to all selected fields like ‘Hero Button Text’, ‘Hero Button URL’, etc. Very useful when using the ‘Seamless’ display. This setting will modify all selected fields labels and prefix the current clone field’s label.
Very useful to re-use an existing group or ‘modules’ such as a group containing ‘button’ settings (used in following examples).
It can replace itself with the selected fields (seamless) or display the selected fields as a group of sub fields. The clone field may be used in one of two ways. This field group is then ‘cloned’ when a button is needed. A good example of this can be seen with the screenshots below where a single field group is created for ‘Button’ information. You may also select one (or more) field groups making it possible to load in ‘module’ groups.
It does not duplicate any fields in the DB, instead, it loads and displays the selected fields at run-time. The clone field allows you to select and display existing fields.