Excellent find, timternet! That should definitely help debugging. If they are really looking into it. This is so annoying I may have to go through the source and fix the bug myself.
@John Huebner It most definitely works and I couldn’t find any other way.
I tried creating a simple Yes/No checkbox. I created a field type “Checkbox” and entered the choices “Yes” and “No”. This doesn’t make a single checkbox like you would think. It makes a “Yes” checkbox and a “No” checkbox. What I wanted was a checkbox where true = “Yes” and false = “No”. Instead, I have to uncheck “Yes” and check “No” to change the saved value. The values display correctly everywhere on my site, but filtering is a problem.
The values stored in the DB are ‘a:1:{i:0;s:3:”Yes”;}’ and ‘a:1:{i:0;s:2:”No”;}’.
I’m sure you can see why the compare ‘LIKE’ works with the value ‘Yes’.
In retrospect, I should have just used a radio button.
@cvolpe12 No update yet. Currently, I enter all my data except for the advanced custom fields. Then I hit Save Draft, F5, then enter the custom fields data, and finally publish.
It’s a bit annoying but only takes an extra second.
I came here to report the exact same issue! Everything was fine until recently. Perhaps the last WordPress update broke something? I am using the same versions as you.
Everything appears to be sending correctly and the response looks correct on the initial save, but the data is not saved.
/wp-admin/admin-ajax.php?_fs_blog_admin=true
Request
acf[field_5fc3aad04255a]: 10
acf[field_5fc7261aae126]: 2021
action: acf/validate_save_post
nonce: e31d46a48c
post_id: 4987
Response
{“success”:true,”data”:{“valid”:1,”errors”:0}}
The update sends the exact same data to the exact same endpoint and gets the exact same response, but it works.
