OrgFuse

Journal des modifications

2.5.10

Fixes from the second demo review (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.9 below.

• Payments: Venmo, Cash App and the « Pay online » link are clickable buttons (« Pay with Venmo », « Pay with Cash App », or your own label) on the registration form, in the how-to-pay email and in payment reminders, which now list the payment methods too. A Venmo handle opens venmo.com/u/handle and a cashtag opens cash.app/$cashtag; a full pay link, when set, is used instead. Settings refuses handles with spaces or symbols and links that aren’t https:// on the right site. [R-66]
• Payments: new Settings switches to stop offering check / money order or cash to registrants. The « Request to pay by… » button names the methods you offer (unchanged when you offer only check, money order and cash), and the membership check setting is labeled « Membership form: offer pay by check ». [R-68]
• Payments: staff can record a payment made through the « Pay online » link. It shows under your link label (or « Online (external link) ») in Record payment, Payment history, receipts, exports and System Status. [R-69]
• Packaging: the build fails if the zip would contain a second copy of the plugin (trunk/, tags/ or branches/ folders, or a second orgfuse.php). [R-65]
• Form builder: a package’s price summary shows the member price, then the guest price, as intended. [R-67]
• Dashboard: the OrgFuse widgets count and list open events whose date is today or later, in date order. [R-70]
• No database schema changes.

2.5.9

Additions to the 2.5.8 fixes (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.8 below.

• Rich-text editor: switching between « </> HTML » and « ◀ Visual » keeps keyboard focus on the switch. [R-60]
• Rich-text editor: the toolbar is a single Tab stop (the arrow keys move between its buttons), and Bold, Italic and Underline announce whether they’re on. [R-61]
• My Account: « View / print » on the Registrations tab opens the printable receipt in a new tab. A registration with a balance due also shows « Pay now », which opens the registration form. [R-62]
• WP-CLI: the one-line help for wp orgfuse scrub-email-subjects, wp orgfuse dun and wp orgfuse event purge no longer stops mid-sentence. [R-63]
• Registration console: « Copied! » after Copy live link is announced to screen readers. [R-64]
• No database schema changes.

2.5.8

Fixes from the 2.5.7 retest (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.7 below.

• Event editor: the Description editor is named by its label for screen readers, its toolbar is a labeled toolbar with plain button names (« Bulleted list », « Insert image », « Clear formatting », « Edit HTML »), and its buttons now work from the keyboard. [R-54]
• Event editor: Escape, × or Cancel after changing Basics, Registration or Fields asks « Discard unsaved changes? » first, with focus on Keep editing. An untouched event still closes straight away. [R-55]
• Registration console: on a phone the search box and the « + New registration » and « Export CSV » buttons wrap, so the page no longer scrolls sideways. [R-56]
• Privacy: on update, emails kept by permanent deletions made before 2.5.6 have the registrant’s name removed from the subject, once, logged under System Status > Permanent deletions as a count only. Also available as wp orgfuse scrub-email-subjects. [R-57]
• Readme: scholarships are listed as part of Core, not Pro. [R-58]
• My Account: the Payment history number column is headed « Order # ». [R-59]
• No database schema changes.

2.5.7

Additions to the 2.5.5 retest found while recording the demo (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.6 below.

• My Account: on a phone, the registrations, payment history and invoices tables show each row as a card of labels and values, so the page no longer scrolls sideways. [R-51]
• Register page: the event description stays on screen after « Request to pay by check » and on the confirmation, like the venue card. [R-52]
• Readme: the Core and Pro descriptions now list the registration console (approve, deny, record payments, pay links and other emails) as part of Core; Pro adds card refunds and voids. [R-53]
• No database schema changes.

2.5.6

Fixes from the 2.5.5 retest (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.5 below.

• My Account: event dates, membership dates and upload deadlines use your site’s date and time format, like the payment history. The Season Pass event list does too. [R-44, R-10]
• My Account: the tab that holds the payment history is named « Payment history » (or « My invoices » when there are only invoices), matching its heading, and each tab is linked to its panel. [R-45]
• Accessibility: every field in the event editor has its own name (« End date », « End time », « Registration opens: time », « Contact phone », « Contact email » and so on), and paired fields are grouped under their row label. [R-46]
• Accessibility: closing the event editor (Escape, Cancel or ×) returns focus to the button that opened it, including « + Add event » when the editor was opened from the starter gallery. The « Unsaved form changes » prompt is an alert dialog that starts on Cancel, and Escape keeps the editor open. [R-47]
• Event editor: ticking or unticking a package shows and announces « Package added: … » or « Package removed: … ». [R-48]
• Permanent delete: the email log rows that are kept no longer contain the registrants’ or attendees’ names or addresses in their subjects (« [removed] »), and the audit entry for a registration names only its number. Entries written by 2.5.5 are cleaned the next time System Status is opened. [R-49]
• Registration console: on a site with no events yet, organizers who can manage events see « No events yet. » with a « Create an event » link instead of « No events are assigned to you yet. » [R-50]
• No database schema changes.

2.5.5

Fixes from the 2.5.4 retest (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1, 2.5.2, 2.5.3 and 2.5.4 below.

• Events: site administrators can permanently delete a test or demo event with all its data (registrations, including trashed ones, orders, recorded and gateway payments, RSVPs, invoices, attendees, answers and uploads). The new row action « Permanently delete… » appears only when the normal Delete is blocked, lists exactly what will be removed, and stays disabled until the event’s title is typed. Everything is removed in one database transaction, or nothing is. Email log entries are kept with the address removed. WordPress users are kept. Each permanent deletion is recorded under OrgFuse > System Status > Permanent deletions. New REST routes: orgfuse/v1/events/{id}/purge and orgfuse/v1/registrations/{id}/purge-all (both require manage_options), new action hooks orgfuse_event_purged and orgfuse_registration_purged, and new WP-CLI command wp orgfuse event purge <id> --yes --user=<admin>. [R-42]
• Registrations: a paid registration in Trash can be permanently deleted with its payment records by a site administrator (« Permanently delete (including payment records)… », typed DELETE to confirm). The normal Delete permanently still refuses, and its message now points at this action. [R-42]
• Events: the message when an event can’t be deleted names both ways out (« Archive it to hide it, or use Permanently delete… to remove it and all its data ») and counts read « 1 registration and 2 orders ». [R-42, R-43]
• Accessibility: confirmations without a separate note (Duplicate event, Delete package) no longer repeat their question as a description. [R-40]
• Accessibility: Move to trash and Restore in the registration window announce « Registration moved to trash » and « Registration restored », and focus moves to Restore or Delete instead of the page. [R-41]
• Registration console: « Send pay link » asks « Send a payment link to …? » first, starting on Cancel, like Resend confirmation.
• New option orgfuse_purge_log (not autoloaded) keeps the last 200 permanent deletions. No database schema changes.

2.5.4

Fixes from the 2.5.3 retest (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1, 2.5.2 and 2.5.3 below.

• Accessibility: every row and inline confirmation (Delete and Duplicate on Events and Packages, invoice Void, Refund and Delete, invitation Delete, venue Delete, member Delete, account merge, and the console’s Resend confirmation and Block & remove) is announced as an alert dialog with its question, starts on Cancel, and Cancel or Escape returns focus to the button that opened it. After a row is deleted, focus moves to the same button on the next row and the result is announced. Pop-up confirmations keep focus inside, start on Cancel and return focus when closed. Error messages above lists are announced. [R-37]
• Registration console: the payment summary reads « Total due: » like the receipt. [R-38]
• Payment methods: PayPal, Square, card and free orders have their own labels, so brand names keep their spelling. [R-39]
• No database schema changes.

2.5.3

Fixes from the 2.5.2 retest (issue IDs in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1 and 2.5.2 below.

• Receipt and receipt PDF: the status uses the same words as every other screen (« Status: Paid », « Status: Payment due », « Status: Partially paid ») instead of upper-cased codes, and follows the orgfuse_status_labels filter. The .paid and .due classes are unchanged, so custom CSS (including text-transform) still applies. [R-28, R-11]
• Payment methods: one list of method words for wp-admin, the console and receipts (« Other (requested) », « Recorded manually », « Money order »), filterable with the new orgfuse_method_labels filter. The console’s order panel shows order statuses from the shared list, so a completed order reads « Completed » in both places. CSV columns and values are unchanged. [R-29, R-11]
• Orders: the order window’s Payments table shows the date a recorded payment was received, in your site’s date and time format. [R-30, R-10]
• Accessibility: the « Close registration… » confirmations in wp-admin and the console are announced as alert dialogs, start on Cancel, and Cancel or Escape closes only the confirmation and returns focus to « Close registration… ». After closing, focus moves to Reopen. [R-31]
• Registration console: the event-level button is now « Stop accepting registrations… » and always asks « Stop accepting new registrations for {event}? Existing registrations are kept. » first. The reverse reads « Reopen event registration ». [R-32]
• Accessibility: settings and event-editor checkboxes have one name (the row label) instead of two, row notes are linked as their description, and clicking the row label still toggles the box. [R-24]
• Registration console: the status filter chips report whether they’re selected and read as « Paid (4) ». [R-33]
• Registration console: switching events loads the list and counts once, for the new event’s current season. [R-34]
• Orders: a resolved « Other payment requested » order, or one whose registration has nothing due, no longer offers Record payment and points staff to the registration. [R-35]
• Settings: « Saved » and save errors next to the Save button are announced to screen readers. [R-36]
• New filter orgfuse_method_labels. No database schema changes.

2.5.2

Fixes from the 2.5.1 retest (issue IDs in brackets).

• Registration console: Export CSV downloads the Event Report columns for the current event in the free plugin, following the status, Unpaid and season filters. With OrgFuse Pro’s Report Builder the column picker opens as before, and it shows an error with a standard-CSV fallback if its columns can’t load. [R-18]
• Registration console: the registration panel is a dialog (focus moves in and stays, Escape closes it, focus returns to the row). « Close » the status change is now « Close registration… », sits with Trash and asks first; the panel’s × is « Close panel ». The wp-admin registration window works the same way. [R-19]
• Dates: the Registrations « Created » and Orders « Date » columns, System Status « Recent emails » and the Event Reports season filter use your site’s date and time format. The Events list column reads « Event date ». CSV values stay ISO. [R-10]
• Status words come from one list everywhere: lists, windows, the event report, the console (badges, order panel and filter chips) and the CSV, in sentence case (« Payment due », « Other payment requested »). [R-11]
• Payments: when a registration is paid in full, denied or cancelled, its open « Other payment requested » orders are marked « Request resolved » with a note such as « Resolved: paid by order #7 ». A one-time upgrade does the same for existing paid, denied and cancelled registrations. Amounts and payments never change; unpaid and closed registrations keep their requests, so payment reminders are unaffected. [R-20]
• Registration console: recording a payment shows and announces « Payment recorded — $25.00 Check ». [R-21]
• Live registration: while a balance is due, the edit view shows the amount due and how to pay (accepted methods, payee and mailing address on check events, your instructions) with « Request to pay by check / money order », or « Request received » once asked. [R-22]
• After « Request to pay by check / money order », the confirmation keeps the amount and how to pay (« Mail it to the address below and write registration #6 on the memo line »). [R-23]
• Accessibility: « Allow check / money order » has visible help text, the follow-up message field is labeled, and Settings row labels are tied to their control (clicking « Accept check / money order » toggles it). The event setting reads « Accept check / money order for this event » with a note on what registrants see. [R-24]
• Readme: no internal issue IDs outside the changelog. [R-25]
• Receipt: a first address line that repeats the organization or payee name is skipped, so the name prints once. [R-26]
• Orders: the Method filter lists the Record payment methods, Card only when a card gateway is active, and any method already on an order. [R-27]
• New REST route GET /orgfuse/v1/reports/registrations-csv (staff who manage registrations, scoped to their events) and filter orgfuse_status_labels.
• No database schema changes. The request clean-up runs once and records itself in the orgfuse_alt_requests_cleanup option; settled orders use the new alt_resolved order status.

2.5.1

Fixes from the 2.5.0 retest (issue IDs in brackets). Ships as 2.5.1 because 2.5.0 is already released.

• Payment reminders: a registration that still owes money on an event that accepts check / money order, or whose registrant asked to pay another way, now gets the day-3 and day-7 reminders and the organizer nudge without anyone clicking « Allow check / money order ». A registration on an event with check / money order off and no per-registration allow or request is still not reminded, since it has no offline way to pay. System Status shows how many registrations are currently due a reminder. [R-1, P-6, X-2]
• Registrations: « Allow check / money order » only shows when it changes something (the event doesn’t accept checks and a balance is due) and says what it does. [R-16]
• Emails: on upgrade, built-in confirmation, approval and follow-up templates you never edited switch from %%EVENT_DATE%% to %%EVENT_WHEN%% (date, time range and timezone). Edited templates are left exactly as they are and listed in a one-time notice with a « Restore built-in » link for each. The follow-up built-in uses %%EVENT_WHEN%% too. [R-2, P-22]
• Registration form: check-enabled events show « Make checks payable to » and the mailing address before and after submitting. The post-submit box reads « Request to pay by check / money order » and only shows when the event accepts checks; events without checks show your payment instructions or a note that the organizer will be in touch. [R-3, R-15]
• Payments: one list of payment methods for every Record payment form, in wp-admin and the front-end console, and the console can record a Check. System Status and Settings list the same methods. [R-4, P-27]
• Emails: the « pay another way » organizer email names the registrant, event, date, amount due and registration number, with a link to open it in wp-admin. The registrant’s copy says how to pay. [R-5]
• Accessibility: the event and package template choosers are dialogs (Escape, focus trap, focus returned); list rows open from the keyboard; the Sign-in and My Account page selects, the color hex fields and the Record payment Method select have labels; the email mismatch error is announced once. [R-6, R-7, R-8, R-14, P-23, P-24]
• Feedback: saving an event or package, recording a payment and sending an email show a confirmation, and the System Status test email says whether the mail server accepted it. [R-9]
• Dates: admin lists, filters and the console use your site’s date format instead of 2027-03-20. [R-10, P-22]
• Status wording is the same everywhere (« Payment due », « Partially paid », « Other payment requested »). [R-11]
• Receipt: the header shows the organization name once. Settings → Organization has an « Organization address » for receipts (falls back to the check mailing address). [R-12]
• Receipt email: one receipt link instead of two near-identical ones. Templates with %%REG_LINK_HTML%% use it in place of the button. [R-13]
• Readme: tracked links from mail services still work. [R-17]
• Code: database queries reviewed for Plugin Check; every query uses fixed table names and passes values through $wpdb->prepare().
• No database schema changes. The template upgrade runs once and records itself in the orgfuse_email_date_tag_migrated option.

2.5.0

New-organizer fixes from the Mesa Grove demo review (issue IDs in brackets).

• Notifications: a « New registration » email goes to the organizer, with the registrant, package, amount due and a link that opens the registration in wp-admin. Set the recipients under Settings → Organizer notifications (the site admin email by default) and override them per event. The orgfuse_event_staff_recipients filter still adds its recipients, and every internal notice (payment requests, « I’ve paid » reports, unpaid nudges, membership and purchase notices) now goes to the same list. [P-1, P-17]
• Registrations: Record payment (method, amount, reference) right in the wp-admin registration window, even before the registration has an order. Confirmation, pay link and follow-up emails work from wp-admin in the free plugin, as they already did in the front-end console. [P-2, P-14, P-36]
• Emails: the confirmation and approval emails state the amount due and your payment instructions. The pay-link email names the event and the balance and its button reads « Review and pay your registration ». The receipt email lists the amount, method, reference and date. New merge tags: %%PAYMENT_DUE%%, %%PAYMENT_DETAILS%%, %%AMOUNT_DUE%%, %%BALANCE_DUE%%, %%AMOUNT_PAID%%, %%PAYMENT_INSTRUCTIONS%%, %%EVENT_WHEN%%, %%PAY_LINK_HTML%%. Existing templates get the payment sections added automatically. [P-3, P-9, P-10]
• Dates: the form header, emails and receipt use your site’s date and time format with the end time and timezone (« March 20, 2027 · 10:00 am – 2:00 pm MDT »). %%EVENT_DATE%% and %%EVENT_TIME%% follow the same format. [P-22]
• Registration form: the email, confirm email and name fields have labels, names and autocomplete, and errors are announced to screen readers. [P-4, P-25]
• Registration form: without online card payment the button reads « Register ($25.00 due) » and a « How payment works » box shows your payment instructions before submitting. [P-19, P-20]
• Registration form: after submitting, a « You’re registered! » message with the registration number and a link to view or print it. « Request to pay by check / money order » only appears when the event accepts checks. [P-7, P-8]
• Shortcodes: the event editor and the Events list show the event’s ready-to-copy [orgfuse_regres_create event="ID"]. Help lists it and the [orgfuse_dept_console] staff console. [P-5, P-15]
• Receipt: fits phone screens, says « Paid (recorded manually) » / « Recorded as paid » for check, cash and other hand-recorded payments, and shows the location instead of repeating the event name. The event report says how much of « Paid » was recorded manually. [P-13, P-16, P-29]
• Settings → Payment reminders: turn the automatic reminders off, change their days (3 and 7 by default) and the organizer nudge. System Status shows the schedule. [P-6]
• System Status: « Recent emails » lists what OrgFuse sent as « Accepted by mail server » with a pointer to SPF / DKIM troubleshooting, and the test email goes to any address you type. The offline-method list matches Settings. [P-11, P-18, P-27]
• Event report CSV: adds registration ID, phone, package, payment method, payment reference, registered and paid dates, balance and a readable status. [P-12]
• Events list: the Location column shows the venue. [P-21]
• Accessibility: wp-admin dialogs have dialog roles, close with Escape and return focus; Settings fields are labeled. [P-23, P-24]
• Payment methods show as « Cash », « Check » and so on instead of lowercase codes. [P-28]
• Help: fixed garbled characters and « & ». [P-30, P-31]
• Packages: « Collect processing fees » only shows when card payments are available. [P-33]
• Readme: installation from Plugins → Add New Plugin; the per-IP rate limit is optional (off by default). [P-26, P-35]
• Cleanup: removed a no-op branch in the registration email handler and the scholarship placeholder text. [P-32, P-34]
• No database schema changes. The new settings and the per-event recipient override live in the existing settings option and event settings.

2.4.9

• Forms: the package choice cards (ad packages, sponsorship levels) keep their own colors and fonts whatever the theme does to buttons, so names and prices no longer turn white on white or black on hover.
• Forms: the cards work from the keyboard like radio buttons (arrow keys to move, Space to choose) and show a clear focus outline.
• Forms: a sold-out choice shows a « Sold out » badge on a gray card instead of fading out, so its text stays readable.
• Themes can restyle the cards with --of-card-* CSS variables on .orgfuse-form.

2.4.8

• Plugins screen: a Check for updates link on the OrgFuse row checks for new versions right away instead of waiting for WordPress’ twice-daily check.
• Plugins screen and Diagnostics: OrgFuse shows whether it is the latest version or which version is available.
• Updates: the database upgrade that follows an update runs exactly once, even when several pages load at the same moment right after the update.
• OrgFuse and OrgFuse Pro now have their own version numbers, so a fix to one no longer means a release of both. OrgFuse Pro 2.4.8 and later wait for the OrgFuse version they need before offering their update, so Update all and auto-updates keep the two in the right order.

2.4.7

• Forms: a date field can default to today’s date.
• Forms: when a form offers « send me an invoice », the note under it shows who checks are payable to, where to mail them and your payment instructions (Settings). With checks turned off it offers just the invoice, and without card payments the invoice is the only option.
• Form builder: a package choice with nothing to offer yet says to add ad packages or sponsorship levels first.

2.4.6

• Released alongside OrgFuse Pro 2.4.6 (sponsorship agreements). No changes in the free plugin.

2.4.5

• Forms: when a visitor chooses to pay by check, the payment total no longer includes the card processing fee.
• Invoices: Mark paid asks how the invoice was paid (check, cash, bank transfer, card or other) and for the check number, and adds it to the invoice notes.
• Anti-spam: file uploads made while filling in a form no longer trip the « too fast » check or count toward the submission rate limit. The honeypot and page token still apply.

2.4.4

• Forms: File upload fields work on standalone forms. Files are sent when the visitor submits, and the entry and notification emails include each file’s web address.
• Forms: a payment that charges the total of the choices can offer « Add the card processing fee » when OrgFuse Pro passes that fee on.

2.4.3

• New: [orgfuse_event_search] puts an event search bar on any page. It opens the calendar with the search, location, type, department and dates already filled in.
• Calendar: the toolbar can filter by type, department and dates as well as search and location. You can hide any filter with a shortcode option, for example search="0".
• Form builder: new « Ad package » and « Sponsorship level » fields for OrgFuse Pro’s Advertising and Sponsors add-ons. They show the choices as cards with prices, and mark the ones that are sold out.
• Payment field: it can charge the total of the choices made, and it can offer « Pay by check: send me an invoice ».

2.4.2

• Fix: when a form can’t be submitted, the message now names the fields to fix and scrolls to the first one, instead of only saying « Please fix the highlighted fields. »
• Fix: fields with nothing to fill in (hidden values, headings, payment and the challenge box) no longer block a form in the browser with an error the visitor can’t see.
• Fix: the password and confirm-password boxes are compared exactly as typed, and phones no longer autocorrect or capitalize them.

2.4.1

• Translation-ready: every admin screen, the registration form and emails can be translated (text domain orgfuse), including sentences with bold text and links.
• Currency: choose the site currency in Settings. Amounts, receipts, invoices and emails use it and follow the site language’s number format.
• Phone and address fields use the US phone mask and state list only on US and Canadian sites; elsewhere they take any format.
• Registration: a signed-in person can choose who they register for when an add-on offers more than one choice (for example, one of several teams).
• My Account: a Profile tab to update details, change the password, and change the email address after confirming it.
• Emails: form notifications are sent in the branded email layout.
• Fix: the bottom Save button in the event editor now also saves the registration form.
• Fix: sign-in forms no longer make browsers offer to create a new password.
• Fix: the Season Pass invoice amount on a registration showed 100 times too small.

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 …