There are 2 possibilities:
- either that checkbox(es) value is not trivial (it has special characters like <,>,/,\,etc) in the value.
https://toolset.com/forums/topic/custom-field-stopped-working-after-upgrade-of-toolset/
- Or, you have a Parent (related) Posts table in that Post edit screen.
(Means, you have this post type in a post type relationship with another type
For this case I still need to find out what exactly is provoking the issue, as all I know by now is, if you have a Parent Post table in the Edit Screen and a checkbox in the actual edited post, that does not save.
But, it must be related to what fields are present in the related post table, and that, I was not yet able to find out.
My colleague Mohammed had initially contact with a user who has seen that issue:
https://toolset.com/forums/topic/check-boxes-are-not-being-saved-as-being-checked/
On that ticket, these are the thing I found which are not native to a default install and ay cause the issue:
- These fields save 0 to the database.
- The same fields do work on any other post type, this happens only (and as well with new fields) on the post type "Dispatch Request"
- If you use the same fields on any other post type, they work
- Hence, it's this post types setting that break the checkbox.
- There are post relationships with even more checkboxes in there connected to the "Dispatch Request" post type.
==> If you delete these connections the issue is resolved.
I could not yet replicate locally yet, and I as well saw user client did not run the migration yet. which might be related.
As you see, I am aware of the issue only from the user's perspective and was not yet able to determine what exactly provokes this issue.
Maybe I have more luck with your example!
Could you eventually check if:
- removing the post type relationship solves the problem?
- if so, what exact fields in the parent/related post types do you have?
I suspect it is related to having another kind of select fields in a parent post which is not saved, and that overwrites the current post.
But I tried to replicate this and failed too.
So I am still missing a crucial point in replication.
Eventually you can help me to see what I miss, otherwise, the developers are as well on this and we will get to the bottom of it ASAP
PS - I would have logged in to check this all myself but the password is not valid for the user you provided.