Gather Grove Booking

Changelog

1.95.9

• Security: the instructor profile’s intro-video embed is now filtered through wp_kses at output (an iframe allow-list on top of the plugin’s widget allow-list).
• Changed: the JSON-LD class schema is encoded at the echo; numeric package attributes are cast at the echo.

1.95.8

• Changed: the public schedule and class-grid renderers close their output buffer on the same straight-line path as every other buffer in the plugin; the exception path discards it explicitly.

1.95.7

• Security: a client or instructor account can now be removed from Gather Grove screens only when every role on that account belongs to Gather Grove. Accounts that also hold a WordPress role (editor, author, subscriber, …) are left in place; the WordPress Users screen remains the only place to delete those.
• Security: the client-profile editor no longer renames WordPress accounts that Gather Grove does not manage; it updates the Gather Grove client record only.
• Changed: every database query is now a single fixed statement with every value bound through $wpdb->prepare(); list filters use bound flags rather than assembled WHERE fragments.
• Maintenance: updated the bundled Stripe PHP library from 20.3.1 to 21.3.0.
• Added: an uninstall.php that honours the “Delete all data when this plugin is uninstalled” setting (off by default).
• Tested up to WordPress 7.1.

1.95.6

• Changed: every database query names its tables with WordPress’s identifier placeholder (%i) through $wpdb->prepare(); no table name is concatenated into SQL any more.
• Changed: request handlers that read form fields verify their nonce in the same function as the reads, even where a caller already did.

1.95.5

• Security: the pre-booking intake metabox fields verify their own nonce and edit capability before reading anything from the request.
• Changed: the Reports page’s CSV export, date-range and tab scripts moved into the admin script bundle — no script is buffered inline any more.
• Changed: every output buffer opens and closes on one straight-line path; the exception path discards the buffer explicitly.
• Changed: the pending-automation cancel query and the prefix-rename scan are single fixed statements with every value on a placeholder.
• Removed: three files nothing loaded (an empty Classes admin-page stub, an empty cancellation-policy stub, and unreleased reports location-switcher scaffolding).

1.95.4

• Changed: the last un-prefixed hook name now carries the gather_grove prefix; a docblock that read as an external service was reworded.

1.95.3

• Security: email attachment temp files can only ever carry a safelisted document extension (.ics, .csv, .pdf, images) — code-like extensions never reach disk.
• Fixed: the Reports data endpoints now check the reports-viewing capability, matching the Reports admin page, instead of the broader booking-management capability.

1.95.1

• Security: a session belonging to an unpublished class now returns exactly the same “not found” response as a session that doesn’t exist, so browsing session ids reveals nothing about unpublished classes — not even that one is there.

1.95.0

• Security: a hardening pass across the plugin’s public surfaces. Draft (unpublished) classes, waivers, and page settings can no longer be read through public booking endpoints by guessing ids; the guest waiver-signing credential is now a fully opaque, expiring, server-verified token that reveals nothing about any account; the waiver-signing endpoint is rate-limited and never records duplicate signatures; and every database query fragment was audited so no prepared statement is ever assembled from another. No settings or data change; nothing to do after updating.

1.94.1

• Fixed: only the first appointment on a site could ever be booked — every later appointment failed with “Could not reserve the session for this slot.” The slot’s internal session record was created without its unique identifier, so the second one ever collided with the first and was silently discarded. Latent for several versions; surfaced on the first 1.94.0 install.

1.94.0

1.93.1

1.93.0

• Added: a Waivers screen that answers “who still owes me a signature?” Until now you could see one client’s waiver history at a time, but there was no way to see the whole roster at once — which is exactly what you need the moment you update a waiver. Find it under Gather Grove → Waivers. It shows, for each active waiver, who has signed the current version, who signed an older one, whose signature has expired, and who has never signed at all — with the reason for each, and a CSV export.
• Added: waiver reminder emails you send by hand. Tick the people you want to chase, review a list of exactly who will be emailed, then send. There is no automatic schedule and never will be — a waiver reminder that fires on its own turns a formality into nagging.
• If someone has an account with you, their reminder link asks them to log in before signing, so a signature is always attached to the right person. People without an account (a child on a family account, for instance) can sign straight from the link.
• The screen tells you plainly how many people have no email address on file — they can’t be reached by any reminder, so you’ll want to collect those in person. You can record a paper signature against anyone directly from the list.
• Fixed: a class-specific waiver in the sample/demo content was never actually being applied.

1.92.0

• Fixed: a package sold for a course or training could be spent on classes instead — and never ran out. If you sell something that grants access to a course rather than a number of class sessions, it was being treated as an ordinary class pack. Two defaults then combined badly: a pack with no specific classes listed counts as valid for every class, and a pack with no session count counts as unlimited. The result was that your most expensive product quietly doubled as a free, never-expiring pass to every class on your schedule, and there was no setting that would stop it.
• The “Access pass” tickbox on a package now does what it says on any package, not only on memberships — tick it on a course or training package and it can never be offered as payment for a booking, never spent on one, and never auto-books its holder into sessions. Nothing changes for your ordinary class packs and memberships: without that tickbox, they behave exactly as before.
• If you sell a course or training package, open it and tick Access pass — that is the one thing worth checking after this update.

Earlier releases are listed at https://gathergrove.io/docs/booking/changelog