I’ve seen this issue before when the values have been saved to the ACF field (to the DB) outside of ACF (not adding them through acf input) and doing so by either using
update_field with the field name or using another function like
update_post_meta. If you’re saving the values programmatically or in some other way you should always use
update_field with the field key.
The reason for this is because using the field_name for a meta value that does not yet exist fails to create the corresponding field key. If the field already exists tho the field key also already exists and it’s fine to use the field name.
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!