Changelogs

Core Forms 4.10.2 makes submissions easier to scan, actions easier to reuse, and Telegram easier to configure.

• Scan submissions with sender details, answer previews, local dates and a responsive inbox. Filter by status, form and date, or switch a form to All fields.
• Import selected actions from another form through a searchable popover beside Active Actions. Review field warnings and save to keep the copies.
• Set up Telegram with bot verification, chat and topic discovery, masked tokens, plain-text messages and sample-message testing. Group migrations recover automatically after a successful send.
• New submissions no longer appear hours old on non-UTC sites. Date filters follow the site timezone, and submit buttons no longer appear as answer columns.
• License & Updates shows the actual last successful release check, offers a direct upgrade when available, and includes changelog and support cards.
• Action inputs use consistent sizing, removal controls are red buttons, and navigation and active editor tabs have clearer styling.
• Job application upload help follows the current limit, donation pledges use honest button labels, required markers are not doubled, and saved unconfigured payment gateways remain selected.

• Analytics uses consistent cards, distinct metric colors and proportional field-interaction bars. Single-day charts show visible points.

• Separate Mailchimp API action with double opt-in, audience mapping and optional merge fields; the MC4WP-based action remains intact.

• Native Forms overview with submission/accessibility sorting and 50-row pagination. Plugin-dependent actions remain visible with dependency tooltips.

Validation: 561 PHP tests, 61 JavaScript tests, PHPStan and browser checks on desktop and mobile.

Re-released 4.10.2 with every form-table editor shortcut restored, including Actions, Analytics and Revisions.

Core Forms 4.10.1 adds Intelligent Inserter and improves the action editor.

• Search field presets with words such as website, mobile and surname. Contact fields arrive with meaningful names and browser autofill.
• Use the same keyboard-accessible inserter at form level and inside containers.
• Save actions repeatedly without accumulating blank or unknown cards.
• Select action fields through compact searchable choosers, with cursor insertion, JSON-aware tokens and multi-field selection.
• Copy exact hook and field values. FlowMattic hooks update with the selected scope; test samples use actual form fields and display the selected payload.
• Edit recipient routes in a compact responsive table. Empty placeholder rows do not accumulate and variable chips are consistent.

Existing fields and submission keys are preserved. Typed unavailable integrations retain their settings.

Update through WordPress with an active Core Forms license.

Release details · Changelog

Core Forms 4.10 adds Service and Event products to Core Commerce, a fuller customer account, and fixes for survey submissions, fullscreen forms and poll results.

Core Commerce

• Sell services and events with the right delivery fields and one-time plans, without issuing software license keys.
• Give customers purchase history, order details, printable receipts, licenses, downloads, subscription terms and profile settings.
• Build product galleries with the Product Gallery block or shortcode. Use virtual product URLs or connect your own content pages.
• Configure new license key style, length, prefix and grouping while preserving existing keys.
• Keep checkout pages separate from other installed stores, with compatibility checks and a repair action.

Forms and polls

• Fixed submission details crashing when checkbox answers are arrays and the optional email is empty.
• Restored field headings in per-form submission tables.
• Fixed tall-form view tracking and clearly labeled capped historical start rates.
• Fixed fullscreen navigation icons, dark choice contrast and scrolling for long steps.
• Included Other write-in votes in admin, frontend and REST poll results.
• Corrected the conditional-logic guide to match the current and older editors.

Updating

Update through WordPress with an active Core Forms license. Existing forms and license keys are preserved. Core Commerce activation is separate from the plugin update.

Service scheduling and event attendance use the links you provide. A yearly license term does not create automatic recurring charges; the payment provider owns recurring collection.

Read the release post · Full changelog

Added

• Drag fields and containers onto step tabs to move them between steps without losing other fields.
• Industry-focused multi-step templates with relevant form fields, local email actions, acknowledgement messages, and submission settings.
• Guided variants of longer starter forms, with multi-step badges, layout filters, and interactive sample previews.

Improved

