Custom fields

Custom fields written through the plugin, not around it.

ACF and Meta Box groups, their fields and their values. Values go through the field plugin’s own update function rather than straight into post meta, so its formatting, serialisation and hooks all still run.

Anyone whose content model is mostly custom fields, where an agent writing raw meta would corrupt half of it.

3 jobs

What people actually ask for.

Each of these is carried by named operations that exist in the release you can download today. The ids under every answer are the calls involved — nothing here is a plan.

“Fill in the product spec fields on these twelve posts.”

The group is read first so the agent uses the site’s own field keys rather than inventing them, then each value is written through the field plugin.

  • acf-group-list needs edit_posts
  • acf-field-list needs edit_post
  • acf-field-update needs edit_post

“What custom fields does this post type even have?”

Groups and fields are enumerated from the plugin’s own registry, with their types and keys.

  • metabox-group-list needs edit_posts
  • metabox-field-list needs edit_post

“Read back what is actually stored.”

A field is read through the plugin’s own getter, so a repeater or a relationship comes back the shape the site expects.

  • acf-field-get needs edit_post
  • metabox-field-get needs edit_post
  • metabox-field-update needs edit_post
The shape of it

8 operations, 6 of them reads.

ACF and Meta Box field groups, their fields, and their values — read and written through each plugin’s own API.

Needs: Advanced Custom Fields 5.9 or newer, Meta Box 5.3 or newer. Either, both, or neither. Where it is absent the operation refuses by name, rather than failing obscurely.

Every operation, with its policy

Reads

6 operations that only report. A read still asks WordPress for a capability against the object.

Writes

2 that change something — each one previewed as a diff, snapshotted, verified by reading the site back, and reversible from wp-admin.

Tier

Free, permanently. Nothing in this area moves into a paid tier later.

The limit

What it will not do here.

Field groups themselves are read only. An agent can fill fields; it cannot redefine your content model.

Note 1

Values go through the field plugin’s own update function, never straight into post meta, so its formatting, serialisation and hooks all still run.

Note 2

A group is read before a value is written, so the agent uses the site’s own field key rather than inventing one.

Next

Try it, or read further.

Get the free plugin How a write is guarded