WPForms – AI Form Builder for WordPress – Contact Forms, Payment Forms, Survey Form, Quiz & More

변경이력

2.0.0.2

• Fixed: Form submissions could still be blocked by stricter web application firewall configurations that flagged the JSON structure of the Form Analytics data; the data attached to each submission is now base64-encoded.
• Fixed: A cross-site scripting vulnerability when a page combined a WPForms captcha with a specially crafted OptinMonster campaign.

2.0.0.1

• Fixed: Form submissions could be blocked by a web application firewall, such as Cloudflare’s OWASP ruleset, because of the format of the Form Analytics data attached to each submission.

2.0.0

• Added: New Onboarding Wizard and Setup Checklist page in the WPForms admin menu to guide users through essential configuration steps.
• Added: New Reconnect button for invalid payment connections in the Form Builder Payments Settings panel.
• Changed: The Form Builder Setup panel now opens significantly faster.
• Changed: Updated DOMPurify library to 3.4.11.
• Changed: The AI Chat button in the Form Builder is now shown in grey and displays a tooltip explaining that WPForms AI is not available on local sites.
• Changed: Updated woocommerce/action-scheduler library to 4.0.0.
• Changed: Stripe payment security is enhanced with automatic detection and blocking of card testing attacks and other fraudulent activity.
• Fixed: Randomize the position of the correct answer in AI-generated graded quizzes.
• Fixed: Admin notices about incompatible WPForms versions are now shown only to users who can update plugins.
• Fixed: A choice deleted in the Form Builder could still appear as an empty option on the front-end and triggered PHP warnings on the form view.
• Fixed: The settings gear icon on the Payments, and Dashboard pages was displayed in the wrong color and oversized when Elementor plugin was active.
• Fixed: Form elements could appear disabled after a Stripe 3D Secure authentication failure, even though they remained editable.
• Fixed: The connection icon was displayed in the Builder settings for payment methods even when no account was connected.
• Fixed: Stripe subscription renewals could remain in the Pending status and display an outdated renewal date on the Payment Single page.
• Fixed: Connected payment methods checkmark could still appear in the Form Builder Payments panel after switching to a template without a payment field.
• Fixed: The Weekly Email Summary email content was displayed right-aligned instead of centered in the web version of Gmail.
• Fixed: The Themes panel in the Form Builder Settings did not re-open when its menu item was clicked again after navigating away and back.
• Fixed: A PHP warning was logged when restoring a trashed form on PHP 8.3 and higher.

1.10.2.1

• Added: AI MCP settings section in the Form Builder with the MCP write-access toggle.
• Fixed: Forms scrolled back to the first text input when adjusting a Number Slider in Chrome on Android.
• Fixed: Email notification header sanitization was improved for better security.

1.10.2

• Added: The Abilities API now supports creating new forms, editing existing form fields, and editing form settings.
• Changed: Stripe subscriptions that finish all configured billing cycles are now marked as Completed.
• Fixed: Delete icon overlapped form name in the Bulk Edit Tags field during bulk edits.
• Fixed: Custom CSS configured in the Form Builder was not applied when the form was embedded via the Gutenberg block.
• Fixed: An AbortError: Transition was skipped console error appeared in the Form Builder on WordPress 7.0.
• Fixed: PayPal Credit payment status was not being synchronized in WPForms > Payments.
• Fixed: The Query String Variable smart tag key was unexpectedly reset when the Email field default value was cleared and re-configured in the Form Builder.
• Fixed: Stripe block-editor CSS and JS assets no longer load unconditionally on every Block Editor screen. They now load only when the wpforms/form-selector block is present.
• Fixed: The wpforms_emails_send_email_data filter silently discarded any changes to the headers key before sending the email.
• Fixed: PHP fatal error when submitting a form with the {page_url} smart tag if the page_url POST field was sent as an array.
• Fixed: An invalid notice about Fastlane and alternative payment methods appeared in Stripe and Square subscription payment settings in the Form Builder.

1.10.1.1

• Added: Inline Connect buttons in the Form Builder Payments panel, allowing users to connect their payment accounts without leaving the form editor.
• Changed: The Payments page has a refreshed design when no payments have been received yet.
• Fixed: Fatal error on form submission when the PayPal Commerce account was disconnected while the form still had the PayPal Commerce payment enabled.

1.10.1

• Added: Secret key fields in the admin settings are now masked for improved privacy.
• Added: Smart Form Editing allows modifying existing forms using natural language through an AI chat interface directly inside the form builder.
• Changed: Updated symfony/polyfill-mbstring library to v1.37.0.
• Changed: Updated symfony/polyfill-iconv library to v1.37.0.
• Changed: Updated DOMPurify library to v3.4.1.
• Fixed: The wrong PayPal Commerce connection status was displayed in certain cases.
• Fixed: Form Builder was stuck loading when third-party plugins prevented WordPress footer scripts from rendering.
• Fixed: Settings input values were saved with a trailing space, which could cause unexpected behavior.
• Fixed: Smart tag parsing returned an invalid value when no smart tags were present in the content.
• Fixed: Form Builder was not loading on sites with inconsistent URL configurations (e.g., www vs non-www mismatch or root-relative URL plugins).
• Fixed: PHP fatal errors could occur in some cases on PHP 8.0+.
• Fixed: The Allow/Deny list settings were being cleared when a form had more than one Email field.
• Fixed: Outdated image asset paths were causing 404 errors on sites using the Divi theme.
• Fixed: An incorrect error message was shown when the daily AI request limit was reached, referring to form generation instead of AI usage.

See changelog for all versions.