Hello, I was able to find a workaround on my side. I found out that it was happening only on fields that weren’t directly drawn on page loading (e.g, fields that only appear if some conditions are matched).
So I choosed to draw by default all fields, and filter them after when the user select his options/categories, etc. This is not perfect but it works
OK here are more information to help for the debugging.
From what I can see on network capture, the ACF datas aren’t sent to the server at the first post save, except for the fields validation.
So basically, the network activity that I see when I push the publish button is something like:
Client :
-POST /wp-admin/admin-ajax.php …. action=acf/validate_save_post (the ACF fields are here)
Server :
-Ok valid, success
Client :
-POST /index.php/wp-json/wp/v2/posts/<id>?_locale=user (in data, there are the post title, categories, status, but no ACF fields…)
Server :
-OK, post created
Client :
POST /wp-admin/admin-ajax.php action=acf/ajax/check_screen
Server :
-Some informations
And that’s all. In this configuration, the ACF data are never sent to the server, except for the validation. So it can be a beginning of the investigation here.
Hello,
Did someone else encounter the same issue ? I’m pretty sure that we are not the only one.
So I also checked the database. The datas from ACF are not saved on the wp_postmeta table on the first publishing.
Hello roodoggy,
Thank you for your answer. I checked the pcap dumped, and I have the same behaviour than you
One more detail : the MySQL version is 15.1
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 use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.