[Resolved] I can’t save values to some custom fields after the last update

[Author]

Posts

[AtefR7377]

Hi,
I have several custom fields groups that appear in several custom post types.
My system was working 100% correctly and I have thousands of posts in each custom post types.

After the last plugin update, I found out that I can't save values to some custom field groups. When I input the values in a new or existing post and click "update" , the page reloads with no values in the custom fields.

I tried using 2 admin users from 2 different browsers. same results. I don;t have caching plugins, so there is no caching happening.

I also deactivated all plugins except Toolset and WPML, still same results.

The custom field group called "Post Type Filteration" is a radio buttons field. it is attached to "Books" and "Sermons" CPT. for posts that don't have any choice (i.e. new posts), when I choose any option, then update the post, I see no choices at all.
This happens in both Books and Sermons CPT posts.

For existing posts with a certain choice, if i changed it and update the post, the old option still remains as if I didn't do anything.

for the custom field called "Schema Book Microdata", (attached to "Books", "articles" and "magazines CPTs), it has several single line text fields. when I add new text in these fields, nothing gets saved, and when i edit text in existing fields, the old text comes back.

The strange thing is that there is a custom field group called "Schema Person Microdata" that is attached to "Persons" CPT is working! i tried adding to these fields, deleting from them, and all working..

So the problem is a mixed bag.

Please note that the custom field groups that don't work are not new. the have been filled in several thousand times before.

can you please check to see why this happened after the last update?

I provided login details and debug information.

thanks.

[Shane]

Hello,

Thank you for contacting our support forum.

Our development team is aware of this issue and have worked on a fix planned for version 3.0.4 of types.

Thanks,
Shane