Contact Forms by Cimatti

Live Preview - Try it in WordPress Playground (form submission is not available in the live preview) Forms are an essential component of any website. Contact Forms by Cimatti is the culmination of years of experience building and developing business websites of all types. Our plugin focuses on simplicity, power, and accessibility, helping you capture, store, and classify contacts according to their lead status. It's ideal for single-language and multilingual sites, simple blogs, or complex WordPress-powered Content Management Systems. Accessibility First Contact Forms is built with accessibility at its core, designed to meet WCAG 2.2 AA standards and comply with the European Accessibility Act:

• Screen Reader Support: All form elements are properly labelled and wired with aria-describedby and aria-invalid, with live regions for dynamic updates and meaningful error announcements
• Keyboard Navigation: Full keyboard accessibility for all interactions, including drag-and-drop file uploads
• Clear Error Messages: Validation summary with clickable links to problematic fields, smooth scroll and focus management
• Accessible Loading States: Visual and screen reader feedback during form submission
• Reduced Motion Support: Respects prefers-reduced-motion user preference
• High Contrast: Error and success states designed for visibility

Select, Configure, and Embed Forms Choose the fields you require, customize on-screen messages and email responses, preview, and effortlessly embed forms into your posts, pages, or custom content types using the Contact Form block, a shortcode, or the button in the classic visual editor. Create Forms for Any Purpose Create as many forms as you need. Design landing pages, contact pages, invitations, job application forms with curriculum upload, customer request forms, spare part requests, and more. Utilize the "Clone" feature to avoid "reinventing the wheel" when creating new forms. Ready-to-Use Features Contact Forms by Cimatti has commonly used fields like First Name, Last Name, Address, Province, Country, Telephone, Email, Captcha, and default success messages and email notifications. Simply create a drag-and-drop form, save it, go to a post or page, and insert it with the Contact Form block or, in the classic visual editor, with the Contact Forms button in the toolbar. Easy to Use for Beginners These features make it effortless for first-time users, but the plugin's fast learning curve will soon entice you to explore its advanced features. Craft Superior Forms Don't leave anything to chance; fine-tune the entire form submission process. Spam Protection Stop spam with Google reCAPTCHA v2 (checkbox), the invisible score-based Google reCAPTCHA v3, Cap (the open-source proof-of-work captcha you host yourself), or Cloudflare Turnstile (which needs the free Simple Cloudflare Turnstile plugin). Captcha fields are added per form with drag and drop, so you protect only the forms that need it. With reCAPTCHA v2 and v3 you can also choose, per form, what happens when the check fails: accept the submission silently (the sender sees the normal success message while it is stored with the Spam status and no notification emails are sent), move it to Trash, delete it immediately, or reject it with a visible error so the visitor can retry. Each type ships with the default that fits it: silent for the invisible v3, a visible error for the v2 checkbox, so a real person who forgot to tick it is asked again instead of being filed as spam. For your visitors' privacy, no request is made to Google until they start filling in the form - and with Cap running on your own server, no captcha request leaves your infrastructure at all. Create Reusable Fields Build custom fields to reuse multiple times, starting with 24 available field types, including Text Field, Text Area, Email, Autoreply Email, Telephone, Date, Checkbox, Multiple checkboxes, Radio buttons, Select, Multiple selections area, Post select, Color picker, Hidden value, File upload, Captcha, Custom HTML, Password, and more. Customize Forms to Perfection Apply visual styles to your forms using options in the "Appearance and General" tab. Select colors, margins, button styles, and more. Custom Messages for Success Each form can have its own unique online success message. So, when a form is completed, you can provide access to a file download link, coupon information, or simply a message to confirm that the form was submitted correctly. Email Notifications for Administrators and Visitors Send email notifications to administrators, including tracking information like visitor IP, referrer, date and time of form submission, and other user properties (for a full list, see the Beginners' Guide). Send an email notification to the visitor as further confirmation that the form was filled in correctly. The live preview in the form editor lets you check the form before you publish it. Data Collection and Excel Export All submitted data is securely stored in your WordPress database. Contacts received can be easily categorized into lead status categories and spam and tests can be easily discarded. Add notes on each contact received to keep track. All contact data received can be filtered, searched, and exported to Excel at any time: export all the columns, or only the ones currently visible in the list. Exports open with the header row frozen and the column filters already switched on. Contact Forms also includes a tracking graph in its Dashboard that displays the performance of all or each of your website forms over time. Developer-Friendly API Contact Forms by Cimatti includes an API to assist developers in customizing and adding their own features. WordPress Filters are used to customize forms during generation, to check and validate submitted form values, to execute custom code using sent data, and to add custom tokens for messages. Read the documentation on our site for more information. Powerful PHP Form Builder Class Contact Forms by Cimatti utilizes a PHP form builder class to generate the forms, ensuring robust and efficient form creation and management.

