Guide

Block Forms user guide

How editors create reusable forms, place them on the site, and review submissions.

Forms library

Open Forms → All Forms in wp-admin. The default list is a DataViews screen (not the classic post table).

You can filter and sort by action, submission method, and field count. Row actions open the form editor or the Responses screen for that form. Avatars on a title show who is editing that form; Active editors and Working on filters match the other Admin DataViews lists.

To use the classic list table, append ?classic=1 to edit.php?post_type=form.

Create or edit a form

  1. Create a new form under Forms, or open an existing form.
  2. The editor template is locked to a single Form block (prc-block/form).
  3. Set Form Name in the inspector (used for persistence and logging).
  4. Choose Method (API or REST) and an Action from registered form actions.
  5. Configure Action Settings when the action provides them (for example Forward To / Redirect Target for email).
  6. Add or rearrange input blocks, Form Page steps, Form Submit, and Form Message as needed.
  7. Publish the form when it is ready to embed.

Action templates

When you select an action that registered a template, the editor may open a Use Form Template? modal:

ChoiceBehavior
Use templateReplaces inner blocks with the action template. Form attributes stay.
Use existing blocksKeeps the current fields.
Start blankReplaces inner blocks with a minimal base layout.

Newsletter variations

The Form block ships with Mailchimp-oriented variations (Newsletter Signup and Newsletter Selection). Use those when you want a preconfigured subscribe flow.

Embed a form (Synced Form)

  1. In a post or page, insert Synced Form (prc-block/synced-form).
  2. Search for a form CPT post, or create a new form from the placeholder.
  3. The editor shows a read-only preview. Use Edit form in isolation to change the source form.
  4. Publish the host post. Updates to the form post apply everywhere it is embedded.

Review responses

Open Forms → Responses.

  • Inbox and Spam folders separate legitimate submissions from spam classification.
  • New responses default to unread. Use Mark as read / Mark as unread; opening a response does not mark it read automatically.
  • Bulk actions move rows between Spam and Inbox, or update read state.
  • When PRC CRM is active, Create CRM Contact upserts the selected inbox rows into CRM on matching email. Spam rows are not eligible.
  • Filter by form, unread state, and search text.

Responses require the capability filtered by prc_form_responses_capability (default manage_options).

Sample forms

On first run (and when the seed version bumps), the plugin may create editable sample form posts. Example:

SlugTitle
speaker-requestSpeaker Request (Sample)

Duplicate or edit samples as starters. Update the form’s recipient / Redirect Target before you use a sample in production. Samples are deletable onboarding content, not runtime dependencies.

Security notes for editors

Public forms rely on Cloudflare Turnstile (Form Captcha), not page-baked WordPress nonces. Keep captcha in the Form Submit template for public-facing forms.

For email actions on Forms CPT / Synced Form embeds, the recipient comes from the saved form’s action settings on the server — not from values a visitor can post.

Was this helpful?