Post Fields

A post field is one value per record — a price, a status, a date, a rating, an address. You define the field once on the record type; each record fills in its own value. The value appears in the record’s page header (the hero) and on the record’s cards in post grids and archives.

How to add a field

1. Open Post Runtime → Post Types and select Post Fields on the type’s row, then Add New.
2. Enter a Key (lowercase letters, numbers and underscores; it cannot be changed later) and a Label (shown on the record edit screen).
3. Choose a Display type, then a Card position and a Single-post hero position. Options for the chosen type appear below.
4. Select Create field.

Editors then fill in values in the Post Fields box on each record. A field left empty is not shown.

Display types

Display type	Shows	Options
Currency ($1,250,000)	A formatted amount.	Currency code (blank uses the currency in Promptless WP’s Business Identity, then USD); Value suffix such as +, /mo or /night.
Number with label (1,800 sqft)	A number and a unit.	Unit label; Thousands separator (turn off for years and ID numbers).
Badge (For sale)	One coloured pill.	Default color intent; Options (JSON).
Meta pair (🛏 3)	An icon and a short value.	Icon.
Date (May 20, 2026)	A date, or a date and time.	Format mode: Absolute, Relative (2 days ago) or Custom with a PHP date format.
Text (plain string)	Plain text, up to 500 characters.	—
Rating (★★★★☆ 4.8)	Stars, the value and an optional review count.	Maximum (default 5).
Progress bar (65%)	A bar with current and goal values.	Maximum is the goal when a record has none; Currency code shows amounts.
Multi-badge (Vegan, GF, Quick)	Several pills from a comma-separated list, at most 8.	Default color intent; Options (JSON).
Location / map (address)	An address. On cards it is text; on the record’s page it is a map.	See Location maps.

Positions

The same five positions exist in the page header and on cards. You pick one for each context, so a field can be prominent on the page and hidden on the card, or the reverse.

Position	Where it appears
Image overlay (badge on image)	A pill on the featured image, top left. Best for a status.
Headline (prominent, above title)	A large value above the title: a price, a salary, an event date.
Subtitle (under title)	A small line under the title: a location, a company.
Meta strip (inline list)	A row of small items: beds, baths, area.
Footer meta (bottom row)	The smallest line at the bottom: a listed date, an ID number.
Hidden in this context	Not shown in that context.

Several fields can share a position; they appear in the order of the field list. Drag rows on the Post Fields screen and select Save order to change it. New fields default to Meta strip in both contexts.

Note

An Image overlay field on a record with no featured image is not lost. On the record’s page it shows at the top of the header text, above the title; on a Promptless WP post grid card (Promptless WP 1.8.4 or later) it shows in the card’s text. The Post Fields box warns when this applies.

Badge options and colours

A badge’s colour comes from its intent: Primary and Secondary use your brand colours with a readable text colour worked out for you; Neutral is a dark translucent pill that reads on any photo. Neutral is the default.

To limit a badge to fixed choices, enter Options (JSON), a map of stored value to label and, optionally, an intent:

{
  "for_sale": { "label": "For sale", "color_intent": "primary" },
  "sold": { "label": "Sold", "color_intent": "neutral" }
}

The record edit screen then offers a dropdown of these labels, and a value that is not in the map is refused. A multi-badge looks up each item in the same way. Up to 24 options per field.

Hiding a field on one record

Each field in a record’s Post Fields box has Hide on cards and Hide in single-page hero checkboxes. They hide that field on that record only; the field’s positions stay as defined. For example, a seller who does not want the price on the listing card.

Other field settings

• Description — help text shown above the field in the Post Fields box.
• Required — marks the field as required on the edit screen. Records can still be saved with it empty.
• Semantic role — marks a date, badge, text or currency field as an event’s start, end, status, location, price or attendance mode. See Events and calendar feeds.
• Filterable and Sortable — let visitors filter or sort a post grid by this field. See Archives and post grids.

Limits and common problems

• Twelve fields per type. The screen warns above eight, because cards get crowded; a thirteenth field is refused. A developer can change the limit with the pcptpages_max_post_fields_per_cpt filter.
• Removing a field keeps the values. Values already saved on records stay in the database; defining a field with the same key brings them back.
• A value does not appear. The field is empty on that record, its position is Hidden in this context, or it is hidden on that record.
• Cards on other themes show no fields. Post fields on cards need a Promptless WP post grid or the Promptless theme’s archive. The record’s own page shows them on any theme.

Related pages

• Groupings — Repeatable lists on a record's page — the five layouts, where they sit, how items link, and the four ways a grouping fills itself, including reverse lookups.
• Single Record Pages — What appears on each record's page and in what order, related records, search engine tags, caching, and how themes and Promptless WP can take over the page.
• Archives and Post Grids — List records as cards on the theme archive or a Promptless WP post grid, choose what each card shows, and give visitors filters and sorting built from your fields.
• Events and Calendar Feeds — Make a record type event-shaped with semantic roles, then get upcoming and past lists, Schema.org Event markup, add-to-calendar links and a subscribable feed.
• Location Maps — Show a map of each record's address on its page with a location field — click-to-load or automatic, zoom, directions, placement, and the fallback address.