Skip Navigation

[Resolved] The custom fields are not showing up in the backend

This support ticket is created 5 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 4 replies, has 2 voices.

Last updated by Christian Cox 5 years ago.

Assisted by: Christian Cox.

Author
Posts
#1386085
Screenshot (48).png
Screenshot (49).png
Screenshot (50).png

I am trying to: create custom post types with custom fields

when using options, the checkbox for custom fields will not save as checked

#1386129

I had upgraded to WP 5.3
downgrading to 5.2 solved the issue

#1386143

Hi, I'm able to see the same symptoms so I've escalated this to my 2nd tier support team. One thing to note is that if you go to Toolset > Post Types and edit this post type, there are options for "Sections to display when editing...". If I check the Custom Field checkbox here, I can then use the Block Editor option more effectively. This is a bit confusing so I've asked for some clarification here. I'll let you know what I find out.

#1388259

We have escalated this as a usability issue to the developers, and are waiting to hear back. My 2nd tier support team feels that managing Custom Fields from the block menu shouldn't be possible if the custom post type has the Custom Fields section turned off in the post type editor. I'll let you know as I receive more information about that from the developers.

#1391239

Okay our developers have investigated further and determined that this is a bug in the Block Editor of WordPress. Types is registering the Custom Fields panel correctly based on the settings in the post type editor, but the Block Editor does not respect the setting and always offers the Custom Fields panel option, even if the panel is disabled in the post type editor. This is a bug in the Block Editor, and there's nothing we can do in our software to change this behavior.

I searched on the WordPress Gutenberg project and found this related pull request:
https://github.com/WordPress/gutenberg/pull/16338

It seems that another User has reported a similar issue.