• Poll creation uses a single-column editor with instant tabs that retain unsaved changes and keyboard shortcuts for adding answers.
• Template category filters span the gallery width and wrap without clipping.
• Core Forms and Core Polls appear when searching for cf in the WordPress block inserter.
• Blank-template buttons retain readable hover and keyboard-focus colors.
• Sample success messages distinguish requests and pledges from completed subscriptions, payments or bookings.
• Sample forms retain their schema, settings, actions, and messages when created or applied in the builder.

Added

• Unlocked Multi-Step Forms in the UI
• Visual multi-step form editing with named steps, step ordering, a canvas for each step, and field movement between steps. Removing a step preserves its fields, and both save controls retain the layout through Visual/Code changes.
• Fluent Support customer and ticket creation with inbox/product mapping, priority conversion, category context, and links between tickets and saved submissions.
• Authenticated n8n webhooks with typed JSON mappings, explicit field selection, test/production URL checks, and an importable intake workflow.
• Pipedrive person/organization matching, lead or deal creation, custom fields, pipeline/stage checks, and optional follow-up activities.
• Zendesk tickets with requester mapping, tags, custom fields, and validated uploads belonging to the saved submission.
• Resend transactional email with stable idempotency keys and signed, correlated delivery/bounce events.
• FlowMattic Plugin Actions bridge with per-form/shared hooks and named field payloads.
• Administrator-only action testing with editable sample data and inline results.

Fixed

• Form previews load the complete form runtime and their own styles. Save & preview opens the latest edits with desktop/mobile widths; URL prefill no longer overwrites submission tokens.
• Multi-step forms supply a final Submit button when none is defined, keep nested container groups out of the step list, and support keyboard step navigation with labeled progress.
• Empty or unsigned Resend webhook requests return an authorization error even when WordPress supplies null headers or body.
• Newly added action cards receive unique persistent identities and control IDs, including after another card is removed.

Core Forms 4.9.4 fixes integration delivery, retries, field mapping, and provider compatibility.

Fixed

• Unify action outcomes across submissions, paid fulfillment, testing, replay, and queued work; report transport/provider failures and missing handlers accurately.
• Connect background delivery and transient retries to eligible actions, with saved-submission requirements, execution leases, and ActiveCampaign/Kit checkpoints.
• Preserve unavailable integrations and validate field mappings; retain explicit unchecked settings.
• Correct Notion title/property mapping, Airtable value types and metadata, FluentCommunity membership APIs, and raw WhatsApp webhook responses.
• Replace the broken Sheets setup link with a maintained authenticated receiver and align integration descriptions with the implemented capabilities.

Integration setup

• Airtable tokens require schema.bases:read and data.records:write for the selected base. Notion connections require read and insert access to the shared database or data source. These permissions let Core Forms match the destination schema and send correctly typed values.
• Google Sheets has a maintained receiver with a shared-secret setting. Existing plain OK receivers remain supported; the new receiver must use the same secret as the form action.

Core Forms 4.9.3 fixes wrapper-class data loss and redundant ARIA requirements, and improves the Support Request template with preconfigured email actions.

Improved

• The Support Request template now includes an optional Site URL, category, priority, subject, and a six-row issue description, with an admin notification and submitter auto-responder configured using the site’s email address.
• Applying a template inside the visual builder now saves its action and message presets through both Save fields and Save Form.

Fixed

• Classes and supported attributes on individual p/div/span field wrappers survive Code/Visual conversions without turning the wrapper into a container or hiding its input. Wrapper attributes remain separate from input attributes.
• Recover the specific saved wrapper/container name collision produced by 4.9.2 when the original input is still present in the schema.
• Native required fields no longer trigger a missing aria-required warning. Frontend enhancement, accessibility autofix, templates, and the legacy field generator no longer add redundant aria-required attributes alongside required.
• Cached accessibility reports discard the retired warning while retaining other findings. Native required validation and explicitly authored ARIA remain intact.

Core Forms 4.9.2 fixes field editing, rendering, and validation across the builder and front end.

