Finish the Custom Fields API

This is a petition to finish the Fields API and integrate it into ClassicPress core.

In particular, see:

This was a feature plugin that never made it into WordPress core. It would have been a great foundation to further build out CMS capabilities and probably many other things that we haven’t even imagined yet.

But, the core developers don’t need to imagine everything that people will do with our CMS, we just need to provide a solid base for people to build on.

I see this API as mainly an un-opinionated way for plugins like ACF, Toolset, etc to do their job, but much more easily, without having to re-invent almost every piece of the functionality they provide.

For developers, this would also allow us to easily register all custom post types, fields, etc in the theme or plugin code for a site. We would change the field definitions in our dev environment, test and deploy, and everything in production is already updated. We could build a simple UI to manage only the settings that really need to be changed, but this UI wouldn’t let users break the custom content types like what happens on sites today.

For users, it’s hard to tell how this would look. I think this would mostly be a back-end improvement, perhaps with some light UI controls, but most user-facing implementation would be up to plugins until clean standards emerge.

Read-only archive:

Author: James Nylen

Vote count: 66

Status: open


  • cp-research-plugin
  • difficulty-hard
  • request-add-feature



:+1: I totally support this. The work was mostly compatible at the time of WP 4.9 and would be a pretty cool reason to use ClassicPress for certain people.

If you need any help here, I’m sure I’d be able to help make this happen using what it ended up as.


I think everyone at ClassicPress would love to see this happen. @james is the person who can best explain the CP core workflow.