OrgFuse

Changelog

2.4.0

• Season passes: a bundle of events can be sold as one season invoice with tier pricing and a payment due date; every covered event registration links to that invoice, and paying it confirms them all.
• Add-ons can be charged automatically by a form answer (for example, an out-of-state surcharge).
• Registration fields can be pre-filled for signed-in visitors from their account, member record or profile fields, and information blocks can be shown only to signed-in or signed-out visitors.
• Registrations: move to trash, restore, or delete permanently (unpaid registrations only). A registrant opening a trashed registration sees that it was removed.
• Admin: action buttons show an inline spinner while working and a clear error message if something fails.
• Fix: calendar hover cards are no longer clipped by the day cells, and register chips keep their color on hover.
• Fix: saving a package that was imported with a legacy package type no longer fails with “Invalid parameter(s): package_type”.
• Security: every REST route names its permission check where it is registered; invoice, bundle and form-builder routes use dedicated capability methods. Department-limited users stay limited to their own events.
• Security: database queries are fully prepared, and admin, sign-in and account actions check the user’s role before changing another account.
• Scripts and styles: all CSS and JavaScript load through the WordPress enqueue API, including shortcode output and standalone pages (receipt, invoice, unsubscribe, print view).
• Excel export: the .xls report is data only (the header row is no longer bold).
• Pro-only items (extra event and package starters, the calendar subscribe/.ics feed, Pro form field types) are no longer listed in the free plugin; they appear when OrgFuse Pro is active.
• WooCommerce: OrgFuse staff can still reach wp-admin when WooCommerce is active.
• Uninstall: “remove all data” also clears OrgFuse transients, user meta, the OrgFuse Manager role and scheduled events.
• PHP 8.4: CSV export no longer raises deprecation notices.
• Requires OrgFuse Pro 2.3.0 or newer when Pro is installed (an admin notice appears otherwise).

2.3.0

• Forms engine: conditional logic, composite fields (Name, Address), required/format validation, merge tags, confirmations and notifications now come from Digital Bread’s shared forms engine, vendored in src/Vendor/Forms and app/shared/vendor/forms. Behaviour is unchanged except for the fixes below.
• Fix: conditional logic on multi-value answers (Multi-select) is now evaluated on the server the same way the browser shows it, so a field revealed by “contains” is required and validated. Previously the server read the answer as “Array” (and logged a PHP warning).
• Fix: a required multi-value field submitted with nothing selected now counts as missing.
• Fix: “is”, “is not” and “contains” compare accented letters case-insensitively on the server too (É = é), matching the browser.
• Privacy: Core now makes no outbound requests at all. The Help screen and the add-ons screen use content bundled with the plugin, and the optional deactivation feedback form has been removed.
• OrgFuse Pro 2.3.0 needs OrgFuse 2.3.0 or newer and says so in wp-admin if it isn’t.

2.2.1

• Events: Duplicate and Delete actions in the Events list, each with an inline confirmation. A duplicate is created as a draft with its form layout, packages, add-ons, custom fields and email templates. Delete is refused while an event still has registrations, orders, RSVPs, invoices or companion events.
• Admin menu: Settings link added under Members.
• Sign-in forms: the “Forgot your password?” link and “Back to sign in” button stay visible under themes that force button colours.

2.2.0

• Free/Pro boundary: the free edition now contains only fully working features. Card payments (Stripe), Cloudflare Turnstile, Badge Studio, the exhibitor/volunteer portal, the advanced report builder, scheduled reports and license handling live entirely in the separate OrgFuse Pro plugin and hook in through documented filters and actions. Basic CSV export stays free. No change to how Core works on its own.
• Requires OrgFuse Pro 2.2.0 or newer when Pro is installed (an admin notice appears otherwise).

2.1.0

• Hardening: the free Core edition now never contacts third-party payment or CAPTCHA services on its own — the Stripe and Cloudflare Turnstile connection tests are limited to the Pro features that use them. No change to how Core works on its own.

2.0.9

• Housekeeping: completed the free/Pro code split — add-on data-access classes now ship only with OrgFuse Pro. No change to how Core works on its own.

2.0.8

• Fixed the live registration form echoing the confirmation email text above the form; the welcome letter now shows only on the first step and single-step events, never on step two or when returning to an in-progress registration.
• Fixed a pricing indicator that could spin indefinitely when returning to an approved or saved registration.
• Fixed a duplicated section heading on registration forms that use section dividers.

2.0.7

• Registrations: staff can now create a registration on behalf of a member or guest directly from the Registrations screen, then record payment or email a finish-and-pay link.
• Registration forms: signed-in visitors now see a clear notice showing which account they are registering as, with a one-click way to log out or continue as a guest.
• Registrations and receipts now display saved answers and package add-ons with their human-readable labels and values instead of raw field keys.
• Emails now preserve paragraph spacing, keeping blank lines between paragraphs as written.
• Fixed checkbox alignment on public registration forms.
• Added a direct link to a registration’s receipt from the admin registration view.
• Accessibility and layout refinements across the admin and public registration screens.

2.0.2

• Members: delete a member from the member list, with an optional — clearly warned, undoable-only-by-you — choice to also remove the linked WordPress login account. A member’s registrations and payments are always kept and reconnect by email if they register again.

2.0.1

Architecture and packaging release. OrgFuse now ships as a lean free Core plus an optional licensed Pro layer and add-on modules, with a refreshed dashboard. Existing sites keep every feature, setting and record; there is nothing to reconfigure.

• Reorganised the codebase so the free plugin contains only free-tier functionality; Pro features and add-on modules load from the OrgFuse Pro plugin when licensed.
• Refreshed the dashboard: a cleaner quick-access grid, with add-on tiles that appear as you add Pro modules.
• Numerous packaging, escaping and coding-standard refinements for the WordPress.org plugin directory.

2.0.0

First stable release of OrgFuse 2. A complete, modern rewrite built around a REST API and a single-page admin.

• Events and a drag-and-drop registration form builder with conditional fields, packages, add-ons, and two-step (approval) registration.
• Memberships with a member “My Account” area, a member directory, and packages/pricing embeddable by shortcode.
• Orders and manual / alternate payments (check, cash, Venmo, Cash App, external pay links) with a pending → reminder → admin-records-payment flow.
• Public events list, calendar, receipts, and account pages via shortcodes.
• Reports with CSV export, and a built-in zero-config spam-protection stack on every public form.
• Optional Pro upgrade and add-on modules (Exhibitors, Badge Studio, Advertising, Sponsors, Sessions, Fundraising, Communications, Media Vault and more), licensed from orgfuse.com; Core is fully functional without a key.

Development history for the 2.0.0 beta and alpha series is available at https://www.orgfuse.com/changelog.