• Code and Visual mode preserve radio and checkbox groups, selected values, empty placeholders, option groups, nested layouts, helper HTML, descriptions, and custom attributes through repeated edits and saves.
• Saving immediately after editing HTML keeps the latest fields. Duplicating or renaming nested fields updates their internal references and avoids duplicate choice values.
• Name, Address, Rating, submit, and reset fields render usable controls. Named submit buttons retain their values in AJAX submissions.
• Conditional fields support both colon and equals rules, checkbox dependencies, multiple conditions, and hidden required controls.
• Required checkbox groups validate correctly when advancing multi-step forms. Inline validation preserves help text and recognizes selected radio groups.
• Server validation checks field types, allowed choices, numeric and date limits, step values, and multiple email addresses while accepting zero as a valid value.
• Calculated fields recognize both supported calculation attributes, and character counters load when their attribute is present.
• Field and option settings have associated labels and retain explicit checked and selected defaults.

Validated with 385 PHP tests, 14 JavaScript regression tests, static analysis, and live audit forms on gauravtiwari.org.

Core Forms 4.9.1 fixes three form-builder issues:

• The p/div/span wrapper setting now applies to schema-backed forms and generated HTML.
• Consent fields render as working checkboxes and keep their type when switching editor modes.
• HTML imports retain autocomplete, inputmode, ARIA, data attributes, and other supported control attributes through saving and rendering.

The stray settings badge has been removed from License & Updates.

Quoted attribute values are escaped correctly in generated markup.

Requires WordPress 6.4 or later and PHP 8.1 or later.

Core Forms 4.9.0 improves submission reliability, spam protection, payment validation, and the WordPress admin experience.

• Fixes reCAPTCHA and math-captcha validation, draft-save protections, and sensitive template-field access.
• Preserves form HTML when saving from other tabs and prevents submission deletion from touching unrelated post metadata.
• Recomputes calculated payment amounts on the server, reports failed submission writes, and preserves uploads without JavaScript.
• Makes activation safer, improves duplicate prevention and GDPR erasure, and adds submission indexes and diagnostic tools.
• Adds searchable settings sections, accurate unsaved-change indicators, consistent borders and colors, and accessible copy controls.
• Improves Commerce navigation and activity, form-builder toolbar states, and submissions filtering.
• Repairs standalone URL-base changes and shows URL controls only when fullscreen mode and standalone publishing are enabled.

Requires WordPress 6.4+ and PHP 8.1+. Tested with WordPress 7.1.

Validation: 336 unit tests, PHPStan, JavaScript lint, generated-asset checks, package integrity and PHP syntax checks, plus local browser verification.

Read the Core Forms 4.9 release post.

Core Forms now ships minified CSS and JavaScript, and only loads them where a form actually renders.

Changed

• All first-party stylesheets and scripts are served minified on the front end and in the admin. Across the library that is 716 KB of CSS/JS down to 553 KB. forms.css drops 48%, forms.js 48%, smart-forms.js 52%.
• Readable sources still ship alongside the minified files. Define SCRIPT_DEBUG or use the new cf_use_minified_assets filter to serve them instead.
• Assets that arrive already minified (the webpack admin bundle, vendored Prism) are served as-is rather than duplicated in the package.

Added

• Core_Forms\Assets resolves an asset path to the file that should be served, with cf_use_minified_assets as the escape hatch.
• npm run build:assets regenerates the minified files; build.sh fails the build when they are stale.

Fixed

• Page-level form detection now also inspects reusable blocks, widget areas, and block-theme template parts, so a form placed outside post content gets its stylesheets in <head> instead of after first paint. The template-part scan is cached and flushed on part save, delete, or theme switch.

Full changelog:

Core Forms 4.7.5 fixes duplicate field IDs and reworks MailerPress consent handling.

• Schema-rendered field IDs are now unique per form instance, so labels and descriptions stay correctly associated when multiple forms appear on one page.
• The MailerPress action defaults to double opt-in, preserves existing subscribers and suppressed contacts, and records form-level consent metadata. Confirmation is resent only when a pending or previously unsubscribed contact submits again.
• The legacy FluentCart-to-MailerPress bridge no longer creates subscribed contacts when its settings are empty.