Trinity Forms
FeaturesPricingCompareFAQBlogAll pluginsOffers (offer running) Get Trinity Forms →
Changelog

What's new in Trinity Forms

Every stable release, newest first.

  1. v2.28.4Nov 14, 2026
    • Fixed: a form made from the Newsletter signup or Testimonial template showed "I agree to the terms." next to its consent box instead of the template's own words ("I agree to receive email updates.", "I agree to have this testimonial published."). Forms already made from those templates now show the right words too, and the Visual Builder opens and saves them with those words.
    • Changed: the readme links to the new product video.
  2. v2.28.3Nov 14, 2026
    * Fixed: on a phone, ticking an entry in the Entries list drew its links (View, Email, Spam, Trash) on top of the entry's name. On a phone they now sit on a line of their own under each entry, big enough to tap.
  3. v2.28.2Nov 13, 2026
    • Fixed: in the list of problems at the top of a form, a question that already ends in a question mark read "How can we help?: Please fill in this field." It now reads "How can we help? Please fill in this field.", and the same goes for a question ending in !, : or a full stop.
    • Fixed: on a phone, the list of problems at the top of a form ran past the right edge and made the page scroll sideways. It now fits the form's width.
    • Fixed: on a phone, the "Email me a link to finish this form later" box was a tiny bare box with small text. It now looks like the form's other fields. A long link pasted into an HTML block now wraps instead of widening the page, and the List field's add and remove buttons and the file picker are finger-sized.
    • Fixed (wp-admin on a phone): on the Entries list a long email address pushed the Status column off the right edge, and the date boxes ran off a small screen. Both now fit, and the unread dot sits on the first line of a long name.
    • Fixed (wp-admin on a phone): on Results and Settings, a long form name in a drop-down made the whole page wider than the screen, and Import / Export ran off a 360px screen. They now fit.
    • Fixed (wp-admin in a narrow window): the Forms list showed a blank gap under every form instead of its Edit, Trash and other links. The links now show.
    • Fixed (wp-admin on a phone): the section tabs scroll sideways, and the screen you were on could be hidden off the edge. The current tab now scrolls into view.
    • Fixed (wp-admin on a phone): the AI assistants table was wider than the screen, with its last column out of sight. Each ability is now its own card.
    • Fixed (wp-admin on a phone): in the Visual Builder, tapping a field seemed to do nothing, because its settings opened at the very bottom of the page. The page now scrolls to the settings.
    • Fixed: on a phone, the [trinity_forms_submissions] table was several screens wide and widened the whole page. Each entry is now a card with every value under its column name.
    • Fixed (wp-admin on a phone): on Results, "Where people stop" wrapped each question to three lines in small capitals and hid the last column. Questions now read normally and the table fits.
    • Fixed (wp-admin on a phone): the form's Layout tab made the settings box about twice the screen width, so every tab scrolled sideways. The Fine tuning controls now stack in one column.
    • Fixed: on a phone, the Signature field's Clear and "Type your name instead" buttons and the Repeater's Add and Remove buttons were tiny. They are now finger-sized.
  4. v2.28.1Nov 13, 2026
    • Fixed: the [trinity_forms_my_submissions] list showed as a bare table on block themes such as Twenty Twenty-Five, with no lines or spacing and the columns running together. It now has its own row lines, spacing and left-aligned headings on block and classic themes, and scrolls sideways on a phone instead of widening the page.
    • Fixed: Resend notifications on an entry in Spam sent the emails while the entry stayed in Spam. Entries in Spam or Trash are no longer resent: the entry screen shows the button greyed out with "restore it first", and the bulk action skips them and says how many it skipped.
    • Fixed: with "Also list every problem at the top of the form" on, an empty required field or a badly typed email was stopped by the browser's small pop-up, so the list at the top only appeared for problems the server found. The form now checks itself: every problem is listed at the top with a link to its field, and keyboard and screen-reader focus moves to the list, on Next in multi-step forms too. With the option off, nothing changes.
  5. v2.28.0Nov 10, 2026
    • Fixed: answer columns on the Entries list showed stored choice keys (a, b) instead of the labels. They now show the labels, as the entry screen does.
    • Fixed: in the Visual Builder's All settings window, a strip of the page showed under the Save settings bar while scrolling.
    • Fixed: editing an entry in wp-admin erased its address and rewrote the total, even when you only changed another field. Fields you do not touch now stay exactly as they were, and the edit note names only the fields you changed.
    • Fixed: editing an entry no longer asks for a required field that conditional logic hid from the visitor.
    • Fixed: pressing Add note with an empty box said "Note added." It now says the note was empty and nothing was added.
    • Fixed: opening an entries page past the end of the list showed the first-run "No entries yet" screen. It now says there are no more entries on that page, with a link to page 1. Screen Options on the Entries screen now sets how many entries show per page.
    • Fixed: the Country field listed every country in English on a translated site. Visitors now read the names in the site language (sorted in that language), and the entry screen and notification emails show them the same way. The stored value and the CSV export keep the English name, so existing entries, conditions and integrations work unchanged.
    • Fixed: a new form opened in the block editor started with English fields (Name, Email, Message) on a translated site. They are now in the site language.
    • Fixed: an HTML field nobody filled in printed "Custom HTML" on the public form. It now prints nothing; the editor shows a hint instead.
    • Fixed: Draft with AI added its fields after the starter fields (Name, Email, Message) and kept the title "Untitled form". The draft now replaces the untouched starter fields and gives the form the AI's title.
    • Fixed: in a form's Payment settings, the recurring billing units (day, week, month, year) were always in English. They are now translated.
    • Fixed: a field's custom error message only appeared when the server rejected the entry. Visitors now see it as soon as the browser flags the field (left empty, wrong format), including on Next in multi-step forms.
    • Fixed: the Website field refused addresses with accents or non-Latin letters (https://ejemplo.es/ñ, an Arabic Wikipedia page), and the browser blocked a bare domain such as ejemplo.es. Both are accepted now; a bare domain is saved with https:// in front.
    • Fixed: on a phone, the tabs in the Visual Builder's All settings window ran off the screen (with Pro, 8 of 11 tabs were out of reach). They now wrap onto more rows, in left-to-right and right-to-left languages.
    • Fixed: a fixed-price Product and a flat Shipping charge showed as "single" and "flat" in emails, on the entry screen and in exports, and the total showed as 0.00 next to prices like $0,00. They now show the amount, in the same number format everywhere; the CSV keeps the total as a plain number.
    • Fixed: Views showed the stored choice keys (a, b) and pricing keys (single, flat) instead of the labels visitors picked. Views, and the answer columns on the Entries list, now show the same labels as the entry screen.
    • Fixed: quiz scores were worked out but shown nowhere. The entry screen now shows the score (for example 7 / 10), exports have Quiz score columns, and a quiz form's merge tags list {quiz_score} and {quiz_max}.
    • Fixed: payments could be switched on for a form with no payment keys saved, with no warning, and every visitor's payment then failed. The Payment tab, the form screens and the save message now warn you, and an entry left pending by a failed payment gets a note saying why, in the site language.
    • Fixed: the Integrations page still said integrations are set up in the block editor. It now points to the Visual Builder's All settings > Integrations. A failed integration's log line now says why (for example, the service refused the API key) instead of only "failed".
    • Fixed: the Save and continue later box used the theme's plain buttons and asked again for an email the visitor had already typed. Its buttons now match the form's own, and the email is filled in from the form.
    • Fixed: the Chained Selects field had two different names in Spanish and Korean (the field list and the locked list). It now has one.
    • Fixed: after going from Pro back to the free version, pages printed the raw View shortcode, the Visual Builder named Pro fields like "trinity-forms/field-signature", and the Views tab opened an "Invalid post type" error. Visitors now see nothing where a View was; people who manage forms see a short note naming the Pro features a form uses that are off, both on the page and in the builder, where Pro fields read like "Signature (Pro)". The free fields of those forms keep working.
    • Fixed: a form started blank in the Visual Builder kept an empty Reply-To on its admin notification, so replies went to the site. Once the form has an email field, Reply-To points to it (the first one when there are several); a Reply-To you set yourself is never changed.
    • Fixed: on the Entries list, entries from forms imported from Contact Form 7 (or any form whose name is a plain text field) showed only an email. Rows now show the person's name and the start of their first written answer.
    • Changed: when a registration form asks for a role a form may never give (such as Administrator), the account is still created as Subscriber, and the entry's notes now say so.
  6. v2.27.1Nov 9, 2026
    • Changed: nothing changes in the free version. This release stops a Pro install with a free licence key from being replaced by the free version when it updates.
    • Fixed: a Pro install that held a free licence key, or whose licence the site could not read, could be "updated" to the free version, which removed Pro without a warning. Pro now takes an update only with a Pro licence: enter your Pro key to get Pro updates.
  7. v2.27.0Nov 8, 2026
    • Fixed: a form made with Add Form was saved as a draft. Visitors saw nothing where it was placed, while its owner, who can see drafts, saw it working. A new form now saves as published, unless you choose Draft in the builder bar.
    • New: a draft form placed on a page shows the people who can edit it a note above it: "Visitors see nothing here: form #N is a draft." Visitors still see nothing.
  8. v2.26.0Nov 7, 2026
    • New: the Visual Builder has an "All settings" window with every setting of the form: emails, confirmations, layout, restrictions and, in Pro, save and continue, popup, payments, integrations and workflow. Before, some of these could only be reached from the block editor.
    • Fixed: saving a form in the block editor said "Post updated." It now says "Form updated."
    • Improved: the poll results script is minified too.
    • Improved: the popup, booking, signature, card payment, survey, conversational, AI chat and View files are minified as well, about 30 KB less on pages that use them.
    • Improved: the "save and continue" email names the form and the site and comes from the site's name, not "WordPress".
    • Improved: a site with Pro installed but no licence key entered makes no licence database query per page, and the one-time "Pro is on" notice no longer reads the database on every admin screen.
    • Security: a file upload field now takes its value only from a file the visitor really uploaded, and a stored file path is checked against the upload folders before the file is attached to an email or deleted. Before, a crafted submission could point an entry at another file on the server. Please update.
    • Changed: forms can now be created and edited only by people who can manage Trinity Forms (administrators). Authors and Editors could create forms before, and a form can send email and, in Pro, create users and posts. They can still place a published form in a post: the block's form list shows them the published forms by name.
    • Security: the WordPress REST API no longer lists forms to visitors. The forms route answers only people who can manage Trinity Forms.
    • Security: the importers read other form plugins' stored settings without creating PHP objects.
    • Fixed: a list posted into a single-value field (text, email, number, date and the like) was stored as "Array" and logged a PHP warning. It is now stored as empty.
    • Fixed: saving a form in the Visual Builder with a field that has no field ID showed an English developer message naming the internal block. It now names the field, says which characters an ID can use, and is translated.
    • Security (Pro): a Save and continue later link opened a page with the visitor's answers that a page cache (WP Super Cache and others) could keep and show to the next person opening the same link. That page is now never cached. If you use a page cache, clear it once after updating.
    • Security (Pro): user registration on a form can no longer give a role that runs the site (Administrator, Editor, Shop Manager and the like) or write capability or session data to the new account. Extra profile fields are stored as text.
    • Security (Pro): a PayPal Standard payment marks the entry paid only when the amount and currency match what the entry owed, and only on a site that has PayPal Standard set up. A form sent before this update and paid after it is checked against the amount the form asks for.
    • Fixed (Pro): a Stripe or Mollie payment notice sent twice no longer sends the notifications twice.
    • Security (Pro): Save and continue later needs the form page's security token and works only on published forms that offer it.
    • Security (Pro): editing or deleting an entry from a View works only on entries that View shows.
    • Improved: pages without a form no longer load any Trinity Forms file. The form CSS and JavaScript (about 105 KB) used to load on every page of the site; now they load only on pages that show a form, whether it is placed in the content, a widget, a page builder or a theme template. A site that loads forms with AJAX can bring back the old behaviour with the trinity_forms_load_assets_everywhere filter.
    • Improved: the form CSS and JavaScript are minified, so a page with a form loads about 51 KB instead of 105 KB. The readable files are still included, and are used when SCRIPT_DEBUG is on.
    • Fixed (Pro): on a form that needs approval, a booking waiting for review did not hold its time slot, so the slot could be booked again. It now holds the place until it is approved or rejected. The same applies to product stock.
    • Fixed (Pro): when a booking was paid more than an hour after it was sent and its slot had filled up in the meantime, nothing said so. The entry now gets a note and the site admin gets an email saying the slot is over capacity.
    • Fixed (Pro): when many people booked at the same moment and the slot check had to wait more than 5 seconds, the booking went through unchecked. It is now refused with a message asking the visitor to send the form again.
    • Fixed (Pro): a popup that opened by itself and was never closed (the visitor went on to another page) opened again on the next page, ignoring "don't open it by itself again for N days". The days now count from when it opened.
    • Improved: pages without a form make no database query for Trinity Forms Pro. The licence status and the landing-page setting were read with a query on every page (4 in all); they are now loaded with the rest of the site's settings.
    • Fixed (Pro): the Delete link in a View always answered "You cannot delete this." It now moves the entry to the trash.
  9. v2.25.2Nov 6, 2026
    Stripe, Mollie and PayPal Standard return to the form's page with its confirmation (or a cancelled notice), not the home page
  10. v2.25.1Nov 6, 2026
    Stripe library updated to 22.1: no curl_close() notice on PHP 8.5
  11. v2.25.0Nov 5, 2026
    • Fixed: a vote on a Poll-mode form sent within about three seconds of the page loading was counted as spam while the visitor was told thanks. Polls no longer use the too-fast rule (the honeypot, the signed page token and the other spam checks still apply); other forms are unchanged.
    • New: Poll mode. Tick "Poll: after a vote, show the results instead of the form" in a form's Restrictions settings (block editor or Visual Builder) and visitors see the results bars with percentages and counts right after voting, and on every later visit from the same browser. The browser remembers the vote, so there is no IP check to block people on shared networks; the optional per-user and per-IP limits, if you set one, show the results instead of an error. The page markup is the same for everyone, so full-page caches are fine, and with JavaScript off the form simply shows. Free-text answers are never shown.
    • New: a "Quick poll" template: one required question with three answers, Poll mode on, no entry limits and no email per vote.
    • New: visitors can see poll results. Put {poll_results} in a confirmation (or {poll_results:field_id} for one question), or add the [trinity_forms_poll_results id="12"] shortcode or the Poll Results block to a page, with an option to show the results only after the visitor votes. Works on cached pages; free-text answers are never shown.
    • Fixed (Pro): a View's single entry page now follows the same rules as the View's list. Typing the id of a pending, held or not-yet-approved entry (or someone else's entry in an own-entries View) into the address no longer shows it, and no longer feeds its page title or share tags. A valid edit link for that exact entry still opens it.
    • New (Pro): PDF from a View. Tick "Allow PDF download" on a View and its single entry page (and, if you want, each row) gets a Download PDF link. The PDF has only the fields that View shows, with the View's labels and order, never a hidden field, and only for entries that visitor can see in that View. Off by default.
    • New (Pro): PayPal Checkout. Add a PayPal REST API Client ID and Secret (one pair for Sandbox, one for Live) in Settings > PayPal and payments go through PayPal's current checkout: the visitor approves on PayPal, the payment is taken on your server when they come back, and the amount and currency are checked before the entry is marked paid. A reload or a second visit never charges or emails twice. Cancelling at PayPal brings the visitor back to the form (or the quote) with a message.
    • New (Pro): PayPal webhook. Paste the Webhook ID of your PayPal app and a visitor who closes the tab after approving still gets their payment taken and the entry marked paid. Refunds and declined payments show on the entry too.
    • Improved (Pro): the entry screen shows the payment's transaction ID (for PayPal the capture ID) next to the amount.
    • Changed (Pro): sites with only the PayPal email keep using PayPal Standard as before, with a notice asking for the REST API credentials. Older PayPal Standard (IPN) payments still complete after the switch, and a resent IPN no longer sends the emails twice.
    • Fixed (Pro): when a customer pays a quote online, you now get an email saying the quote was paid (before, only the approval email was sent).
    • New (Pro): Square payments. Add your Square Application ID, Access token and Location ID (Load locations finds it) in Settings > Square, pick Square as a form's payment provider, and the card is taken on the form itself with Square's card field. The card goes straight to Square; the entry is marked paid, with the Square payment ID, before the visitor leaves the page. Declined cards get a clear message and nothing is sent. Quotes can be paid by card too.
    • New (Pro): Authorize.Net payments with Accept.js. Add the API Login ID, Transaction Key and Public Client Key in Settings > Authorize.Net and cards are taken on the form (the page needs https). Declines, AVS and security code mismatches and duplicate payments get plain messages.
    • New (Pro): Refund with Square / Authorize.Net on a paid entry refunds the card in full (Authorize.Net voids a payment that has not settled yet). Optional webhooks (signed, checked on every delivery) record refunds made in the Square Dashboard or the Authorize.Net Merchant Interface, and payments held for review.
    • Improved (Pro): saved Square and Authorize.Net keys are never shown again on the Settings screen, only their last 4 characters, and new keys are checked with the gateway when you save.
    • Fixed (Pro): replacing Pro with the free zip now gives the licence seat back, so the key can be used on another site.
  12. v2.24.0Nov 4, 2026
    • Fixed: a Page break's "Next button text" and "Previous button text" are used on the form. They were saved but every step showed "Next" / "Previous".
    • Fixed: on a multi-step form the Next button looks like Submit and Previous gets a matching outlined style (both were plain browser buttons), with even spacing, wrapping on a phone, the right order in right-to-left languages and readable on dark themes. Save & continue later gets the same outlined style.
    • Fixed: the Visual Builder's Settings now has the Restrictions: when the form opens and closes, entry limits (total, per user, per IP address) with their messages, and Require login. They are the same settings as the block editor's Restrictions tab, so a change in either editor shows in the other. Before, they were only in the block editor's settings box.
  13. v2.23.0Nov 3, 2026
    • Fixed (Pro): the licence screen explains every refusal in plain words (no more raw codes like license_expired), and its status updates right after "Check for updates now" without a reload. A free key entered in the Pro build now gets a clear warning.
    • Changed: entry exports (CSV, Excel, View downloads, WP-CLI) name the entry columns in the site language ("Entry ID", "Date submitted", "Status", "IP address") instead of id / submitted_at / status / ip_address, the Status column reads like the entry screen ("Completed", "Spam") instead of the stored key, and the date header names the site time zone, e.g. "Date submitted (Europe/Madrid)". Dates are in the time zone set under Settings > General (stored as UTC). A spreadsheet or script that looked for the old column names needs the new ones.
    • Fixed: Visual Builder field settings show readable, translated choices instead of stored values (Product type, Show as, Fills in, Amount mode: "Dropdown of the answers", not "select"), and settings such as Minimum length, Maximum rows or Next button text have translated names instead of English ones made from the setting's key.
    • Improved (Pro): with the AI spam second opinion on, the double opt-in confirmation email waits for its verdict, like the autoresponder: an entry the AI moves to Spam gets no email (no mail to a forged address). If the AI fails, the licence lapses or the check takes over 10 minutes, the email goes out as before.
    • Fixed (Pro): with email confirmation (double opt-in) on, the visitor is told on screen to open the email and confirm; only "Thank you!" was shown, so entries stayed unconfirmed.
    • Fixed: success and error messages, required stars and help text stay readable on dark themes (they fell to about 2:1 contrast, e.g. Twenty Twenty-One in dark mode).
    • Fixed (Pro): after an AI chat form is sent, only the thank-you message stays; a Send button that did nothing was left under the chat.
    • Fixed: "Create a page" on a site where pages open in the Classic Editor puts the form's shortcode on the page, so the page no longer looks empty in the editor.
    • Fixed (Pro): the AI spam second opinion no longer moves a real entry to Spam because the name or email was masked for privacy ("A. G.", a***@...) or because a booking or sign-up form has no message.
    • New: QR code button next to the landing page address, and the landing page offered first on the QR screen. (Pro)
    • New (Pro): REST API: change or add a form's integration feed (PUT /forms/{id}/feeds/{slug}). Same permissions as the admin screens.
    • New: Form revisions. Every save of a form (block editor, Visual Builder, form settings, REST, AI assistants) keeps a copy; the last 20 are listed with who, when and what changed (fields added, removed or changed, title, settings). Restore one with a confirmation; the restore is kept as a revision too. "Revisions" on the forms list and a box on the form edit screen.
    • New: QR code that opens a form. "QR code" on the forms list: pick a page the form is on (blocks, shortcode, Elementor, Beaver Builder), another page or any address, optionally tag scans with utm_source=qr, then download SVG or a 1024px PNG. Made on your own site, no outside service.
    • New: Beaver Builder module "Trinity Forms" (works with the free Beaver Builder Lite): pick a form, see it in the editor.
    • New: REST API: read, add, edit and delete an entry's notes (/submissions/{id}/notes; notes the plugin wrote stay read-only), and read a form's integration feeds with secrets hidden (GET /forms/{id}/feeds). Same permissions as the admin screens.
    • Improved: REST API requests signed in with an application password no longer need a nonce.
    • New (Pro): AI on entries. A short summary on the entry screen, a spam second opinion that can move clear spam to Spam (or only flag it) but never deletes, with the reason in the activity log (while it runs, the form's emails and integrations wait: nothing goes out for an entry it moves to Spam, everything goes out as usual otherwise or if the AI does not answer, within 10 minutes at most; the visitor's confirmation on the page does not wait), and a reply draft you edit before sending. Each is off until you turn it on under Settings > AI assistant, for all forms or the ones you pick. Files, passwords, card numbers and signatures are never sent, and the entry is sent as data the AI may not take orders from.
    • New (Pro): "Explain with AI" under the Where people stop report gives a plain-language read ("most people stop at Phone: consider making it optional"). Only question labels and counts are sent; kept per form and date range.
    • New (Pro): AI chat forms. Turn on "AI chat" on a form's General tab and visitors can fill it in by chatting: the AI asks the form's questions one at a time in the visitor's language, puts the answers into the real fields, checks them with the form's own rules and shows a summary; the form is then sent as usual (spam checks, notifications, entries unchanged). Files, payments, signatures and consent boxes stay normal fields at the end. Uses your AI source (own key or the WordPress AI connector), with an hourly limit for the site and a limit per visitor; what visitors type is sent as data the AI may not take orders from. When the AI is not available, a limit is reached or the license has lapsed, the normal form is shown. Works on cached pages. Not used on multi-step forms.
    • New (Pro): Smart Edit in the Visual Builder. Type what should change ("make Phone optional", "add a course dropdown after Email"), see the changes, Apply them to the canvas, Undo if you like, then save as usual.
    • New: Visual Builder: a toolbar slot and a small bridge for extensions.
    • Fixed (Pro): a license key now only activates the plugin it was bought for. A key for one of our other plugins is refused with a clear message, and a site already running the wrong key loses the Pro tools at its next license check. Bundle keys are not affected: a bundle gives one key per plugin. Licensing client 1.8.4.
    • New (Pro): three survey fields. Likert / Matrix (statements rated on one scale), Net Promoter Score (0 to 10, the Results page shows the score with promoters, passives and detractors) and Ranking (drag or use the move buttons; works without JavaScript too). Entries, CSV, emails, PDFs, conditional rules, the Results page, {poll_results} and the WPForms import (Likert and NPS fields) all understand them. Survey, quiz and poll features that were free stay free.
    • New (Pro): popup forms. Show any form in an accessible popup: on every page (form settings, General tab) or on chosen pages with [trinity_forms_popup id="12" button="Join us"]. It opens after some seconds, at a scroll depth, when the visitor is about to leave, or from any link to #tf-popup-12; it waits a number of days after it is closed and never opens by itself for someone who sent it. Works on cached pages. Without Pro the shortcode shows the form in the page.
    • New (Pro): voters can see poll results. Put {poll_results} in a confirmation (or {poll_results:field_id} for one question), or add the [trinity_forms_poll_results id="12"] shortcode or the Poll Results block to a page, with an option to show the results only after the visitor votes. Works on cached pages; free-text answers are never shown.
    • New (Pro): integrations can have a rule, "Send only when" or "Don't send when", the same rule notifications have. Every integration and the webhook get it; a skipped send is noted in the entry's log.
    • Improved: accessibility and right-to-left pass on visitor forms. Choice groups (radios, checkboxes, ratings, name, address, survey fields) are a fieldset named by their question; help text is read out with every input; a failed submit marks each wrong answer for screen readers, ties the message to it and moves focus to the error summary or the first problem; a multi-step form no longer jumps to itself on page load. Darker default borders, placeholder, error, success and star colours for easier reading, visible keyboard focus on every button, and Arabic and Hebrew forms put the dropdown arrow, labels and side borders on the right side while emails, phone numbers and totals stay left to right. The Pro signature field can be signed by typing a name.
    • New (Pro): three more View layouts. Calendar shows a month with each entry on its day (a date field such as an event or booking date, or the day it was sent), with previous and next month links, and turns into a list of days on a phone. Timeline lists entries down a line with a heading for each month. Data table adds a page-size menu (10, 25, 50, 100), column sorting, a quick search that narrows the rows on screen as you type (Enter searches every page) and a "Showing 1 to 25 of 120" line; it all works without JavaScript too. Same access rules, search, edit links and magic links as the other layouts.
    • New (Pro): "Where people stop" on the Results screen. For a form that captures partial entries, it shows for each question how many visitors reached it and how many left there without sending, for any date range, with the share who sent the form.
    • New (Pro): your own spam lists. Block IP addresses and ranges (such as 203.0.113.0/24 or IPv6 ranges), block email domains, or accept only listed email domains (for staff or members-only forms), site-wide under Settings > Spam rules and per form in its General settings. Caught entries go to Spam with the rule that caught them; the reason names the rule, not the visitor's address.
    • New: campaign source capture. Turn on "Record where visitors came from" on a form's General tab and each entry keeps the utm_source, utm_medium, utm_campaign, utm_term and utm_content of the visit, the site that sent the visitor and the first page they saw. Shown on the entry, added to the CSV export and available in emails as {utm_source}, {utm_medium}, {utm_campaign}, {landing_page} and {first_referrer}. Kept in the visitor's browser only for the visit, with no cookie, and works on cached pages.
    • New: choose and order the columns of an entry export, and export to Excel (.xlsx) as well as CSV. Entries > Export opens a small panel; filtered to one form, it lists that form's columns to tick and move up or down, and remembers your choice (also used by "Export selected", which gains "Export selected to Excel"). Excel cells are plain text, so leading zeros stay and nothing runs as a formula. CSV files keep the byte order mark Excel needs.
    • New: an option to not store visitor IP addresses. Settings > Data turns it off for every form, or a form's General tab for that form; the default is unchanged. A Stored IP addresses card on Settings removes the addresses already kept (all forms or one). Spam lists, Akismet and rate limits still check the address while a form is sent; the per IP address entry limit needs stored addresses. The personal data export now lists the IP address (when kept), date and browser of each entry, and the CSV/Excel export can include an IP address column when you tick it.
    • New (Pro): Booking field with time slots. Visitors pick a date, then one of that day's free times; you set the open weekdays, opening hours, slot length, a break between slots, people per slot, closed dates, how far ahead and how soon people can book. Free times load live, so cached pages are right too; a full time shows as taken, and the place is checked again under a lock when the form is sent, so two people can't take the last one. Spam, trashed and deleted entries free their place; an unpaid entry holds it for an hour. Opening hours and times are in your site's time zone (Settings > General) and are shown in it everywhere; each booking is saved as an exact moment (UTC), so a daylight-saving change or a later time zone change never moves it, and a time skipped when the clocks go forward is not offered. Emails get a calendar file (.ics, in UTC so every calendar app shows the right local time), and a merge tag links to it. Views can use a booking field for the calendar and timeline layouts. Syncing with Google or Outlook calendars is not included.
    • New (Pro): quotes. On an entry, write a quote (line items with quantity and price, a note, the currency) and send it; the customer gets an email with a private link to a page where they approve or decline it. After approval they pay online through your Stripe, PayPal or Mollie account for exactly the quoted total, or see your offline payment instructions. You get an email when they answer, the entry's activity log keeps every step, and the gateway's normal confirmation marks the entry paid without sending the form's emails a second time. A new quote replaces the old link.
    • New (Pro): native double opt-in. Turn on "Ask people to confirm their email address" on a form's General tab and each entry stays Unconfirmed until the person opens the link in the email they get (subject and text are yours, field merge tags work). The form's notifications and its integrations (mailing lists, webhooks) wait for the confirmation by default; either can go out at once instead. The link works for 48 hours by default; an expired link offers a new one, and the entry screen has Resend confirmation email. Unconfirmed entries have their own tab and are not counted in Results. Forms that need approval go to review once confirmed.
    • New (Pro): stock on product fields. Set how many of each product (or each product choice) you have on the form's Stock tab; the bound Quantity field counts down, a choice that runs out shows as sold out and can't be picked, and asking for more than is left says how many remain. Stock is checked again under a lock when the form is sent, so two people can't buy the last one. Trashing or deleting an entry puts its units back, and a new "Mark as refunded" button on paid entries does too.
    • New (Pro): Lookup field. Fill a field from another form's entries: a dropdown of the answers given to one of its fields (newest first, no repeats, up to 200), or a text box prefilled with the logged-in person's latest answer. "Only the logged-in person's own entries" keeps it to their entries; otherwise every visitor sees the dropdown's values. Email, phone and name fields can be used only with "Only the logged-in person's own entries" on, so a public dropdown never lists other people's contact details. Passwords, files, signatures and payments are never offered, and only finished entries are read. The source field is picked from a list of that form's fields.
    • New (Pro): calculations over repeater rows. In a Calculation formula, sum({items.price}), avg({items.price}), min(...), max(...) and count({items}) work on a repeater's column (rows left empty don't count), on the page as you type and again on the server. The Visual Builder's field settings gain "Used by", listing the fields whose show / hide rules or calculations use the selected field.
    • New (Pro): View extras. One View can list entries from several forms (fields with the same ID share a column). Pin entries to the top of the first page. Add your own text above and below the entries, with {count} for how many there are. Single entry pages can take their browser title, meta description and sharing (Open Graph) title and description from fields of the entry, and can ask search engines not to list them; with Yoast SEO or Rank Math their tags get these values.
  14. v2.22.0Oct 31, 2026
    • New (Pro): choose where AI requests go. Keep your own OpenAI or Anthropic key, or use WordPress's AI connection (Settings > Connectors, WordPress 7.0 or newer) so every plugin shares one key and more providers work. Sites with a key keep using it; the settings say what each choice means.
    • Improved (Pro): Claude Haiku, Sonnet and Opus 5.5 are offered first for form generation and work with it (they refuse settings older models used).
    • New: the AI assistants screen has a "Guide for your assistant" download, a short file that tells Claude or another AI app how to use the Trinity Forms abilities safely.
  15. v2.21.0Oct 31, 2026
    • New: an AI assistants screen (Trinity Forms > AI assistants). Connect Claude Desktop, Claude Code, Cursor or another MCP app and ask it about your forms: how they are built, how they perform, and what people sent. It shows ready-to-paste settings, installs the free MCP Adapter plugin in one click, and lists every request an assistant made.
    • New: reading forms and entries is free. Contact details in entries are masked by default (also inside messages), files, passwords, card numbers, signatures and payment fields are never shown, forms you tick are kept from assistants, and each entry an assistant opens gets a note. It stays off until you switch it on.
    • New (Pro): assistants can build forms. Create a form (saved as a draft), add, change, move or remove fields including conditional logic, publish it, import one, and mark entries read, starred or spam; moving entries to the trash has its own switch. Each change is shown first and saved only when the assistant asks again, and can be undone unless the form or entry was changed since. Forms are changed through the visual builder's own rules, so they open the same in the builder and the block editor.
Older releases (10)
  1. v2.20.0Oct 31, 2026
    • Fixed: entry PDFs print Hindi, Bengali, Tamil and the other Indian languages with their joined letters and vowel signs, and Korean, Chinese and Japanese instead of boxes. Arabic and Persian letters join up and read right to left, and so does Hebrew.
    • New: Forms > Settings > PDF fonts. Fonts for those languages are downloaded once, in the background, when a PDF or the site language needs them, or with a button there. Each file is checked before use. A visitor's form submit never waits for a download.
    • Changed: on a right-to-left site the default PDF layout reads right to left, and each answer keeps the direction of its own language. A custom PDF template keeps the direction you give it. A logo from your Media Library now shows in a custom PDF template; images from other sites are not fetched.
    • Changed: the Pro zip is about 5.3 MB (it was 5 MB).
  2. v2.19.0Oct 31, 2026
    • New: ticking "Delete all Trinity Forms data" asks you to confirm and shows what deleting the plugin will remove.
    • Changed: deleting the plugin frees this site's licence seat, so you can use it on another site straight away. Your data stays unless you ticked the delete box; if you install the plugin again, enter your key again.
    • Fixed: with the delete box ticked, deleting the plugin also removes the saved licence key.
    • Fixed: the licence box answers in your language (a wrong key, Install Pro, deactivating), an unlimited licence shows Unlimited instead of a site limit of 0, and a free key is no longer told it switches on Pro.
    • Fixed: View details on the Plugins screen is there right after you activate the plugin, and its tabs keep WordPress's order.
    • Fixed: the question shown when you deactivate the plugin closes with Esc.
    • Fixed: WPForms notifications set to "Don't send" when a rule matches are imported that way. They used to be imported the other way round and sent to the wrong people.
    • Fixed: a notification's rule shows in the block editor as it works ("Send only when" or "Don't send when"), and you can change it, flip it or remove it there. Before, a "don't send" rule from an import read as "Sent only when" and could not be changed.
    • Fixed: file uploads in entries imported from Forminator, Fluent Forms, SureForms and the other form plugins show as links to the file. They used to show as blank, and entries imported earlier now show their links too.
    • Fixed: saving a form in the block editor no longer removes merge tags written in angle brackets from a notification, like "Name <{your_email}>", and the mail shows the brackets around the address.
    • Fixed: the 3-send limit on one copy of a cached page holds when a bot sends many copies at the same moment. Before, sends that arrived together could all get through.
    • Fixed: a custom PDF template styled with Arial, Helvetica or sans-serif prints Arabic, Persian, Russian, Turkish and Vietnamese text instead of question marks.
    • Fixed: Fluent Forms notifications that greet by first or last name ({inputs.names.first_name}) are imported with the name filled in, using the new {field:<id>:first} and {field:<id>:last} merge tags.
    • Fixed: links in consent text (to a privacy policy or terms page) are kept when importing from Fluent Forms and Forminator.
    • Fixed: imported entries store the choice the visitor picked the same way new entries do, so rules, merge tags and filters match old and new entries alike.
    • Fixed: a required consent box shows its asterisk in the Visual Builder, and a consent text with a link shows as words, not HTML, in both editors.
    • Fixed: with "Delete all Trinity Forms data" ticked, deleting the plugin also removes your forms, the widget settings, the licence state and every saved setting, as the box says. Before, only the entries went. Files visitors uploaded stay in their private folder on the server.
    • Changed: the "Trinity Forms is ready" notice goes away once you open any Trinity Forms screen, not only the forms list.
    • Changed: imported fields get readable ids (and merge tags) when the label is Arabic, Korean or another non-Latin script ({email} instead of {field_1}), and Formidable's generated keys like "xqo5y" give way to the label. A field is never given the id of a built-in merge tag such as {date}.
    • Fixed: dates in entries imported from Ninja Forms are stored the way new entries store a date (2026-01-02), not as the text Ninja Forms showed.
    • Changed: Contact Form 7's demo_mode and skip_mail lines are no longer listed as "not imported" after an import.
    • Fixed: the field list in a rule no longer offers page breaks, sections and HTML blocks, which hold no answer.
    • Fixed: an "is one of" rule matches a choice whose label has a comma in it, like "Group, 5+".
    • Fixed: a form opened in the block editor stays there when you save and reload the page, instead of moving to the Visual Builder.
    • New: Import forms takes several forms in one go. Tick the ones you want, and the result of each is listed after the import.
  3. v2.18.2Oct 31, 2026
    * Fixed: View details on a free install shows the full description, changelog and FAQ, with the video, instead of raw text.
  4. v2.18.1Oct 31, 2026
    • Changed: View details on the Plugins screen shows the plugin's banner, icons and screenshots, loaded from our server.
    • Changed: one copy of a cached page can send the form 3 times. A bot replaying the page's HTML is then asked to send again, like a stale page. Visitors with JavaScript get their own token and are not limited.
    • Changed: the Pro download is smaller (4.8 MB instead of 6.5 MB). PDFs keep Arabic, Persian, Russian, Turkish and Vietnamese text in a <pre>, <code> or serif style in a custom PDF template, where it used to print as question marks.
  5. v2.18.0Oct 30, 2026
    • Fixed: the licence box shows its status, update channel and dates in your site language.
    • Fixed: the Add Trinity form button works inside SiteOrigin's Editor widget, and the Trinity Forms widget no longer shows as missing in SiteOrigin Page Builder after a save.
    • New: import forms from Contact Form 7, WPForms, Fluent Forms, Ninja Forms, Formidable, Forminator, Everest Forms, SureForms and MetForm, with their entries where the plugin keeps them. The forms list says what it found on your site, and anything that could not be brought over is listed after the import.
    • New: a Trinity Forms widget in Elementor, a classic widget for sidebars and SiteOrigin Page Builder, and an "Add Trinity form" button in the classic editor.
    • New: the submit button text and what happens after submit (message, page or address) can be set in the Visual Builder too.
    • New: when a rule is about a choice field, its value is picked from that field's choices. Rules typed as the label now match.
    • New: Arabic translation (review pending).
    • New: after activation the Plugins screen says "Trinity Forms is ready. Start here", once.
    • Changed: the "too fast" spam check uses a signed time token, so a bot posting a copy of a cached page is caught while cached pages keep working for visitors. A page older than 5 minutes asks the visitor to send again instead of filing the entry as spam.
    • Changed: a blank From name sends as your site title instead of "WordPress".
    • Fixed: a notification's sending rules were dropped when the form settings were saved, so a conditional email went out for every entry.
    • Fixed: phone and number answers typed in Persian, Bengali, Thai or Arabic digits were saved empty or refused.
    • Fixed: on a Spanish (or other translated) site, templates, new fields and the submit button started in English, and saving in the block editor turned "Enviar" into "Submit".
    • Fixed: a required consent box sent unticked was accepted by the server.
    • Fixed: entries search finds Persian ی/ک written as ي/ك, Turkish ı/İ in any case, words with or without the Persian ZWNJ, text pasted from a Mac, and phone numbers typed in local digits.
    • Fixed: a Turkish "İstanbul" choice got a value with a hidden dot, so its rule never matched.
    • Fixed: Persian notification emails read right to left; addresses, emails and phone numbers keep their order on right-to-left screens and in mail.
    • Fixed: forms keep the block editor when the Classic Editor plugin is active.
    • Fixed: saving a published form empties the page cache of common cache plugins, so visitors see the change.
    • Fixed: the entry Activity log is in your site language.
  6. v2.17.0Oct 29, 2026
    • New: Hindi translation.
    • Fixed: block names in the block editor now follow your WordPress language.
    • Fixed: the licence box on the Settings screen is now translated.
  7. v2.16.2Oct 28, 2026
    * Fixed: when WP-Cron stopped or a server cron died, webhooks and CRM sends queued in the first few minutes waited for an admin visit. The next form submission now sends them.
  8. v2.16.1Oct 28, 2026
    * Fixed: on hosts with WP-Cron turned off, webhooks, Zapier, Google Sheets and CRM or mailing-list sends now go out with the submission. Before, they waited until you next opened wp-admin, but only when another plugin had loaded Action Scheduler (for example JnK Linkweave). Geolocation and delivery alerts had the same delay and are fixed too.
  9. v2.16.0Oct 28, 2026
    • Fixed: CSV exports showed Korean, Japanese, Arabic and emoji as garbled text in Excel on Windows.
    • Fixed: in Arabic, Hebrew and other right-to-left languages, every Trinity Forms admin screen scrolled sideways.
    • Fixed: the Visual Builder was laid out left to right on right-to-left sites, and long field names in the palette were cut off.
    • Fixed: "wp trinity entry export 12" and "wp trinity entry delete 12" ignored the 12 and acted on every form. They now stop and ask for --form=12.
    • Fixed: the Views "Download CSV" file now opens in Excel with non-Latin text intact, and Chained Select data pasted from such a CSV is read correctly.
  10. v2.15.0Oct 27, 2026
    • Changed: times are now stored in UTC and shown in the time zone set in Settings > General, so a time zone change or a daylight saving switch no longer shifts entry times. Existing entries are converted once, the first time an admin page opens after the update. Do not go back to an older version afterwards, as it would show the times shifted.
    • Fixed: entries imported from Gravity Forms showed the wrong time.
    • Fixed: on a multi-step form, a link to a spot on the same page jumped back to step 1, and after sending, Back walked through the empty steps.
    • Fixed: with JavaScript off, a page from a cache, a file that was too big or too many submissions showed a page of code. The visitor now goes back to the form with the message, and each error names its field.
    • For developers: entry times in the REST API keep site time and gain a submitted_at_gmt field. Entries::get() now returns UTC.
    • For developers: webhook, Zapier and Slack payloads keep submitted_at in site time and add submitted_at_gmt.

Updates arrive in your WordPress dashboard like any other plugin, free version included.