2.3.6 Fixes

• Color pickers in the plugin settings, Layout & Styling tab: picking a color a second time did nothing. The first color you chose was kept and every later choice was silently discarded, so a color could only be changed by clearing the field and starting again, and saving stored the old color rather than the one you had just picked. The small color square beside the button also stayed blank instead of showing your choice. Both are fixed, on all nine color settings.
• Color pickers in the form editor, Appearance and General tab: clicking the color square often appeared to do nothing, and clicking it again opened the picker, so the first click looked as though it had been missed. It started once you had clicked into the box where the color code is typed. The picker now opens and closes on every click, still with only one open at a time, and clicking into the color code box no longer disturbs the picker that is open.

2.3.5 New features

• Submissions list: the two Excel exports are now in the Bulk actions dropdown as well, where they cover only the submissions you have ticked instead of the whole list. Tick the rows you want, choose "Export visible columns to Excel" or "Export all columns to Excel" under Bulk actions, and click Apply. The two buttons above the table are unchanged and still export everything the current filters show. The bulk export follows the screen you are looking at: the columns you have visible, the sort order you have chosen and the filters you have applied, in the Trash and Spam views too.
• Fields page: a search box above the list, the same one you already use on the Categories and Tags screens. It looks at the label, the slug, the field type and the description, so you can find a field by any of them, and it tells you how many matched. Searching and sorting work together, and the list now shows its total count whether or not you are searching.
• Auto mark as spam: a list of email addresses that are always treated as spam, in the new "Other settings" tab of the plugin settings. Submissions carrying one of them in an email field are marked as spam on every form, whatever the captcha of that form decided. A captcha can tell how a form was filled in, not who filled it in, so a sender you already know is unwanted gets through it. List an exact address (spammer@example.com), a whole domain (@spammydomain.net, or just spammydomain.net), its subdomains (@*.spammydomain.net) or any wildcard pattern, one per line, with # comment lines to note why an address is there. Matching ignores upper and lower case and covers every Email and Autoreply Email field. A match is accepted silently: the visitor sees the usual success message, the submission is stored with the Spam status, and no notification or autoreply email is sent. You will find it under Spam in the submissions list, where "Not spam" restores it. The list is empty out of the box, so nothing changes until you add an address.
• Form editor: a "Create new field" link at the foot of the Available Fields column goes straight to the Fields page, so you no longer have to leave through the menu to define a field you find missing while building a form.

Fixes

• Submissions list: with enough columns showing, the whole admin page slid sideways instead of the table. The filters, the pagination and the heading went out of view, and on some sites the menu on the left slid away too. The table now scrolls on its own, with a scrollbar pinned to the bottom of the screen so you can reach it without scrolling to the foot of a hundred rows. Column widths keep adapting to their content.
• reCAPTCHA v3 badge, "Bottom left" position: the badge was drawn cut off against the left edge, showing the end of its text instead of the reCAPTCHA logo. It now sits properly in the corner and opens and closes on hover again.
• Auto mark as spam: an entry using several wildcards could stop matching longer addresses, so a sender you had listed could still get through. Wildcard matching now gives the same answer whatever the address.
• Settings: the "Other settings" tab could refuse to open if the spam list had been put into the database by a migration or by hand rather than typed into the settings page. It opens either way now.
• Form editor: saving a form no longer leaves warnings in your site's error log. The save itself always worked; the entries were only noise.
• The live previews, in the form editor and on the Fields page, no longer fill your site's error log as they refresh. On sites that keep an error log this was the largest single source of entries in it, since the preview refreshes as you type. The previews themselves look and work exactly as before.

Improvements

