Troubleshooting

The Post Runtime menu is missing

Only users with the pcptpages_manage_cpts capability see it, and activation gives it to administrators only. Sign in as an administrator, or ask a developer to grant it to your role.

A status badge is missing

Check, in this order:

• The record has no value in that field.
• The field’s position for that context (card or hero) is Hidden in this context, or Hide on cards / Hide in single-page hero is ticked on that record.
• On a card: the list is not a Promptless WP post grid or the Promptless theme’s archive, which are the only lists that show post fields.
• The record has no featured image and the badge is placed at Image overlay. From version 0.10.1 it shows above the title instead; on earlier versions it is not shown. Add a featured image, or place the field at Headline.

The map is not showing

• The record’s address is empty and Promptless WP’s Business Identity has no address either.
• Map placement is Don’t show map on single posts, or the record’s Map placement: is Don’t show map.
• With Click to load, the map appears only after the visitor selects Load map. That is intended.

See Location maps.

The filter bar shows nothing, or a filter has no options

• No field of the type is marked Filterable and the type has no public taxonomy whose terms are used by published records.
• Visitor Filters is off on the Promptless WP post grid.
• A taxonomy filter lists only terms that published records of this type carry. Assign terms to the records and publish them.
• A location or meta pair field cannot be a filter.

A filter link typed by hand does nothing

A field or taxonomy whose name clashes with a WordPress address word uses f_ in front of its filter name, such as ?f_neighborhood=downtown. Copy filter links from the page after choosing the filters.

The record address has an underscore

The address uses the type’s slug, such as /pt_meeting/…. Set a different address with rewrite through the connector — see Creating record types. Up to version 0.10.0, rewrite was stored but ignored, so a type kept its slug whatever you set. The fix is in version 0.10.1; after updating, old addresses redirect to the new ones.

A custom address reverted to the slug

Up to version 0.10.0, saving the type from the Edit Post Type screen, which has no address field, dropped an address set through the connector. Set rewrite again through the connector. From version 0.10.1 the screen keeps settings it does not show.

Visitors see an old version of a record

Record pages are cached for visitors for up to an hour, and a change that affects a page clears it at once: saving the record, field values, groupings and hiding set through the connector, a changed field or grouping definition, and a new or changed record that a grouping on the page lists. Up to version 0.10.0 only saving the record, or changing a definition, cleared it; everything else reached visitors when the cache expired. You always see the current version while signed in as someone who can edit the record.

A grouping does not appear

• It has no items on this record. Empty groupings are hidden.
• An automatic source found nothing: the record has no term in the taxonomy, has no value to match, or the matched records are not published.
• A gallery item without an image is not shown.

Images do not show in a grouping

Compact grid and Horizontal row show icons only. Change the record’s Variant to Card grid or Featured card, or set icons.

Records vanished from the admin after removing their type

WordPress only shows registered types. Registering the same slug again brings the records back. Through the connector, postruntime_list_posts with include_orphans: true lists them. Up to version 0.10.0 that worked only for types removed through the connector, not with Remove.

Registering a type reports fields or groupings already exist

The slug was registered before, and its definitions and records survived the removal. The response’s revived block lists them. Use them, or remove the type with purge_data: true to start clean.

An event is listed as past too early

• The type has no Event end date field, or this record’s end date is empty, so the start time counts as the end.
• Up to version 0.10.0, an all-day end date counted from midnight at the start of its day, so the event was past on its last day.

See Events and calendar feeds.

Event times are off by some hours

The site time zone in Settings → General → Timezone, or the field’s Event time zone, is wrong. Up to version 0.10.0, a time sent with a UTC offset was also stored at the UTC time; send local times such as 2026-10-04 18:00 until you have updated.

A record “trashed” through the connector is not in the trash

Up to version 0.10.0, deleting a record of a custom type through the connector deleted it permanently while reporting a trash. It cannot be recovered except from a backup. From version 0.10.1, records go to the trash. Until then, trash records in the admin instead.

The connector returns an error

Error	Cause and fix
connector_disabled (403)	Tick Allow Claude Cowork to call this site on Post Runtime → Connector.
rest_not_logged_in (401)	The application password is missing or revoked. Generate the connection again.
rest_forbidden (403)	The connected user lacks the permission for that tool. See Connector overview.
rate_limit_exceeded (429)	Too many calls to that tool this minute. Wait retry_after seconds.
pcptpages_version_conflict (409)	The definition changed since it was read. Read it again, then update.
pcptpages_foreign_post_type (403)	The post belongs to WordPress or another plugin; the connector only removes its own records.
pcptpages_max_field_count_exceeded (422)	The type already has twelve post fields.

Related pages

• FAQ — Short answers about cost, Promptless WP and theme requirements, ACF, where data is stored, changing slugs and addresses, and what happens when things are removed.
• Post Fields — The ten post field display types, the five positions in the page header and on cards, badge options, per-record hiding, and the twelve-field limit.
• 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.
• 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.
• Connector Overview — The 32 connector tools grouped by task, how to turn the connector on, permissions, rate limits, version conflicts, and how deleting records and types works.