Home › Forums › Bug Reports › Programmatically inserting field with update_field() does not at _field_key meta › Reply To: Programmatically inserting field with update_field() does not at _field_key meta
Unfortunately this doesn’t actually seem solve it when I test it out.
If you create a field group
settings, add a field to it
my_settings, when saving via the UI you get a wp_postmeta of
settings_my_settings with a field key like
If you create it programatically via your recommendation:
update_field( 'field_59c383916102a', $some_html, $some_new_post_id );
In the database you instead get
settings_my_settings is needed). This causes then field to be empty when then opening it up in the UI.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We’re hard at work on ACF 6.1, and Beta 1 is now available 🚀— Advanced Custom Fields (@wp_acf) March 16, 2023
This release includes custom post type and taxonomy registration, an improved experience when selecting field types, PHP 8.1 and 8.2 compatibility, and more!
Let’s take a look 🧵https://t.co/Y0WcAT11l4
© 2023 Advanced Custom Fields.