• Tested with WordPress 7.1. The oldest supported version is still WordPress 5.9.
• Dashes tidied up throughout the plugin's own text, so the wording reads the same everywhere. The Contact Form block's placeholder now simply reads "Select a form".
• Italian and Spanish translations updated.

2.3.0 This release consolidates all changes since 2.2.32. See changelog.txt in the plugin folder for the detailed per-version history. New features

• Live preview on the Fields page: while you create or edit a field, a preview panel beside the editor renders it exactly as it will appear in a form: same rendering engine, styles, and scripts as the frontend. It updates as you type, for every field type: see the options of a select or radio group, the multiple-selection box, your custom HTML content, the file-upload drop zone, the date picker, and so on. The preview is interactive too: the field is treated as required there (only for demonstration: in your forms it is required only if you say so), so you can leave it empty or type an invalid value and see the validation messages exactly as visitors would, including your custom required/format messages; the preview never actually submits anything. Fields with no visible output (hidden values, captcha fields whose keys are not configured yet) say so instead of showing an empty box.
• Fields page editing improvements: the field slug is suggested automatically from the label while you type (until you edit the slug yourself; emptying the slug resumes the suggestion), the slug is checked while you type (invalid characters, reserved prefixes, excessive length or a slug already used by another field are flagged immediately with a message under the input instead of after saving), deleting a field now asks for confirmation and the Delete button is styled as a destructive action, and when editing a field the heading shows which field you are on with a link back to the fields list.
• Choose your own essential columns: each field on the Fields page has a new "Show in essential columns" option, and the "Essential Columns" button of the submissions list now keeps visible exactly ID, Actions, Form, Submitted and the fields you flagged: one click to go from the full table to the compact view you actually scan. New installs flag the name, email and message fields; on updated sites the email column stays flagged so the button keeps showing it, while the technical IP, Page, Referrer and Language columns are no longer considered essential. The same flags choose which field columns are visible the first time you open the submissions list. The button's tooltip lists the columns it keeps on your site and points to where you choose the fields.
• Choose what happens to your data when the plugin is deleted: a new option in the plugin settings, Danger Zone tab, off by default. Left off, deleting Contact Forms from the Plugins screen keeps your forms, submissions and settings in the database, exactly as before, and reinstalling the plugin brings everything back. Tick "Delete all Contact Forms data when the plugin is deleted" and deleting the plugin also removes everything it owns: forms, submissions, uploaded files and settings, with no further confirmation at that point. On a multisite network each site answers for itself.
• Google reCAPTCHA v3 support: add the new "Captcha (reCAPTCHA v3)" field to any form for invisible, score-based spam protection, with no checkbox to tick. Configure the v3 key pair in the plugin settings (reCAPTCHA v3 uses different keys than v2). The existing reCAPTCHA v2 checkbox field keeps working unchanged, and both can be used on different forms of the same site. As with v2, no request is made to Google until the visitor starts filling the form.
• Cap captcha support: add the new "Captcha (Cap)" field to protect any form with Cap, an open-source, privacy-first CAPTCHA alternative based on proof-of-work: visitors just click a checkbox, no puzzles to solve and no data ever sent to third parties. Requires a self-hosted Cap Standalone server: enter its URL and the key pair in the plugin settings. The widget script is loaded from your own Cap server, so no request ever leaves your infrastructure.
• Per-form spam action on captcha fields: the new "When the spam check fails" setting on the reCAPTCHA v2 and v3 fields lets you choose what happens to submissions that fail the captcha check: accept them silently and mark them as Spam, move them to Trash, delete them immediately, or reject them with a visible error so the visitor can retry. The two captcha types ship with the default that suits them, each configurable site-wide in the settings and per field: reCAPTCHA v3 scores visitors invisibly, so a failed check is accepted silently and stored with the Spam lead status, with no notification emails; reCAPTCHA v2 shows a checkbox the visitor is asked to solve, so a failed check is rejected with a visible error and they can solve it again. Otherwise a real person who forgot to tick the box, or whose challenge expired, would be filed as spam without ever being told.
• Spam management in the submissions list, working like the WordPress comments screen: a dedicated "Spam" view collects all submissions with the Spam lead status (including those classified automatically by the captcha spam action), and spam is hidden from the Active view. Each row has a "Spam" quick action (with a "Mark as spam" bulk action); inside the Spam view you can restore submissions with "Not spam", trash them, or delete them permanently.
• Dashboard: the "Last 10 submissions" table now shows a sortable Lead Status column with the same quick-edit dropdown as the submissions list, plus Spam / Not spam and Trash quick actions. Below the table, a "Go to:" row of quick links (Active, each lead status in use, Spam and Trash, with counts) jumps straight to the corresponding submissions-list view.
• "Hide field title" option on the reCAPTCHA v2, reCAPTCHA v3 and Cap fields, enabled by default: captcha widgets are self-explanatory, so their field title is no longer displayed in the form. The title stays in the page for screen readers and error messages; uncheck the option on the field in the form editor to show it again.
• Configurable reCAPTCHA v3 minimum score: reCAPTCHA v3 scores every visitor from 0.0 (almost certainly a bot) to 1.0 (almost certainly a person), and you can now decide where the line is. Set the site-wide minimum in the plugin settings (Google's suggested 0.5 out of the box) and, if one form needs to be stricter or more forgiving than the rest, override it on that form's reCAPTCHA v3 field.
• The reCAPTCHA v3 score of each submission is recorded and shown on the submission page, so you can see what your forms actually score before changing the minimum.
• reCAPTCHA v3 badge position: choose whether Google's floating badge sits at the bottom right (as before), at the bottom left, or is hidden. Hiding it is allowed by Google only if the reCAPTCHA branding is shown elsewhere, so the plugin automatically prints the required "protected by reCAPTCHA" notice in the form, where the reCAPTCHA v3 field sits.
• Site-wide defaults for the captcha options: "When the spam check fails" and "Hide field title" are now set once in the plugin settings and apply to every captcha field, with a per-field "override" checkbox, the same pattern as every other field setting. Existing forms keep the values already saved on their fields.

Improvements

• The reCAPTCHA v2 loader script is now delivered as a regular cacheable file instead of inline code repeated for every captcha field. Google's reCAPTCHA script is still requested only when the visitor starts filling a form, never on page load.
• Removed the legacy reCAPTCHA v1 code, discontinued by Google in 2018. Existing forms are not affected: reCAPTCHA v2 keeps working with the same keys and settings.
• Submissions list: quick actions (Open, Trash, Spam / Not spam, Restore, Permanently delete) moved from the hover menu under the ID column to a dedicated always-visible "Actions" column, the first column of the list, available in the Trash view too, with the actions always kept on a single row. Column widths now adapt to their content instead of being evenly divided, while long page and referrer URLs stay compact behind the usual [+] toggle.
• Submissions list: long values now compress in the field columns too, not only in the URL ones: a long or multi-line message collapses to a single line behind a [+] toggle, keeping the rows compact; expanding shows the full text with the visitor's line breaks as paragraph breaks.
• Submission page: line breaks typed by the visitor in a message are preserved, so an empty line renders as a paragraph break instead of the whole text collapsing into one block.
• Submissions list: two new icon buttons in the toolbar expand or collapse all the [+] compressed cells at once ("Expand All Rows" / "Collapse All Rows", named in the tooltip), and the "Essential Columns" button now lists in its tooltip which columns it keeps.
• Plugin Check (PCP) 2.0.0 compliance.
• Live demo (Playground): new "Custom HTML Content" example page showing one-off HTML blocks, a reusable HTML field shared by two forms, and a per-form content override; new "Website Restyling Brief" page (color picker field, custom submit button) and "Member Registration" page (password with confirmation stored only as a secure hash, submission without AJAX).
• Form editor: captcha field settings no longer show a "Default value" and a "Custom required message" row that had no effect on captcha fields.
• Leaner admin pages: removed leftover code from earlier versions, including two jQuery UI libraries that were loaded on every WordPress admin page without being used.
• Italian and Spanish translations updated.

Fixes

• Cloudflare Turnstile field: the widget was not reset after a submission sent without reloading the page. A visitor who submitted the form again, for example after correcting another field, sent a verification token that had already been used, and got a "Turnstile verification failed" error they could only clear by reloading the page. The widget is now reset after every submission, so a retry always carries a fresh token.
• Fields page: the "Custom HTML" field type offered no way to edit its HTML content, and other field types were missing settings they support. Every field type now shows exactly the settings it uses, with matching labels ("Custom HTML content" for HTML fields, "Additional query parameters" for post fields), and field types added by extension plugins now get the generic settings (default value, custom required message) instead of none.
• Fields page: saving the pre-installed "Turnstile" field turned it into a plain text field, because its type was missing from the field type list. It is now listed as "Captcha (Turnstile)" next to the other captcha types.
• Fields page: the same could happen to any field whose type is temporarily unavailable, for example while the extension plugin providing it is deactivated. The type is now kept, shown as "currently not registered", and editing the field no longer overwrites it.
• The CSS Class and CSS ID settings on submit buttons and hidden fields had no effect; they are now applied to the rendered button and hidden input.
• Form editor: in the Messages tab, checking "Customize" on the notification email fields (To, Bcc, Subject, From name, From email) did not unlock the text field for editing.
• Form editor: clicking Save while the field widgets were still saving could silently lose part of the changes. All the saves triggered by the Save button now run in sequence, so the published form always matches what is on screen.
• Form editor: the live preview could stay clipped at its minimum height and live style updates could stay disabled when the preview loaded faster than the editor scripts.
• When the reCAPTCHA v2 check failed on the server, the error in the validation summary showed an internal field name with a link leading nowhere. It now shows the captcha field's label, the link scrolls to the captcha widget, and the error message also appears next to the widget itself.
• Submissions marked as Spam could show a different lead status in the dropdown, and the Spam quick-filter link above the list pointed to the wrong view.
• Searching the submissions list with the browser (Ctrl+F) counted every match inside a compressed long URL twice, because the compressed cell kept two copies of the text. It now keeps exactly one, in the submissions list and in the dashboard's last-submissions table.
• Fields page: the live preview appeared oversized and shrank to its real size a moment later; it now starts compact and grows smoothly to its real size, with a discreet loading spinner, and never flashes unstyled content or a stray scrollbar while it loads.
• Resolved PHP 8.4 deprecation warnings logged by several form element classes. No functional changes.
• "Delete all data" did not delete everything. If you had set your own upload folder, the files your visitors submitted were left on disk, and the captcha keys, the analytics and file settings, the cached dashboard statistics and your submissions-list column preferences all survived. They are all removed now. As a safeguard, the folder deletion refuses to touch anything that is not the plugin's own upload folder, so an unusual setting can never take your media library with it.
• On a small number of sites the list of fields had become unreadable to WordPress, usually after a site migration rewrote the stored text. Updating the plugin would have replaced it with the standard fields, losing the ones you had created. The update now repairs it instead, and keeps a copy of the original either way.
• Two fields whose slugs differ only in upper/lower case (for example "role" and "Role") were treated as the same field by the database. The submissions list and the Excel export showed a single column for the pair, and, worse, only one of the two values was actually saved on each submission: the other was silently discarded. Slugs are now case-sensitive everywhere, so both fields keep their own column and their own stored values. Slugs of newly created fields are lowercased to avoid the confusion in the first place; slugs you already have are left exactly as they are.
• The submissions list offered columns for values the plugin stores for its own use: on sites with file upload fields, that included the internal download token, whose value also ended up in the Excel export. Those internal values are no longer treated as fields.
• Forms carried over from a very old installation (before version 2.0) saved submissions with no data in them. The form worked and looked normal, the submission was recorded, but every field value was missing, because the old conversion of those forms left their fields in a shape the submission handler could not match. Affected forms are repaired automatically when you update, including forms sitting in the trash.
• The "Contact Form" block produced an empty front end on WordPress 5.9 and 6.0: it declared its rendering in a way only WordPress 6.1 and later understand. The block now renders on every supported version.
• The high-contrast styles never actually applied: they used a media query value that browsers do not recognize. Visitors who ask their system for increased contrast now get the stronger borders, focus outline and bolder floating labels the forms were meant to show them.

2.2.32 Maintenance release consolidating all changes since 2.2.4. See changelog.txt in the plugin folder for the detailed per-version history. New features

• Fieldset group: new "Border and Title" style selector with 6 options (no border, border only, inline legend, title above, title inside, borderless with title). The fieldset border is now opt-in instead of always-on; re-enable it on existing forms via this option.
• Post select and Multiple post checkboxes fields: add post_status=publish,private to the custom query parameters to also list private posts. Draft and pending posts are never listed.
• Multiple post checkboxes field: the post_type custom query parameter now overrides the field's post type setting, matching the Post select field.
• Fields page: rebuilt as a WordPress-native list table with sortable columns, a "Used in forms" count, bulk delete, and row actions.
• Form editor: permanent "Default Submit Button" indicator at the bottom of the form area, hidden automatically when a custom submit field is present.

Improvements

• Single submission page: redesigned with a WordPress-standard two-column layout, human-readable field labels, and fully AJAX notes (add and delete without a page reload).
• Dashboard: last 10 submissions table rebuilt with sortable columns and an Actions column; 30 individual queries per page load replaced with a single query.
• Submissions list: long page URLs and referrers collapse with an expand toggle; Page and Referrer columns are clickable links; "Review" column renamed to "Open"; export buttons repositioned for better discoverability.
• Dashboard widget: now shown only to administrators, the same users who can access the plugin pages, and its statistics are cached so the dashboard loads faster on sites with many submissions.
• Admin sidebar icon: now monochrome and follows the active WordPress admin color scheme, without flashing the brand color on page load.
• Plugin Check (PCP) 2.0.0 compliance; minimum required WordPress version raised to 5.9.
• Italian and Spanish translations completed.

Fixes

• Translations no longer trigger a _load_textdomain_just_in_time deprecation notice on WordPress 6.7+.
• reCAPTCHA v2: on pages with two or more forms, the captcha now appears when the visitor starts filling any of the forms, not only the first one.
• Post select and Multiple post checkboxes fields: child posts are no longer dropped from the list; search by title, the parent=, include=, child_of= and exclude_tree= filters, and "load more" pagination now work correctly; lists appear in hierarchical order; the {__post_id_*} and {__post_url_*} email tokens output the correct values.
• Post select field: draft, private and pending post titles are no longer shown to site visitors, and a submitted value must match the field's post type.
• Validation summary links now scroll to and focus the correct field instead of jumping to the page top.
• Email format error no longer appears twice after a field loses focus following a previously displayed format error.
• AJAX form submission no longer changes the browser URL; non-AJAX submission sets the correct URL hash after page reload.
• Date field: fixed validation error for custom date fields with minimum or maximum date settings.
• Trashing a submission from the single-submission view now redirects correctly.
• Hidden field: the "CSS ID" setting now sets the id attribute on the hidden input element itself.
• Frontend CSS: focus styles for buttons, checkboxes and radios are scoped inside the form and no longer affect page-level styles.
• Form editor: Save/Cancel button alignment fixed; sort indicator on the Submissions column in the forms list is no longer misaligned.

2.2.4

• Form editor: Appearance tab labels are now clickable (native label elements for accessibility).
• Form editor: Section headings use proper h2 elements with consistent styling.
• Form editor: Consistent row heights for style options; color pickers hidden when row is unchecked.
• Form editor: Labels dropdown no longer overflows its container.
• Form editor: Responsive 2-column layout at viewports narrower than 1200px with preview below full-width.
• Form editor: Fixed flash of unstyled content (FOUC) on page load.
• i18n: Italian and Spanish translations updated.

2.2.3

• Form editor: Added "+" button on each available field to add it to the form with a single click (appends as last, scrolls into view, opens settings).
• Form editor: Hidden the expand caret from available fields list for cleaner UI.
• Form editor: Long field names now wrap to multiple lines instead of being truncated. The "+" button and expand caret remain vertically centered and always clickable.
• i18n: Added Italian translations for new UI strings.

2.2.2

• Form editor: Added instant search filter in the Available Fields column: type to quickly find fields by name (substring match).

2.2.1

• Form editor: Redesigned Fields tab as a stable three-column CSS Grid layout (available fields, drop zone, live preview). The available fields column has its own scrollbar; the other columns use the main browser scroll. Fixes wrapping issues on high-zoom levels, small screens, and forms with many fields or long labels.
• Form editor: Each column now has its own heading styled consistently and aligned at the same height.
• Form editor: Drop zone title moved outside the dashed border for clearer visual hierarchy.

2.2.0

• Tested up to WordPress 7.0.
• Added WordPress Playground blueprint for live preview on wordpress.org - five demo forms covering all field types including fieldsets, checkboxes, multi-select, post-select, and HTML blocks.
• Email notifications: Long URLs no longer break print/PDF layout. Applied table-layout fixed and word-break on URL fields.
• Email notifications: Improved vertical spacing between submitted fields with proper cell padding.
• Email notifications: Fieldset labels now display correctly instead of raw field IDs.
• Email notifications: Fixed malformed font-family quotes in the email body wrapper.
• Single submission page: Restructured from 3-column to 2-column (30/70) layout. Details and Lead Status are now in the left column, submitted fields in the right.
• Single submission page: Renamed "Stats" postbox to "Details".
• Single submission page: Long URLs now wrap properly in the submitted fields table.
• Submissions list: Added view links (Active, Trash, Lead Status) for quick filtering.
• Submissions list: Refactored filter controls into native WP_List_Table extra_tablenav pattern.
• Bugfix: Fieldset without a label no longer shows a gap in the border.
• Bugfix: Essential Columns button race condition - column settings no longer lost during batch save.
• Bugfix: Fields page - legacy-format fields now display correctly with proper name/slug fallback.

2.1.4

• Responsive sidebyside layout: labels automatically stack on top when the form container is narrower than 500px, using CSS container queries. Works across all themes regardless of viewport width.

2.1.3

• Fixed: Post select field value was not saved to database and not included in notification emails. The submission handler now resolves posts directly instead of relying on empty lazy-loaded options.

2.1.2

• Form editor: Added submission count with link to the submissions list, displayed inline with the page heading.
• Form editor: Title input now has proper spacing and sizing matching WordPress core post editor styling.
• Form editor: Google Ads and Tokens tabs now use WordPress postbox markup with form-table layout.
• Form editor: Added unsaved changes warning (beforeunload prompt) when the form has been modified.

2.1.1

• Fixed single submission page: restored proper padding and spacing in the Lead status and Notes postbox
• Improved layout alignment for Lead status dropdown and help icon
• Italian: standardized terminology - "compilazione/compilazioni" for submissions, fixed mixed "modulo/moduli" back to "form/forms", translated all missing strings
• Spanish: added ~260 missing translations (Theme Helper, Appearance, Danger Zone, default messages, block editor, GDPR)

2.1.0 Admin UI modernization with a more coherent design language aligned with native WordPress admin patterns.

• Flat single-level tab bar for the form editor (Fields, Appearance & General, Messages, Data Retention, Google Ads, Tokens)
• Grid-based layout for form field editor and live preview
• Tab navigation on the settings page with ARIA-compliant accessible tabs
• Native WordPress postbox structure for all settings sections
• Messages tab: 2×2 grid layout, accessible radio buttons with fieldset/label, TinyMCE font selector with 10 email-safe fonts
• Default font changed from Lucida Sans to Arial for new forms
• Merged dashboard.css into admin.css, removed dead CSS selectors
• Bugfix: broken CSS selectors caused by panel ID renaming
• Bugfix: Messages, Data Retention, and Tokens panels not properly contained within the tab system

2.0.0 Major rewrite focused on accessibility, modern admin UI, and GDPR compliance. All existing forms continue to work without changes. Important: CSS changes (35 removed !important declarations) may affect frontend layouts customized via theme CSS. Use Contact Forms > Theme Helper to identify conflicts. Where possible, use the plugin's Appearance tab instead of theme CSS overrides.

• Accessibility rewrite: WCAG 2.2 AA / European Accessibility Act compliance
• Inline Labels layout (floating labels)
• Live preview in the form editor
• GDPR data retention, anonymization, and WordPress Privacy API
• Cloudflare Turnstile support (via Simple Cloudflare Turnstile plugin)
• Google reCAPTCHA v2 (checkbox) and reCAPTCHA v3 (invisible, score-based) with built-in key configuration
• Drag-and-drop file upload with keyboard navigation
• Telephone field with E.164 validation and country prefix
• Custom validation messages per field and per form
• Custom CSS class and ID on all field types
• Submissions list with sortable columns, row actions, and Excel export
• Dashboard charts with monthly-by-page breakdown
• Gutenberg block for inserting forms
• Settings page with Danger Zone and deactivation cleanup
• Theme Helper: diagnose CSS conflicts between your theme and Contact Forms
• English, Italian, and Spanish translations
• Plugin Check (PCP) fully compliant

For the detailed per-beta changelog, see the plugin's changelog.txt file. 1.9.14

• Added Cloudflare Turnstile field integration