Luxa Forms — Changelog

1.0.4 — August 30, 2026

Fixed

• A field’s own settings could occasionally revert to blank after saving and reloading the form builder — most noticeable on the Multi-step Form add-on’s “Page Break” field, where a custom Step Title, Next button text, or Back button text typed in would appear to save, then come back empty the next time the builder was opened. This is now fixed, including for fields that had already been affected — no manual re-entry of old data is required after updating.
• Hardened CSV entry exports against a spreadsheet-formula trick some malicious form submissions could use to try to run a hidden formula when the exported file is later opened in Excel, Google Sheets, or similar. Ordinary entry data is completely unaffected.
• Improved the accuracy of spam-protection rate limiting so it can no longer be bypassed by sending fake IP address information with a submission.
• General security hardening of the form builder’s internal data handling.
• Removed an unused, inactive security token that was being generated but never actually checked — the real protection on every form submission was unaffected throughout.

Improved

• Added a small building block that lets add-ons apply their own styling to specific admin screens (used by the Multi-step Form add-on’s builder view, among others) — no visible change on its own.
• Renamed the “All forms” label to “Forms” on the Dashboard and “All Forms” in the navigation menu, for clearer, more consistent wording.

1.0.3 — August 3, 2026

New

• Added the underlying building blocks that let official add-ons (like Conditional Logic and Multi-step Form) plug into the form builder more deeply — extra settings panels, custom validation behavior, and so on. No visible change unless you have one of those add-ons installed.
• A field hidden by an add-on (for example, via Conditional Logic) is no longer incorrectly treated as “required but empty” by the browser before you submit — the server-side check, which was always the real authority, is unchanged.

1.0.2 — July 28, 2026

Fixed

• The “From Email” and “From Name” fields under Settings → Email were being saved but silently ignored — every notification email was sent using your site’s default admin email and site name regardless. Notifications now correctly use your configured sender details.
• Fixed a couple of edge cases where an explicitly blank sender field wasn’t falling back to your site defaults the way it should have.
• Hardened outgoing notification emails against a header-injection technique that could theoretically be attempted through form input.
• Failed email sends are now recorded in Settings → Debug Log, so you have somewhere to actually check when a notification doesn’t arrive.
• Minor performance improvement for forms with multiple active email notifications.

1.0.1 — July 22, 2026

Fixed

• Critical: a background WordPress process (WP-Cron) could encounter a fatal error on sites running Luxa Forms Pro, potentially interrupting scheduled tasks unrelated to forms. This has been resolved — WP-Cron runs are unaffected.

1.0.0 — June 25, 2026

Initial release. Visual drag-and-drop form builder, 15+ field types, AJAX submissions with inline validation, entry management with CSV export, spam protection (honeypot, per-form security token, rate limiting), HTML email notifications, and a shortcode for embedding forms anywhere on your site.

1.0.2 — August 29, 2026

Fixed

• Multi-step forms could appear unusually narrow or cramped on the front end of your site, instead of using the form’s normal full width. Layout now displays correctly.
• Fields set to less than full width (for example, two fields side-by-side at half width each) inside a single step now correctly sit next to each other, matching how they’d appear on an ordinary, single-page form.

1.0.1 — August 29, 2026

Fixed

• On sites also running the Conditional Logic add-on, a required field that Conditional Logic hid could sometimes prevent visitors from moving to the next step, with no visible explanation why. This combination now works correctly.

1.0.0

Initial release. Split any form into multiple steps using a “Page Break” field, with a progress bar, and customizable Back/Next button text per step.

1.0.1 — August 29, 2026

Fixed

• Important: a scripting error could prevent show/hide rules from working correctly for every field in a form except the first one — on affected sites, the add-on could appear to not work at all. This is now fixed; no changes to your existing rules are needed.

1.0.0 — August 3, 2026

Initial release. Show or hide any field — or an entire section — based on the value of another field in the same form, with support for multiple rules combined with AND/OR logic.

Don’t see your question answered here? Check the User Guide, the Installation & License Setup Guide, or the FAQ, or reach out to support directly.