OrgFuse

Registro de cambios

2.7.0

Items held over from the 2.6 retests. Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.6.3 below.

• Package prices: an early or late price can now be $0 on purpose. Leave the cell blank to charge the base price in that window. On update, existing packages keep charging exactly what they did.
• Packages have an image, picked from the Media Library, shown on that package’s card on the membership join form.
• Record payment: the Check / Money order reference reads “Check / MO number or note”. With “Pay online” enabled, its method asks for the payment ID (for example a Stripe pi_…), and a note explains that those payments must be recorded by staff.
• The top menu’s dropdowns close after a mouse click and when the pointer leaves, so they no longer cover the page underneath. Keyboard focus still opens them.
• [orgfuse_pricing] cards use the full width on phones and no longer shrink inside a theme’s column block.
• An unedited “Payment received” email template from 2.5.0 is updated to the current wording. Edited templates are not changed.
• Settings: a note explains that open and click tracking comes from the mail service, not OrgFuse.

2.6.3

Follow-up to the 2.6.2 retest. Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.6.2 below.

• A registration’s “Email not sent” notice now clears once a later email about that registration reaches the same recipient, for example after Send confirmation works.
• The PHP error log names the registration instead of the recipient’s email address when a send fails. The email log still shows the recipient.

2.6.2

Fixes from the 2.6.1 retest. Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.6.1 below.

• Emails: a failed send is retried once, and the reason is saved in the email log. A registration shows staff any email about it that didn’t send, in wp-admin and the staff console.
• The organizer’s “registrant reports they have paid” email now names the event in the subject and has a details table and an “Open this registration” link.
• “I’ve paid” answers right away on servers that can finish the page before sending email (PHP-FPM, LiteSpeed); the emails go out just after.
• Membership join form: the price suffix follows the package length (“/6 mo”), and [orgfuse_pricing] says “per 6 months”.
• After “I’ll pay another way — hold my registration”, the confirmation says the registration is held and to pay by any method listed, instead of check-only wording.

2.6.1

Shortcode reference, membership setup and payment-request fixes from the Mesa Grove demo survey. Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.6.0 below.

• Help → Shortcode reference lists only tags that exist, adds the missing Core tags (buttons, login menu, rows and columns, event search, Season Pass, sign-in URL, show/hide and member tags, account summary), and shows each tag’s attributes with a copyable example. Pro-only tags are listed under Pro.
• Pricing Cards guide: says plainly that the visual builder is part of OrgFuse Pro, and how to write [orgfuse_pricing] by hand in Core.
• Packages: a Description field, a Membership length choice (one year, a set length, the same date each year, or a fixed date), and role pickers instead of free text.
• Settings: a Membership page picker, and a warning while no sign-in page is set. My Account’s Membership tab shows staff where to set up the join page; members no longer see setup wording.
• My Account greets members by their display name.
• After “Request to pay…”, registrants can tell you they’ve paid (“I’ve paid”), as on the receipt page.
• After submitting a registration, the confirmation scrolls into view and takes focus.
• Buttons builder: “Link to a page or post” no longer keeps the old URL; Login / Logout menu notes that LOGIN uses Settings → Sign-in page.
• With four or more payment methods, the request button reads “I’ll pay another way — hold my registration”.
• Venue City / State / Zip fields have labels for screen readers; new consent fields default to full width.

2.6.0

Algamail becomes OrgFuse’s email, newsletter and CRM layer; the Communications add-on is retired. Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.17 below.

• OrgFuse → Communications now introduces Algamail (sold separately on algamail.com). With Algamail active it shows its status, an Open Algamail button and the email opt-in settings.
• OrgFuse Pro & Add-ons lists Algamail under “Made for OrgFuse”. Communications is no longer sold as an add-on.
• Email opt-ins on registration forms (the checkbox and the “Email opt-in” field) fire orgfuse_comm_consent, which Algamail records. The opt-in checkbox and field are offered only while a plugin receives them.
• Developers: new orgfuse_unsubscribe_url filter sends old unsubscribe links to another preferences page, and orgfuse_comm_optin_available decides whether opt-ins are offered.
• Settings: the stored SparkPost API key is no longer returned to the admin screen.

2.5.17

Two console polish items from the 2.5.16 retest. Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.16 below.

• Staff console: Trash asks first (“Move this registration to trash? It can be restored later.”), like wp-admin.
• Staff console: buttons clicked with the mouse no longer show the theme’s focus outline; keyboard users still see it.

2.5.16

Fix from the 2.5.15 retest (issue ID in brackets). Updating from 2.5.0? This release also includes everything listed under 2.5.1 to 2.5.15 below.

• Staff console: opening a registration by clicking anywhere on its row no longer draws a focus ring around the panel; keyboard users still see one. [R-81]

2.5.15

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

• Staff console: panels and headings that receive focus after an action no longer show a theme outline after a mouse click; keyboard users still see a focus ring. [R-79]
• Staff console: after recording a partial payment, the check / reference number is cleared and the amount resets to the new balance, so the same payment can’t be recorded twice by accident. [R-80]

2.5.14

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

• Accessibility: buttons in the front-end staff console (Yes, send, Record, Create registration, Create another anyway, Close, Trash, Block & remove, Approve, Deny, the follow-up email, paper-mode Save and the event’s stop/reopen button) keep keyboard focus while they work. The duplicate notice focuses “Open existing”, and paying a balance in full moves focus to Order & payments. [R-77]
• Admin: “Creating…” uses a proper ellipsis on the new-registration window. [R-78]

2.5.13

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

• Accessibility: action buttons that show a working state (Send, Record, Create, Approve and similar) keep keyboard focus while they run, and if the action replaces the button, focus moves to the nearest sensible control instead of the top of the page. [R-76]

2.5.12

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

• Accessibility: keyboard focus stays on the Save button while settings save, instead of jumping to the top of the page. [R-74]
• Settings: after a refused save, fixing one of several fields updates the Save bar message to the problems still open, and clears it once all are fixed. [R-75]

2.5.11

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

• Payments: the “Pay online” link can carry {reg_id}, {amount_due}, {email}, {first_name}, {last_name}, {event} and {event_id}, filled in for each registration on the registration form and in the how-to-pay, approval and reminder emails, so a payment page can prefill them. Other {…} placeholders are removed. The pay buttons now appear after you register, not before, with a line saying so. [R-71]
• Settings: when a save is refused, the field in question is marked, focused and shows its own message beside it, as well as in the Save bar. [R-72]
• Registration console: recording a payment no longer returns the registrant’s private live-link token. [R-73]
• No database schema changes.

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.

= …