All notable changes to WPsigner are documented here. Each release lists Edition impact (Lite, Pro, or Both) and Docs links to the guides you should re-read after updating.
How to read this changelog
Section titled “How to read this changelog”| Label | Meaning |
|---|---|
| Edition: Both | Behavior exists in Lite and Pro (or shared core) |
| Edition: Pro | Requires WPsigner Pro (or a Pro addon / integration) |
| Edition: Lite | Affects the free WordPress.org edition |
| Docs | Official guides to open after you update |
Compare editions anytime: Lite vs Pro. New to WordPress.org? Start with First Document on Lite.
v3.3.2.12
Section titled “v3.3.2.12”October 4, 2026 · Edition: Pro
The WooCommerce feed can fill booking line details and the three money figures from the cart or the order: Line item details, Amount due now, Full amount, and Balance due. You pick them in Field mapping. WPsigner does not invent a date or a balance that WooCommerce did not store.
Do not create another contract for a remaining-balance order is on by default. A later order that points at an earlier paid order keeps that agreement. Changing the booking details before payment asks for a new signature. After the order is paid, the same kind of change creates an amendment and emails it. The original sealed PDF stays as it was signed.
Ask an administrator to countersign after payment emails a separate signing link after the customer pays. Payment is not blocked. Apple Pay and Google Pay cannot start until the customer has signed.
Docs
v3.3.2.11
Section titled “v3.3.2.11”October 2, 2026 · Edition: Pro
In the WooCommerce feed, Checkout step is a dropdown. A drawing of checkout shows where the purple signature block sits: after billing, before payments, after payments, on a separate signing page, or by email after the purchase. Trigger on Order Status and After order appear only for After the purchase. Field mapping is two dropdowns, template field to checkout field. You do not type a variable name.
Payment methods stay visible. Place order stays closed until the document is signed.
The contract is visible before the customer enters a name or email. The preview shows the PDF pages only, without the browser’s page thumbnails. On a phone it stays in the signing area. Expand document opens the same pages larger. After the customer enters a billing name and email, the PDF fills those fields. The sentence above the contract is edited in Custom Texts → WooCommerce checkout.
A signature belongs to the order that used it. The next purchase asks for a new signature. A signature that is finished but not yet paid still lets that checkout place the order. After signing on iPhone, checkout loads again and keeps the details saved at Sign.
When the customer already signed, the sealed PDF is attached to the WooCommerce customer Processing email, or the customer Completed email if the order skips Processing. The stored file is not rewritten. A feed that emails a signing link at Completed also sends when the paid order stays on Processing.
On the order screen, Open in WPsigner opens the audit trail.
Docs
v3.3.1
Section titled “v3.3.1”September 24, 2026 · Edition: Pro
A wrong confirmation number on app pairing is counted against that QR code, not only against the visitor’s IP address. After 10 wrong tries the code locks, so the number cannot be guessed from many addresses during the five minutes the QR stays valid.
App login and QR routes stay available when another plugin blocks every REST call that has no WordPress session. The app still checks its own token and confirmation code. If Wordfence closes the connection before WordPress runs, the WPsigner App screen explains how to allow /wp-json/insigner/v1/app/.
Docs
v3.3.0
Section titled “v3.3.0”September 22, 2026 · Edition: Pro
The WPsigner apps are officially available on both stores:
- iOS: App Store
- Android: Google Play
Pair either app with a licensed site from WPsigner → Mobile App. Documents stay on that WordPress site.
The finished PDF shows the document title. A separate first name and last name are combined into the signer’s name.
With Formidable, choosing email sends only the signing email. Choosing the signing page does not also send that email. The download and the email attachment use a readable file name. The email subject and the confirmation page use the form name. A company field maps to the company. Signature boxes stay where you placed them, and each box for a signer shows that person’s signature.
On the client portal you can set the greeting name and hide the role label. Each document belongs to the signer email from the form.
In WooCommerce, each feed can require a signature before payment, or keep creating the document after payment. Different products can use different templates. Until the required document is signed, checkout payment, including Stripe, stays blocked.
Docs
v3.2.38
Section titled “v3.2.38”Edition: Pro
LearnDash keeps a template per course, still lists courses on the settings screen, and unlocks the student after they sign.
On a phone, the PDF keeps its shape. Letters no longer squeeze together, and checkboxes stay on their marks. Converted Word documents keep the spaces between words.
Docs
v3.2.37
Section titled “v3.2.37”Edition: Pro
Signing on a phone keeps the PDF page in the correct aspect ratio. iOS no longer squeezes the letters together, and checkbox boxes stay on their marks instead of stacking.
Docs
v3.2.36
Section titled “v3.2.36”Edition: Pro
Elementor Forms no longer overwrites every field label with “Signature”, and turning the integration off now stays off. Having Elementor Pro installed is not enough to enable the module.
Docs
v3.2.35
Section titled “v3.2.35”Edition: Pro
LearnDash settings stay usable when LearnDash is already active. Enable and Save are not locked on that screen.
Docs
v3.2.34
Section titled “v3.2.34”Edition: Pro
LearnDash can use a different WPsigner template per course. Set a default template, then override it next to each gated course.
Docs
v3.2.28
Section titled “v3.2.28”Edition: Pro
The orange signature box on a Formidable E2Pdf feed is saved with the feed. New submissions place “Click to Sign” where you dragged it.
v3.2.27
Section titled “v3.2.27”Edition: Pro
Formidable feeds read the signer email from the form, including labels such as “correo”. The document is sent and the browser opens the signing page instead of staying in draft.
v3.2.26
Section titled “v3.2.26”Edition: Pro
Show WP Menu restores the WordPress admin bar and sidebar immediately. The WPsigner header no longer shifts into an empty 160px gap.
v3.2.25
Section titled “v3.2.25”Edition: Pro
Formidable E2Pdf feeds create the document and redirect to signing even when the form On Submit action is “Show message”.
Docs
v3.2.24
Section titled “v3.2.24”Edition: Pro
Form feeds can map a first name and an optional last name when those are separate fields.
Docs
Signer name mapping
- First name / full name is required
- Last name is optional — use it when first and last are independent fields
- Leave last name empty when one field already contains the full name
v3.2.23
Section titled “v3.2.23”Edition: Pro
Formidable integration feeds keep every field when you save, and Edit shows the current setup.
Docs
Formidable feeds
- E2Pdf tag on the feed card
- Edit restores the form, template, signers, signature boxes, and what happens after submit
- After submit either sends the signing email or opens the signing page, using what you saved
v3.2.22
Section titled “v3.2.22”Edition: Pro
E2Pdf Formidable feeds include the visual signature placer again.
Docs
Formidable + E2Pdf
- Drag or resize the orange signature box on the page preview
- The signing page uses that placement
v3.2.21
Section titled “v3.2.21”Edition: Pro
Formidable Forms feeds can generate the PDF with E2Pdf again, then send it through WPsigner for signing.
Docs
Formidable Forms + E2Pdf
- If the E2Pdf plugin is active, the Formidable feed shows an E2Pdf template dropdown
- E2Pdf fills the PDF from the Formidable entry; WPsigner adds a signature box and invites the signer
- Do not pick a WPsigner PDF template on the same feed. Extra signers and sequential / parallel order still apply
- Approver role from 3.2.20 is unchanged
v3.2.20
Section titled “v3.2.20”Edition: Both
A participant can approve the document before anyone is invited to sign.
Docs
Approver role
- On Add Signers, set Role to Approver (or Signer)
- That person receives a Review & Approve email, not Review & Sign
- The public page shows the PDF with Approve and Reject — no signature pad
- Signers are emailed only after every approver accepts
- Reject (optional reason) marks the document declined and notifies the sender
- The signed PDF no longer draws a blue bar across the top. Each page keeps a short note at the bottom: electronically signed, the date, and the certificate ID.
v3.2.19
Section titled “v3.2.19”Edition: Pro
Formidable Forms feeds use a WPsigner PDF template or content signing only.
Docs
Formidable Forms
- The feed no longer offers a third-party PDF companion. Extra signers and sequential / parallel order stay on the feed
- Saved feeds that pointed at that companion stop creating documents until you pick a WPsigner template or use content signing
v3.2.18
Section titled “v3.2.18”Edition: Pro
Multi-page PDFs are counted correctly.
Docs
A signature placed on the preview stays on that page of the finished PDF.
v3.2.17
Section titled “v3.2.17”Edition: Pro
Downloading the signed PDF no longer fails with “File not found” when the server cannot draw images.
Docs
If the signature image cannot be drawn, the download still completes. Ask the host to enable image support in PHP so the drawn signature appears on the page.
v3.2.16
Section titled “v3.2.16”Edition: Pro
Signature boxes on a Formidable feed can be resized by dragging a corner or edge.
Docs
Formidable feed editor
- Drag a corner or edge of a signature box to resize it. Width and height update as you drag; you can still type the numbers.
v3.2.15
Section titled “v3.2.15”Edition: Pro
Reopening a Formidable feed keeps name, email, extra signers, and signature boxes.
Docs
Formidable feed editor
- Reopening a feed restores name, email, extra signers, and signature boxes
- Add signature box — the same signer can have several boxes (initials, page 2, etc.)
v3.2.14
Section titled “v3.2.14”Edition: Pro
A Formidable feed can take two or more signers.
Docs
Formidable extra signers
- Additional Signers on the Formidable feed (name + email field per person)
- Sequential signing emails signer 2 after signer 1 finishes; the document is completed only when everyone has signed
- Parallel invites everyone at once (extra signers still get email if the form opens the signing page)
v3.2.13
Section titled “v3.2.13”Edition: Pro
The signing PDF loads on phones again.
Docs
The PDF opens in Safari and in the app. Pinch zoom keeps signature fields on their boxes.
v3.2.12
Section titled “v3.2.12”Edition: Pro
Formidable Forms matches Fluent Forms for content signing, verification codes, and PDF templates. The signing pad stays a signature pad, a real signature is not treated as spam, and the success message can offer the signed PDF. WooCommerce no longer marks WPsigner as incompatible after a recovery.
Docs
Formidable Forms
- Content signing — Name + email + WPsigner Signing (Lite and Pro) or the native Pro Signature field. Feed optional (CC / document title only)
- OTP — Email, SMS, both, or WhatsApp on the Signing field, same as Fluent Forms
- PDF template feeds — Field mapping dropdowns, open-for-signing redirect or email request, CC field + extra addresses
- Signed PDF download — After content signing, Formidable’s success message shows Download Signed PDF. The signed-PDF link still works in notification emails
- Pad on Formidable 6 — The signing field stays a signature pad instead of turning into a text box
- Spam — A real signature is no longer blocked as spam
Signing zoom
- Desktop: Ctrl or Cmd + mouse wheel (trackpad pinch counts). Mobile: two fingers. No + / − bar and no zoom label
WooCommerce
- WPsigner stays compatible with WooCommerce order storage and checkout blocks, including after the plugin recovers from an error
v3.2.11
Section titled “v3.2.11”Edition: Pro
ChatGPT can work with your templates. Sending a document requires a person to confirm first.
Docs
ChatGPT
- Integrations → ChatGPT — Site URL, API key, and instructions for a Custom GPT
- ChatGPT can list templates, preview a document, and send it only after you confirm
- Placeholders in Document Builder text become fields. Signature and initials stay empty for the signer
- Creating a document from written content requires the Document Builder addon
v3.2.10
Section titled “v3.2.10”Edition: Both
Silent zoom on the signing page: Ctrl/Cmd + wheel on desktop, pinch on mobile. No zoom buttons. Fields stay aligned with the PDF.
Docs
v3.2.9.1
Section titled “v3.2.9.1”Edition: Pro
The mobile app follows the same audit trail and sending rules as WordPress.
Docs
-
Fields saved from the app keep their names, and show-or-hide rules still apply
-
Verification, identity checks, and access codes use the same Always / Per document / Off choices as the website
-
In-person signing from a draft uses those same checks
-
The app downloads the completed PDF correctly, including the certificate of completion
-
The audit trail in the app matches the one in wp-admin
-
The identity-check report downloads the same compliance PDF
-
The document list in the app loads faster
v3.2.9
Section titled “v3.2.9”Edition: Pro
Docs
-
Void from the app — Cancel a draft, sent, or viewed document. Signing links stop
-
Upload and send — If a document has no fields when it is sent, WPsigner places one signature box per signer
-
Cancelled documents are included in the statistics
v3.2.8
Section titled “v3.2.8”Edition: Both (sender-chosen access codes) · Edition: Pro (Fluent Forms CC field)
Sender-chosen access codes with an optional prompt, safer delivery of known secrets, and Fluent Forms CC from a form field.
Docs
Access codes
- I’ll set the access code — 4–8 digits you choose (last 4 of SSN, date of birth
MMDDYYYY, and similar), plus an optional Signer prompt on the signing page - Generate a random 6-digit code — same as before; after send you can still copy the PIN
- Include access code in signing email — off by default when you set your own code, so the invite can be the link only
- Request access code — only for random codes, and only to the signer’s email or the phone already on file. Known secrets cannot be resent from the signing page
- Existing documents keep their access code. You do not need to resend pending envelopes
Fluent Forms (Pro)
- CC email field on the feed — map a Fluent Forms Email field (typed or filled from the URL) onto the signed-PDF / completion CC
- Additional CC emails — optional fixed addresses, combined with the mapped field
- Works for content-signing feeds and PDF-template feeds
v3.2.0
Section titled “v3.2.0”Edition: Pro
Unicode signed PDFs, WordPress user picker on Add Signers, and an optional per-signer WordPress login gate. This is the release that includes the work built on top of 3.1.3 (Appearance and Bulk Send stay in that version).
Docs
Signed PDF fonts
- Languages → Signed PDF fonts — Optional Noto packs so flattened signed PDFs keep accents and non-Latin scripts. Does not translate the WPsigner screens
- Packs — Accented Latin (Vietnamese, Turkish, Polish, and other Latin languages with accents), Japanese, Chinese Simplified, Chinese Traditional, Korean, Arabic, Hebrew, Thai
- One active pack — Install only what you need. Use for signed PDFs sets the active pack
WordPress signers
- User search — Type at least two characters in a signer name or email to pick an existing WordPress user
- Add me as signer #1 — Fills the first row with the current account. Does not turn on the login gate by itself
- Signer order — The first person you add is Signer #1 (their signature fields). Drag rows to change the order
- Use Template — Same search and checkbox per slot (for example signer #1 must log in, signer #2 can be a guest)
WordPress login for a signer
- Per signer, off by default — Check Require WordPress login with this email. The email must already belong to a WordPress user (the checkbox is turned off if it does not). The signing token is not enough; the WordPress account email must match that signer
- Same message on the signing page — Log in (or log out and switch accounts) and return to the document
- Does not replace OTP, KYC, or access codes
- No campaign hybrid — An active public campaign cannot share a document with a gated signer, and you cannot turn the checkbox on while a campaign is active. Individual links for those signers are not redirected to the campaign URL. Public reuse of that email still requires the matching WordPress login
- Bulk Send and public guests — CSV rows and new public-campaign signers do not get this gate
Download from your Account Portal.
v3.1.3
Section titled “v3.1.3”Edition: Both (Pro 3.1.3, Lite 1.0.2)
Official compatibility with WordPress 7.1 and WooCommerce 11.0.1. Sending and signing are unchanged. The WooCommerce integration uses orders and does not change the checkout form.
Pro also adds Appearance (brand, signing-page buttons, and client portal on one page) and Bulk Send (CSV invitations from a template, with a tag you name for each send).
Docs
Signing page buttons (Pro)
- Signing Page tab — Under More → Appearance. Pixel controls for font, padding, corner radius, and border width, plus color, hover, style (solid / outline / soft), weight, and width. S / M / L remain as shortcuts that fill the pixel fields
- Live preview — Sidebar mockup updates as you edit, with a light/dark toggle and a contrast warning when text is hard to read
- Applied everywhere signers tap a primary action — Finish, Apply, OTP, KYC, the public “start signing” button, and campaign embeds. Decline stays red
- Brand color finally reaches the signing page — A custom Primary Color from Appearance → Brand now styles signing buttons. Stock plugin blue/indigo is unchanged until you save a custom button color
- Button labels stay in Custom Texts — Finish, Complete, and Decline copy is still edited there
- No flash of default styles — Brand colors, theme, and fonts apply on the first paint so signers do not see a generic look first
- Appearance hub — Brand, Signing Page, and Client Portal are tabs on one Appearance page. Previous Signing Appearance and Client Personalization URLs redirect there
Bulk Send (Pro)
- Documents menu — New Bulk Send item next to Documents, plus a button on the Documents list
- CSV — Download a sample file (
name,email, optionaltitle). Up to 200 rows - Batch name = tag — You name the send; every document in that send gets that tag so you can filter the batch in Documents
- Emails in batches — Default 4 per step (1–20). Pause, cancel, or leave the page; the rest continue on their own
Download from your Account Portal. Lite updates via WordPress.org.
WPsigner for Uncanny Automator 1.2.0
Section titled “WPsigner for Uncanny Automator 1.2.0”Edition: Pro (official addon)
Native Uncanny Automator integration: field tokens and prefill, cloud/payment/delete triggers, messaging actions, signer loops, and a settings page for signing-URL privacy.
Docs
1.2.0
- The recipe shows which signer slots the template uses, up to five signers
- Template fields can be filled from the recipe
- Triggers for cloud backups, document update/trash/delete, Stripe fail/refund
- Channel reminders (WhatsApp, SMS, Slack, Telegram, Teams) and Slack custom message
- Automator Pro condition “signer is a WordPress user” and loopable signer tokens
- Settings to hide signing URLs and field values; hourly create cap
Previously 1.1.0 added certificate/owner/tag tokens, PDF and Stripe succeeded triggers, tag/signer/expiration actions, and the “document has tag” condition. 1.0.0 was the initial integration.
v3.1.1
Section titled “v3.1.1”Edition: Pro (forms integrations)
Fluent Forms and WPForms reliability for larger forms with inline signing and OTP, safer signer name detection, and a clearer PDF field editor (name / mapping popup and delete control).
Docs
Forms & OTP
- Fluent Forms OTP submit — Large forms with a signature and a verification code no longer fail after a successful verification
- Fluent Forms email field — OTP uses the feed’s mapped signer email instead of guessing the wrong field on complex forms
- WPForms OTP + feeds — Same reliability: session OTP fallback, smarter name/email detection (avoids “Username”), OTP only when a signature is present, and content-signing feeds save without forcing a template
- Signer name field — Name detection no longer mistakes “Username” for the person name; Fluent Forms
names(first/last) is preferred - Content-signing feed save — Saving a feed for inline signing no longer asks for a template when Feed Name and Form are already set
PDF field editor
- Field Properties (double-click) — Set Field name, optional Mapping name (Zapier / forms), and Placeholder. Docs: Form fields
- Floating popup — The editor opens outside the field box (not clipped inside it)
- Delete (X) — The remove control sits outside the field corner again
Content signing
- Multiple signatures (Fluent Forms / WPForms) — Forms with several WPsigner Signing fields include every filled signature on the generated PDF, each with its field label
- Form tags in Documents — Documents created from form integrations get a tag like “Form: [form name]” (same idea as Campaign tags)
- Certificate of Completion (forms) — Signature thumbnails load correctly for content-signing documents; multiple Signing fields appear as separate cards labeled with the form field name (e.g. Client / Witness)
Download from your Account Portal.
v3.1.0
Section titled “v3.1.0”Edition: Pro (portals, campaigns, team roles) · shared admin/diagnostics for Pro installs
A clearer admin experience, better portals, smarter team access, more reliable campaigns, and safer storage tools. Your existing documents and signer data are kept when you update.
Docs
- System Status & Storage
- Client Portal
- Team Roles & Permissions
- Campaigns
- Form Fields (VAT field)
- Security & Compliance
- Languages
Easier admin screens
- System Status is a practical diagnostics hub (compatibility, storage, cron repair, and cleanup tools when you need them)
- Storage & Retention uses the same clear layout as the rest of WPsigner
- License page matches the standard WPsigner admin design (activate, verify, renew, and remove license with less confusion)
- Signer Protection cards (OTP, KYC, Access Code) line up evenly on Security & Compliance
- Security settings save button stays aligned correctly
Client Portal and Admin Portal
- Cleaner Client Portal login and document list (items that need attention appear first)
- Option to hide your theme header and/or footer on portal pages
- “Enable Client Portal” now saves correctly
- Front-end Admin Portal: clearer stats, activity, and “needs attention” view
Team access that matches each role
- Dashboard shows all documents for Managers, Viewers, and Admins; Senders still see only their own
- Viewers no longer see a New Document button they cannot use
- Users page works for inSigner Admins (not only WordPress Administrators)
- Clearer “No Access” option when assigning roles
Campaigns — one completed document per signature
- Each campaign signature is saved as its own completed document in Documents, with the campaign tag
- Audit trail opened from a submission focuses on that independent signed document (not the shared template)
- Campaign signed PDFs and certificates no longer show the internal “Campaign template” as a signer
- Empty “Pending” boxes from that template no longer appear on campaign PDFs
- Campaign links stay open for many people to sign; the shared template is not closed after the first submission
- Legacy shared-template submissions are promoted to independent documents when you open Submissions, Audit, or Download
Fields and languages
- New VAT field type available in the PDF editor, campaigns, Document Builder, and the signing page
- Language packs update correctly
- A regional language (for example Spanish for Spain) is preferred over an older generic pack
Storage — Delete Everything
- Storage → Delete Everything permanently removes all documents and PDFs (including signed), plus templates, campaigns, submissions, tags, payments, and audit logs
- Runs in safe batches so large libraries do not time out the server; keep the page open until it finishes
- Plugin settings and license are kept
Signing experience and small fixes
- Legal Notice from settings is included on the certificate page of the signed PDF
- Telegram Chat ID in the document wizard only appears when Telegram is connected
- Signing page “Page X of N” controls stay readable with common themes (including Astra and WooCommerce)
- Creating and sending signature requests is done in WordPress admin under New Document; the front-end Admin Portal is for reviewing status
Download from your Account Portal.
v3.0.1 – v3.0.x
Section titled “v3.0.1 – v3.0.x”Edition: Pro
Incremental fixes and integration improvements shipped between 3.0.0 and 3.1.0, including Fluent Forms feed UI and OTP, Contact Form 7 parity, WhatsApp Complete Setup, language packs foundation, Storage & Retention tools, and related hardening. These builds are superseded by 3.1.0.
Docs
v3.0.0
Section titled “v3.0.0”Edition: Pro
Major release with official addons, Fluent Forms content signing, and Stripe improvements.
Docs
-
Addons marketplace — WPsigner → Addons to install and activate official extensions
-
Account Portal integration — Download addons from app.wpsigner.com
-
Smart Signing Forms (addon v1.6.0) — Drag-and-drop signing forms with design presets, OTP, Stripe payments, and signed PDF output
-
Fluent Forms content signing — Sign inline with the WPsigner Signing field; PDF generated from form content without a template feed
-
Fluent Forms OTP — Email, SMS, and WhatsApp verification on the Signing field before submit
-
Fluent Forms merge tags —
{inSigner:signed_pdf_url}and{inSigner:download_button}in notification emails -
Stripe — Payments are confirmed before the PDF is created. Restricted API keys are recommended
-
Submission blocked when content-signing PDF generation fails (no orphaned Fluent Forms entries)
-
Security and compatibility improvements across signing and integrations
Download from your Account Portal.
Smart Signing Forms v1.6.0 (addon)
Section titled “Smart Signing Forms v1.6.0 (addon)”Edition: Pro · Docs: Smart Signing Forms
- 4-step wizard: configuration, form builder, design presets with live preview, compliance
- Field types: signature, payment (Stripe), OTP, columns, conditionals, file upload, and more
- Stripe payment is confirmed before the PDF is created
- Entry management with signed PDF download and audit trail links
v2.5.0
Section titled “v2.5.0”Edition: Both (field editor / signing UX) · Pro addons page
A major update to the field editor and the signing experience.
Docs
-
Checkbox groups — place checkboxes anywhere on the PDF and set optional, “pick at least one”, or “pick exactly one” rules.
-
Conditional fields — show, hide, or require fields based on what the signer answers.
-
Right-click menu on fields to clone, delete, or change checkbox options.
-
Checkbox stamp mode — drop one checkbox, then click to add more. Press Escape when you’re done.
-
Custom labels and placeholders — double-click any field to edit.
-
Addons page — Smart Signing Forms available; Flow Builder coming soon.
-
Better signing page on mobile, especially for long PDFs.
-
Fields stay in place when you zoom in the editor.
-
Dates and times now match your WordPress site timezone everywhere.
-
Saves no longer lose fields on multi-page documents.
-
Public document verification page works reliably.
-
Signing links and PDF viewing work better with caching and security plugins.
Download from your license portal.
v2.4.0
Section titled “v2.4.0”Edition: Pro
Interim release with webhook reliability, admin tooling, and integration prep ahead of the 2.5.0 field-editor work.
v2.3.1
Section titled “v2.3.1”Edition: Pro
Security and reliability improvements:
Docs: REST API · Webhooks · Security & Compliance
- Stronger protection for API access and signing order.
- Webhooks fire correctly again when documents are signed or completed.
- Better IP detection when your site uses Cloudflare or a CDN.
- Safer storage for certificates and integration credentials.
- General hardening across the signing page and admin.
v2.3.0
Section titled “v2.3.0”Edition: Pro
Docs: Didit · Twilio · Security & Compliance
- Identity verification with Didit.me. Signers can now verify their identity with a government ID, selfie, and liveness check before signing. You set it up once and get real-time status updates.
- SMS verification via Twilio. Signers can verify by text message, email, or both.
- New option in settings to choose how verification codes are delivered.
- The signing page now adapts based on the verification method you’ve picked.
v2.2.3
Section titled “v2.2.3”- Encryption is now set up automatically when you install the plugin. One less thing to configure.
- Fixed Google Drive disconnecting when the token expired. Reconnection is handled automatically now.
- Admin notices now link directly to the relevant setup guide instead of a generic settings page.
v2.2.2
Section titled “v2.2.2”- Redesigned the timestamp verification email. Much clearer now.
- Blockchain verification links open a clean branded page instead of a raw URL.
- Fixed an edge case where some timestamp providers were incorrectly filtered out.
v2.2.1
Section titled “v2.2.1”- IP detection now works correctly when your site is behind Cloudflare, load balancers, or reverse proxies.
- All parts of the plugin now use the same IP source, so rate limiting and audit logs stay consistent.
- Added support for custom proxy headers if your hosting setup needs it.
v2.2.0
Section titled “v2.2.0”Big encryption upgrade. Your stored credentials are now much more secure.
- Encryption keys come from your site’s unique WordPress configuration instead of the database.
- Certificate passwords use stronger encryption with unique keys for each operation.
- Tighter file validation across uploads, downloads, and templates.
- Location lookups are encrypted in transit.
- You’ll see a warning if encryption keys change after a site migration.
v2.1.1
Section titled “v2.1.1”- Fixed a crash on mobile with large PDFs (100+ pages).
- Pages now load as you scroll, so your device doesn’t run out of memory.
- Automatic cleanup for pages you’ve scrolled past.
- Better performance on lower-end phones and tablets.
v2.1.0
Section titled “v2.1.0”- Rate limiting on all API and integration endpoints.
- Security review of every admin form and input field.
- Third-party credentials (API keys, tokens) are now stored encrypted.
- Plugin uses ~12% less memory.
v2.0.2
Section titled “v2.0.2”- Reorganized the integrations page by category: Forms, Messaging, Automation, CRM, Cloud Storage.
- Added “coming soon” labels for Make, n8n, Telegram, Gravity Forms, Dropbox, and Teams.
- New card designs with official brand icons for each integration.
v2.0.1
Section titled “v2.0.1”- Fixed PDF viewer not loading on some shared hosting setups.
- Fixed WhatsApp templates breaking when document titles have special characters.
- Better loading indicators for documents over 20 pages.
v2.0.0
Section titled “v2.0.0”Biggest release since launch.
- WhatsApp Business. Send signing requests, reminders, and completion notifications via WhatsApp.
- Integrations Hub. New admin page showing all integrations and their connection status.
- Google Drive. One-click setup. Signed PDFs are saved to your Drive automatically.
- License System. Manage plugin licenses through WooCommerce.
- Smoother mobile signing with larger buttons and better scrolling.
v1.9.1
Section titled “v1.9.1”- Signers now see the full document first instead of being auto-scrolled to the first field.
- Better keyboard navigation and accessibility across the signing page.
- Fixed a validation issue with the consent checkbox on Safari and iOS.
v1.9.0
Section titled “v1.9.0”- OTP Verification. Signers confirm their identity via email before signing.
- Location capture. Optionally log where signers are located for richer audit trails.
- Browser, platform, and timezone are now included in the audit trail.
- Consent checkbox gets its own timestamp for compliance records.
v1.8.0
Section titled “v1.8.0”- REST API. Full API with key management, permissions, and rate limits.
- Zapier integration. Connect WPsigner to 6,000+ apps with real-time triggers and actions.
- API documentation with examples in PHP, JavaScript, Python, and cURL.
- Cleaner email templates.
v1.7.0
Section titled “v1.7.0”- Roles. 4 roles: Sender, Viewer, Manager, Admin. Each with specific permissions.
- Download links for signed documents now expire after 48 hours.
- You can add custom messages to signing request emails.
- More reliable auto-reminders, even on sites with inconsistent WordPress cron.
v1.6.0
Section titled “v1.6.0”- Translations. English, Spanish, Italian, French, German, and Portuguese (Brazil).
- All fonts and scripts are self-hosted. No external requests, fully GDPR compliant.
- Pages load ~300ms faster.
v1.5.0
Section titled “v1.5.0”- Digital ID. Generate a self-signed certificate directly from the settings page.
- Elementor Forms and Fluent Forms integrations. Turn form submissions into signing documents.
- New system status page with a health score, auto-fix tools, and debug export.
- Dashboard widget showing health score and pending reminders.
v1.4.0
Section titled “v1.4.0”- Security Center. New settings page with a real-time compliance score.
- Upload your own certificates for Adobe-verified digital signatures.
- Timestamp Authority integration for legally provable signing times.
- 6-digit access codes for sensitive documents.
- Compliance badges for ESIGN Act, eIDAS, and UETA.
v1.3.0
Section titled “v1.3.0”- Webhooks. Get real-time notifications when documents are signed, viewed, or completed.
- Compatibility fixes for WP Rocket, LiteSpeed Cache, and Autoptimize.
- Added Portuguese (Brazil), French, and German translations.
v1.2.0
Section titled “v1.2.0”- Document Wizard. 4-step guided flow: Upload, Signers, Fields, Review.
- Sequential signing: set a strict order or let everyone sign at the same time.
- One-click copy for signing links after sending a document.
- White-label: use your own logo, colors, and footer text.
v1.1.0
Section titled “v1.1.0”- Multi-signer support. Up to 6 signers per document.
- Color-coded fields so each signer’s fields are easy to identify.
- Quick-share modal for signing links.
v1.0.0
Section titled “v1.0.0”Initial release.
- PDF upload with drag-and-drop.
- Electronic signatures: draw, type, or upload an image.
- Form fields: signature, initials, date, text, checkbox.
- Automatic email notifications for signing requests and completions.
- Audit trail with timestamps, IP addresses, and action logging.
- PDF certificate of completion with QR code verification.
- Works on desktop, tablet, and mobile.