WebHD

Custom Fields Pro

Field groups for any content type, with nineteen kinds of field including repeaters, groups, pictures and links to other items; a screen to fill them in, an API to read and write them, and blocks that print them.

Version 1.2.1Updated November 19, 2026Automation & Developer

Get in line

Not open yet No card

Description

Field groups for any content type, with nineteen kinds of field including repeaters, groups, pictures and links to other items; a screen to fill them in, an API to read and write them, and blocks that print them.

What it does

  • Field groups
  • 30+ field types (19 here: see what is not built)
  • Repeater
  • Location rules (content type, page template, term)
  • REST exposure
  • A panel inside the editor: Core's editor has no place for a module to add to. Fields are filled in on this module's own screen, linked from the list of items. Seam needed: a filter such as core.editor.panels (value: a list of { title, html }; ctx: { post, user }) plus an action when the editor's form is posted, so a module can print and save its own inputs with the item. Not built yet.
  • Custom content types and ways of filing content made from the admin: a module must name its content types in its own code, when it loads, before the database can be read, and each name must begin with the module's own name. Seam needed: Core reading stored definitions at start-up (or api.registerPostType being allowed after settings are loaded) with owner-chosen names. Not built yet.
  • Flexible content (a field whose rows each pick their own layout). Not built yet.
  • Options pages (fields that belong to the whole site, not to an item). Not built yet.
  • Rules that show or hide one field depending on another. Not built yet.
  • Fields on users, terms and media: values are kept with items of content only. Not built yet.
  • Further kinds: gallery, map, embed, user, term, password, and a picker window for Media (a picture or file is given by its number). Not built yet.
  • Values in Core's own content API: Core gives a module no way to add to what /api/v1/posts returns. Values are read at this module's own addresses. Not built yet.
  • Repeaters and groups inside repeaters: one level only. Not built yet.

Stands in for

Advanced Custom Fields (ACF).

These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.

What comes across

What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.

From Advanced Custom Fields (ACF)
Comes across: Field groups that apply to a content type which exists here, with their fields mapped kind for kind: text, text area, WYSIWYG (as text with bold, italic and links), number, range, true/false, select, radio, button group, checkbox, date, date-time and time pickers, email, URL, colour, image, file, post object, relationship, page link, repeater and group. Labels, names (as keys), instructions, required, choices, limits and starting values come too.
Does not: Gallery, flexible content, clone, map, oEmbed, taxonomy, user, link and password fields; fields inside a repeater or group that are themselves a repeater, group, picture gallery or map; conditional logic; location rules other than content type (a warning says so); groups for options pages, users or terms.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
From Advanced Custom Fields (ACF) values
Comes across: What was typed into ACF fields, read from a WordPress export's post meta, for items already on this site and fields already defined here (matched by key). Lists of ticked choices, dates, repeater rows, group values and links to other items in the same export are converted. Only fields still empty here are filled, and every value passes the field's checks.
Does not: Pictures and files (WordPress stores the number of the file in its own library), links to items that are not in the export or not on this site, values that fail a field's checks, and HTML in rich text beyond bold, italic, code and links.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
From Secure Custom Fields
Comes across: Secure Custom Fields keeps ACF's own export format, so its field groups come in exactly as ACF's do: field groups that apply to a content type which exists here, with their fields mapped kind for kind: text, text area, WYSIWYG (as text with bold, italic and links), number, range, true/false, select, radio, button group, checkbox, date, date-time and time pickers, email, URL, colour, image, file, post object, relationship, page link, repeater and group. Labels, names (as keys), instructions, required, choices, limits and starting values come too.
Does not: Gallery, flexible content, clone, map, oEmbed, taxonomy, user, link and password fields; fields inside a repeater or group that are themselves a repeater, group, picture gallery or map; conditional logic; location rules other than content type (a warning says so); groups for options pages, users or terms. Its post types and taxonomies made in the admin are not carried: content types cannot be made from stored data here yet.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
From Secure Custom Fields values
Comes across: What was typed into ACF fields, read from a WordPress export's post meta, for items already on this site and fields already defined here (matched by key). Lists of ticked choices, dates, repeater rows, group values and links to other items in the same export are converted. Only fields still empty here are filled, and every value passes the field's checks.
Does not: Pictures and files (WordPress stores the number of the file in its own library), links to items that are not in the export or not on this site, values that fail a field's checks, and HTML in rich text beyond bold, italic, code and links.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
From Advanced Custom Fields: Extended
Comes across: ACF Extended adds to ACF and keeps ACF's field groups, so they come in through the ACF importer (with their values through “Advanced Custom Fields: values”).
Does not: Gallery, flexible content, clone, map, oEmbed, taxonomy, user, link and password fields; fields inside a repeater or group that are themselves a repeater, group, picture gallery or map; conditional logic; location rules other than content type (a warning says so); groups for options pages, users or terms. Also ACF Extended's own additions: dynamic post types, taxonomies, options pages, forms, templates and its extra field kinds.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
From Pods
Comes across: From a Pods package, every pod that adds fields to posts, pages or another content type this site has, as one field group: text, website, email, phone (as text), paragraph, code, WYSIWYG, number, currency, yes/no, date, date-time, time, colour, file and image, simple custom lists (single or several choices) and links to posts or pages. Labels, names (as keys), descriptions, required marks and limits come too.
Does not: Pods that make their own content types, taxonomies or Advanced Content Types, and fields on users, media, comments or settings pages; links to terms or people; oEmbed fields; values (Pods packages hold none); templates and pages.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.

No importer yet for: Meta Box, Toolset Types.

Using a plugin that is not named here? It is built for your site On The Fly. How that works

Changelog

  1. 1.2.1 November 19, 2026

    Custom Fields 1.2.1: content imported before the module was switched on gets its custom fields when the same WordPress import is run again; a value already typed here is never replaced. Needs Core 0.1.45.

  2. 1.2.0 November 18, 2026

    Custom Fields Pro 1.2.0: a WordPress content import (an export file or a connected site) brings each item's plain custom fields along: one group per content type, "From WordPress: Posts", with a field for each name; a name that is already a field here fills that field. Fields start as text; change their kind on the groups screen (needs Core 0.1.41).

  3. 1.1.1 November 18, 2026

    Custom Fields Pro 1.1.1: its importers that read a WordPress export now name the WordPress plugins they import from, so a site connected through Migrate → “Connect your WordPress” is offered them only when the old site uses one of those plugins. Nothing else changed. Needs Core 0.1.40.

  4. 1.1.0 November 17, 2026

    Custom Fields Pro 1.1.0: a new Pods importer turns the pods that add fields to posts, pages and other content types this site has into field groups, kind for kind, from a Pods package. Secure Custom Fields and ACF Extended use ACF's own export, so their field groups and values come in through the ACF importers. Pods that make new content types, taxonomies or tables, and fields on people, terms or media, are named in the report.

  5. 1.0.0 November 17, 2026

    Custom Fields Pro: field groups for any content type with 19 kinds of field, including repeaters and groups, a Fields screen per item, an API for filling them, and blocks that show a field, a group or a repeater. Imports ACF field groups and values.

Get Custom Fields Pro when WebHD opens

Hold a place for your site.

One form on the home page: your WordPress address, then your email.

Get in line

No card Takes a minute No fake scan