Single Record Pages
Promptless CPT Pages draws the page of every record of its types. You do not build these pages: they come from the record type’s settings and the record’s values, so every record of a type looks alike.
What the page shows
Section titled “What the page shows”From top to bottom:
- The hero — the title, the excerpt, the featured image and the post fields placed in the hero, in the layout set on the record type. For an event, Add to calendar and Google Calendar links follow.
- Groupings and maps placed above main content.
- The main content you write in the WordPress editor, if the type supports the editor. A Promptless Forms shortcode here shows its form.
- Groupings and maps placed below main content.
- A sidebar, only when a grouping or map is placed there. The page then has two columns on wide screens; the sidebar stacks below on phones.
- Related — up to three other published records of the same type that share a term in the type’s first taxonomy, with their images and titles. Not shown when the type has no taxonomy or the record has no term.
The page sits inside the theme’s header and footer. When Promptless WP is active, it uses the site’s colours, fonts and spacing, and follows its light and dark section styling.
Search engine tags
Section titled “Search engine tags”Each record page gets a meta description (the excerpt, or the start of the content, cut to about 155 characters) and Open Graph and Twitter tags with the title and featured image. They are left out when an SEO plugin is active — Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework or Slim SEO — so it can write its own. Event records also get Schema.org Event markup; see Events and calendar feeds.
Building one record by hand
Section titled “Building one record by hand”To design one record’s page yourself, switch Promptless WP’s builder on for that record. Promptless WP then draws the page, and this plugin steps back for that record only: no hero, groupings, meta tags or Event markup of its own. The rest of the type is unchanged.
For developers — template overrides
Section titled “For developers — template overrides”A theme can supply its own template, looked up in this order:
post-runtime-engine-{type}-single.phppost-runtime-engine-single.php- The plugin’s
templates/single-base.php
The template calls PCPTPages_Renderer::render() for the record. The action
pcptpages_single_hero_after_meta runs after the hero’s fields, and the
filters pcptpages_meta_description, pcptpages_meta_tags and
pcptpages_seo_plugin_active adjust the head tags.
Caching
Section titled “Caching”For visitors who cannot edit the record, the rendered page is cached for up
to an hour. The cache is cleared when the record is saved or its terms
change, and when the type or its groupings are edited. Anyone who can edit
the record always sees it fresh, as does the connector’s preview. A
developer can turn the cache off with pcptpages_render_cache_enabled or
change its lifetime with pcptpages_render_cache_lifetime.
Limits and common problems
Section titled “Limits and common problems”- Visitors see an old version. A change that does not save the record — field values or groupings written by the connector, a post field definition edited, or a new record that an automatic grouping should now list — shows to visitors when the cached page expires, within an hour. Updating the record clears it at once.
- The theme’s own single template is ignored. The plugin’s template takes over for its types. Use a template override file instead.
- No main content area. The type does not support Editor (main content). Turn it on under Supports on the record type.