Thanks, that worked also for me.
I have the same problem. Good reason to use HTML in label, and the solution of replacing the entity code did not work out for me. There should be an option at the field level.
Also, the “allow html” in the message settings seems not to work anymore.
I’d use the “update” from my sql on the wp-postmeta to change the meta_value of the fields, to the new field key. Make a backup before 🙂
Update wp_postmeta set meta_value = 'new field key' where meta_value='old field key' and substr(meta_key,1,1) = '_'
Note that the meta value has to be in the form field_llnmc9c86353a
The second condition is just to check where are dealing with the right meta
Hi, adding a subfield to an already existing group is rather simple: you just add a property in the field declaration, telling which is the parent group :
'parent' => 'group_1'
See in details here : https://www.advancedcustomfields.com/resources/register-fields-via-php/ under “Individual”
