NetterTech Events

npm install && npm run build

Changelog

1.4.3

• Fixed: on a single event with extra dates added by hand, the “Upcoming Dates” cards linked back to the page they were on, so visitors could never reach a specific date’s page or its ticket form. Date cards, calendar entries, and related links now go to the chosen date whenever an event has more than one date.
• Fixed: embedded event/RSVP markup once again strips inline style attributes. WordPress 7.0 began allowing certain inline styles through its sanitizer, which silently widened the plugin’s embed output rules; the plugin now enforces its own stricter rule regardless of WordPress version.

1.4.2

• Fixed: on WordPress 7.0+, clicking “Export All” on the Attendees / Purchases screen was blocked by a new core bulk-actions validator with “Please select a bulk action to perform.” The button now submits under its own name, which the core validator correctly ignores.

1.4.1

• Fixed: “Export All” on an event’s Purchases view now exports that event’s purchase records — previously it exported every attendee in the database while the button promised the event’s count.
• Improved: the attendees list states its counts in both units (“Showing 5 purchase records (32 tickets)”), and the Export All button says how many records it will export, so the list, summary, and export figures can be compared at a glance.
• Improved: ticking the select-all checkbox now explains that selection covers only the current page’s rows and points to Export All for everything matching the filters (announced to screen readers too).
• Fixed: the Tickets & Attendance summary no longer squeezes the Issued figure against the Checked-in column (“12 issued0”).

1.4.0

• Fixed: recurring events created with the “Weekly” pattern no longer drift to a different day of the week (or duplicate their dates) when the calendar automatically extends further into the future.
• Security: hardened the way the plugin identifies a visitor’s IP for rate limiting so a forged proxy header can no longer spoof it; tightened rate limiting on the admin attendee and ticket-type endpoints.
• Improved: the calendar tooltip’s availability text (“Sold out”, “Low stock”, “Tickets available”) is now translatable instead of hardcoded English.
• Improved: attendee CSV exports now come out in the order shown on the Attendees list — including the first/last-name alphabetization mode — instead of always newest-first.
• Improved: setting event times is faster and friendlier — time fields now suggest quarter-hour options as you type (end times show the resulting duration), while still accepting any exact time like 7:05 pm.
• Improved: ticket sale windows are entered as a clear date + time pair with one-click “Now” and “At event start” presets, replacing the fiddly combined picker. Existing saved windows are unaffected.
• Improved: date and time validation messages now appear next to the field and are announced to screen readers, instead of a blocking browser alert.
• Improved: time fields show which timezone your entries are interpreted in.

1.3.2

• Fixed: an extra date added with just a date and start time now saves — the end time is filled in from your default event duration instead of the date being silently discarded. Anything skipped or auto-filled is reported in a notice after saving.
• Fixed: re-saving a single event no longer overwrites an earlier hand-picked date.
• Fixed: saving an event from a screen without the ticket section no longer deletes a date’s ticket types.
• Fixed: tickets for an unrecognized event now default to draft (not purchasable) instead of active.
• Fixed: editing a single date validates its times (minimum length, end after start) the same way the main editor does.
• Improved: “apply to all dates” leaves individually customized dates alone and lists them in the save notice.
• Improved: editing a date no longer resets its rescheduled status.
• Improved: converting a recurring event to a single event now warns which hand-picked dates would be removed.
• Improved: unpublishing an event no longer creates shop products; it only unpublishes existing ones.
• Improved: series passes and ticket templates can be managed on single-date events.
• Improved: choosing a shared-capacity type on an event-level ticket now shows an error instead of silently changing to fixed capacity.

1.3.1

• Fixed: re-saving a recurring event no longer silently loses a date when one of its dates has been individually customized — most visibly the first day of a short daily run.
• Fixed: event cards and calendar entries now link to the specific date you clicked instead of the event’s series page.
• Fixed: a date-specific featured image now appears everywhere the image is shown, including event grids and the calendar hover preview.

1.3.0

• Fixed: editing an event from a screen that didn’t show its ticket template (or series pass) section no longer silently deletes those ticket types — a save only touches the ticket sections it actually displayed.
• Added: the Seating add-on can now resolve which date a ticket product belongs to, so seat selection works reliably on multi-venue sites (requires NetterTech Events Seating 1.0.2).

1.2.0

• Added: build a whole event before saving once — add several extra dates and set up ticket types on a brand-new event; everything is created together on first save.
• Added: draft events stay fully dark — their tickets and shop products are not purchasable until the event is published, and revert to non-purchasable if the event goes back to draft. Existing orders are never affected.
• Added: the recurrence pattern editor now collapses to a one-line summary once a pattern is set, with a toggle to expand.
• Fixed: editing a single date of a recurring event no longer brings the original date back as a duplicate on the next save.
• Fixed: dates that carry their own ticket types now survive schedule regeneration (their tickets and products previously lost their connection on re-save).
• Fixed: a per-date featured image now shows on event cards and grids, not just the event page.

1.1.4

• Added: a series pass now has a clear buy button on the public event page — its own “Series Pass” section (“valid for every date of this event”), shown once whether the event lists as single or recurring, instead of being scattered across each date’s ticket form.
• Fixed: the per-date ticket form no longer repeats an event’s series pass; each date’s form lists only that date’s own ticket types.
• Changed: refreshed the Events admin-menu icon.

1.1.3

• Changed: test and tooling configuration now reads environment variables with portable defaults instead of machine-specific fallback paths; integration-test setup is documented in tests/Integration/README.md.
• Changed: internal working-hours tooling removed from the repository.

1.1.2.2

• Added: series passes now work end to end — a pass gets its own product, a single purchase admits the buyer to every date of the event (one attendee per date, ready for check-in each day), and a pass occupies a seat on every date it spans: its availability is bounded by the tightest date’s room.
• Added: the ticket editor’s Series Passes and This Occurrence tabs are available on any event with more than one date, not only pattern-recurring events, and the events list says “Single (N dates)” when a single event carries extra hand-picked dates.
• Added: the attendees screen consolidates Tickets & Attendance into one panel — per-ticket-type issued, check-ins, and (with Pro) net revenue with refunds already subtracted — beside Event Details; the table gains a sortable Ticket type column and an attendee-id/ticket-code identity line; attendees can be edited in place and added manually (manual adds respect capacity); bulk actions gain Re-send Confirmation Email.
• Fixed: editing a ticket no longer silently re-creates its WooCommerce product — the product, its SKU, and its sales history now survive every save, and a SKU typed into the event editor is honored instead of being replaced by a generated default.
• Fixed: one sold series pass no longer counts once per date in the Ticket Overview, and pass sales now appear in revenue reporting — including orders whose product an earlier save had orphaned.
• Fixed: the Coupon column loaded every order in the store to decorate one page of attendees; it now loads only the page’s own orders.
• Developer: new filters — nettertech_events_ticket_type_revenue (per-type net revenue for the consolidated panel) and nettertech_events_sale_schedule_ui_available (suppress base’s sale-window guidance when a real price-schedule control renders).
• Developer: the hook reference now covers every hook the plugin fires, backed by an automated completeness check; hook name constants are complete and version tags corrected.
• Developer: new hooks fire when a ticket type is created or updated, when an attendee is checked in, when settings change, and when attendees are exported, so integrations and the activity log can react to each.

1.1.2.1

• Fixed: a ticket’s sale window, description, and per-order limits entered on a date’s own ticket form were silently discarded on save. All tiers of a chained price schedule therefore showed and sold at once, ignoring their start and end dates. The form’s values are now saved exactly as entered.

1.1.2

• Fixed: a ticket left in the cart could still be bought after its sale window closed or its allotment ran out. The cart is now re-checked at the checkout, not only when the ticket was added, and the shopper’s own held seats are no longer counted against them.
• Fixed: an event was treated as past from the moment it started, so an event still running was listed as over. Past and upcoming are now judged by when an event ends.
• Fixed: an event’s date was judged against the site’s clock rather than its own, so an event in another timezone could turn “past” hours early or late. Each date now records the actual moment it starts and ends, and is judged by that.
• Fixed: turning a recurring event back into a single one silently overwrote its first date and stranded the rest — still scheduled, still on sale, and no longer visible on any screen. Converting now keeps the date you choose, with its own times, and removes the others. A date that has sold tickets is never removed: the save is refused and tells you which.
• Fixed: switching an event to “recurring” and saving without choosing a pattern generated hundreds of daily dates. The editor carries a default frequency of “daily” and an end condition of “never” whether or not you ever open the pattern controls, and those defaults were being read as your answer. An unchosen pattern is now refused rather than invented, and the message points you at “Add a date” if one more date is all you wanted.
• Added: a date can be added to an event outside its recurrence pattern, so an event can run every Tuesday and also on one Saturday. Saving the pattern again does not remove it.
• Added: each date can be removed from the Dates box. A date that has sold tickets is never removed — the removal is refused and tells you which.
• Added: ticket types can now be set on any date, from that date’s own editor. Previously only an event’s first date could be given tickets, so a date added by hand had no way to sell anything. A date added by hand also inherits the event’s ticket templates, exactly as a generated date does.
• Added: the Dates box now lists every date on any saved event, not just recurring ones.

1.1.1.4

• Fixed: on the event-scoped Purchases screen, each ticket type subtracted its own sales from its own copy of the room, so an event selling three tiers into one hall reported roughly three halls’ worth of seats remaining. Tiers on a date now share one house, exactly as the Events list’s “% of capacity” column has always counted them: availability is what the house has left, a tier with its own smaller limit still stops there, and the Total reports the house once rather than once per tier. A tier with no limit of its own no longer reads “unlimited” when the date has a capacity. Seated tiers take their availability from the seating add-on.
• Fixed: a ticket type that had sold nothing was omitted from the Ticket Overview entirely; every active type is now listed, including at zero.
• Fixed: the Attendance Overview counted guests on its “Tickets” line but attendee records on its status lines, so a card could read “Tickets 32” directly above “Confirmed 5” for the same people. Every line now counts guests.
• Fixed: the Attendees filter bar inherited WordPress’s own theme-browser styling, boxing each filter in an oversized bordered panel and stacking the Filter and Clear buttons; the bar is now a single aligned row.
• Fixed: long availability labels in the Ticket Overview were clipped at the card’s edge.
• Fixed: the Attendees table ran off the side of the screen on narrow windows and tablets. It now fits the available width, and on small screens each attendee collapses to a row you can expand — the standard WordPress list-table behaviour.
• Added: attendees can be checked in directly from the Attendees screen, and the check-in action is now offered only for attendees whose status permits it.
• Added: the ticket-confirmation email can be re-sent from the Attendees screen.
• Added: an event’s Purchases screen now opens with Event Details, Ticket Overview, and Attendance Overview summary cards; add-ons render their own cards alongside them (the Pro add-on’s financial synopsis appears here).
• Security: attendee CSV exports now neutralize spreadsheet formula injection in exported fields.

1.1.1.3

• Fixed: events still in progress were listed as “past” — past/upcoming bucketing now uses the event’s end time rather than its start time, in listings and in the admin occurrence pickers.
• Fixed: splitting a recurring series (“this and following dates”) dropped the new event’s categories, tags, and organizers; they now carry over.
• Fixed: the admin Events list “Created” timestamp could display shifted by the server’s timezone offset; creation times are now stored in UTC and rendered in the site timezone.
• Added: WooCommerce ticket products now mirror their event’s categories as product categories, so category-scoped coupons (e.g. “10% off all Music events”) apply to ticket purchases without listing each product.
• Added: a Content-Security-Policy script allowlist setting, so operators can permit specific external script origins on event pages without loosening the policy globally.
• Added: the event image box now shows the configured display ratio as an upload hint, and each event can set a crop anchor for how its image is framed on event cards.
• Added: an extension point on the event-scoped Purchases screen that add-ons can use to render purchase summaries (the Pro add-on shows a financial synopsis there).
• Security: rate limiting now identifies clients by connection address by default; proxy-reported addresses are honored only on sites that declare a trusted proxy.

1.1.1.2

• Fixed: the Events list “% of capacity” figure summed every ticket tier’s capacity, so multi-tier events (e.g. Standing / Seated / Youth sharing one room) showed a denominator several times the real house and a percentage far too low. Tiers now share one house pool, so the denominator is the largest tier capacity (or the occurrence ceiling when set); multiple dates are still summed.
• Fixed: the Attendees “Export All” / “Export Selected” CSV actions failed (no output / “Please select a bulk action”) because the export dispatched after page output had begun; dispatch now runs on page load so the file streams correctly.

1.1.1

Maintenance and accessibility release, plus space assignment on events.

• Added: events can now be assigned to a Space from the event editor (Space / Venue box); the Seating add-on uses the assignment to pick the right seating map on multi-space sites.
• Fixed: header and footer lost their layout styling on event pages under block themes (e.g. Twenty Twenty-Four).
• Fixed: events configured to show only the “Current Date/Time” layout component lost their date row and RSVP button on event pages.
• Fixed: the RSVP form appeared expanded before the RSVP button was clicked; it now starts collapsed, and stays fully usable without JavaScript.
• Fixed: the organizer metabox never appeared in the event editor.
• Fixed: the Events list “Tickets Sold” column counted ticket records, so RSVPs and group registrations were undercounted; it now reflects the full confirmed guest count.
• Fixed: screen-reader labels on the RSVP form were being stripped; they now come through intact.
• Improved: YouTube/Vimeo videos in event descriptions now scale to the full content width at 16:9.
• Security: the CSP reporting endpoint is rate-limited and length-capped; settings saves check capability before nonce.

1.1.0

This release adds calendar-feed publishing, per-occurrence editing, richer ticketing and admin tooling, and finer image control, alongside recurrence fixes and broad quality work.

New features
* Calendar feed (iCal/ICS): publish a subscribe-able feed at a clean URL so attendees can add your events to Google, Apple, or Outlook calendars. Open-ended recurring events are bounded by a configurable feed horizon.
* Per-occurrence editing: change a single date in a recurring series — override its time, venue, or virtual URL, or cancel just that occurrence — with a clear scope selector. iCal export reflects overrides and cancellations via RFC 5545 RRULE / EXDATE / RECURRENCE-ID.
* Per-event image control: set the single-event-page featured-image aspect ratio independently of cards/list/carousel, plus a per-event vertical crop anchor (top/center/bottom) so the important part of off-ratio images is kept.
* Ticket SKUs: per-ticket-type SKUs are auto-generated, editable, and viewable from the event list and on public tickets.
* All Events list: new “Tickets Sold” (with percent of capacity) and Date columns, a “Ticketed” type filter, and a “Purchases” row action that opens the Attendees list filtered to that event — with per-occurrence drill-down and WooCommerce order links.
* Year-scoped past-events archive: browse past events by year.
* Archive filters: multi-select category/tag filtering, timeframe limiting, and settings to control which filters appear.
* Beaver Themer integration for event field data.
* Configurable defaults for new-event start time and duration, and an optional intro paragraph above the events archive.

Improvements
* The Past Events archive now shows event imagery at full vibrance; the muted “past” treatment is reserved for mixed/upcoming views where it still distinguishes past entries.
* Accessible multi-select filter widget and accessible (3:1+) disabled-button styling.
* Safer event deletion: removing an event cleans up its child data and ticket products, events with sold tickets are protected, and order history is preserved.
* Static analysis raised to PHPStan level 8 across the codebase, with a large expansion of automated test coverage.

Fixes
* Single-event featured images render at the configured aspect ratio instead of being clipped to a fixed-height band.
* Recurrence: yearly rules honor BYMONTH; BYSETPOS no longer overrides a positioned BYDAY; cancelled and edited occurrences survive schedule regeneration without duplicating.
* All Events list: filter and search restored; bulk actions no longer truncate on long selections.
* iCal exports recover original occurrence slots correctly (EXDATE / RECURRENCE-ID).
* Timezone correctness: event “past” / “Completed” status now honors the site timezone (DST-aware). On UTC-hosted servers, events no longer flip to past/completed hours before they actually end in local time, and the calendar feed (iCal DTSTART/DTEND) exports the correct moment.

Under the hood
* Database schema updates apply automatically on upgrade (additive, no data loss): per-occurrence overrides, occurrence sequence numbers, the per-event image crop anchor, and occurrence authoring timezones.

1.0.2

• Compliance: Round-2 WP.org Plugin Review remediation. Suppression-as-documentation removed across the source tree; per-issue root-cause refactors landed in waves.
• Compliance (Wave A): Output escaping refactored across blocks, BeaverBuilder modules, frontend shortcodes, admin/repo/service classes, and templates. Custom wp_kses allowlist helper (ShortcodeOutput::get_allowlist()) preserves SVG, ARIA, and data-* attributes that wp_kses_post would strip.
• Compliance (Wave B): Service classes (RecurrenceRuleBuilder, TicketTypeSaver, CheckInEmailSaver, AttendeeFieldsSaveHandler) no longer fall back on $_POST — callers must pass verified data after nonce/capability checks. Bulk-action handlers extract input only after nonce verification.
• Compliance (Wave B): SecurityHeaders re-anchored to current_screen + WP_Screen API (was reading $_GET on admin_init priority 1).
• Compliance (Wave B): Calendar shortcode URL parameters migrated from ?month= / ?date= to registered query vars nettertech_events_calendar_month / ..._date; legacy URLs 301-redirect to the prefixed format.
• Compliance (Wave B): Settings page sanitizes $_POST['nettertech_events_settings'] at the boundary via map_deep( ..., 'sanitize_textarea_field' ); type-specific tightening continues in SettingsSanitizer.
• Compliance (Wave B): TicketCartAjax sanitizes the JSON ticket payload at the boundary; the prior suppression is removed.
• Compliance (Wave B): EventTemplateResolver::can_preview_event() refactored to close a bypass gap where a malformed ?preview= value could skip nonce verification.
• Compliance (Wave C): Dynamic-hook patterns (e.g. Hooks::SETTINGS_TAB_PREFIX . $tab, {filter_prefix}_get_template_part_{slug}) replaced with fixed Hooks::* constants; listeners receive what was previously encoded in the suffix as an action argument. Backward-compat bridges fire the deprecated names alongside the canonical ones (will be removed in 2.0).
• Compliance (Wave C): AdminMenu exposes explicit SUBMENU_NEW, SUBMENU_EDIT, SUBMENU_ATTENDEES, SUBMENU_QR_GENERATOR, SUBMENU_CSV_IMPORT, SUBMENU_ACTIVITY_LOG, SUBMENU_SETTINGS constants. Eight callsites refactored.
• Compliance (Wave C): MigrationManager (legacy ve_* → canonical) state-option keys renamed from nte_rebrand_migration_* to nettertech_events_legacy_rebrand_*. A v1.0.2 upgrade-path transition forwards legacy keys onto the new names for sites that ran the migration under v1.0.0/1.0.1. Only the canonical nettertech_events_legacy_rebrand_complete action fires on completion; the legacy bridge hook was removed for the initial WP.org submission.
• Compliance (Wave C): PrefixMigrationManager loads its old/new prefix maps from config/legacy-prefix-map.json instead of carrying nte_* literals in PHP source. The remaining nte_* mentions in production source are confined to the MigrationManager legacy-rename code path: state-transition source-key strings (nte_rebrand_migration_complete, nte_rebrand_migration_log) read on upgrade from v1.0.0/1.0.1, the intermediate post-type and taxonomy slugs targeted by the ve_* → canonical rename, and docblock examples documenting them. No nte_* literal is emitted at steady-state runtime.
• Compliance (Wave C): Template loader now passes a typed TemplateContext (or EmailContext for email templates) as a single $context parameter instead of injecting locals via extract(). Thirty-two templates refactored to property-style access ($context->event). The NonPrefixedVariableFound suppressions across templates/ are gone (was 38).
• Compliance (Wave D): Vendor documentation (per-library LICENSE, NOTICE, CHANGELOG.md, README.md, tests, examples) excluded from the distribution zip. The “Bundled Third-Party Libraries” section of this readme.txt is the authoritative attribution surface (a standalone CREDITS.md was previously used and has been inlined here). License selected for the dual-licensed chillerlan/php-qrcode dependency: MIT (GPL-2.0 compatible).
• Compliance (Wave D): .eslintignore removed from the distribution (Plugin Check’s “hidden files are not permitted” rule).

1.0.1

• Compliance: Renamed all nte_* prefix identifiers to nettertech_events_* to satisfy WP.org plugin review’s 4-character minimum prefix requirement (hooks, options, post/user/order-item meta keys, transients, AJAX action strings, nonces, $POST keys, JS-localized variables, table prefixes, cron hook names)
• Compliance: Renamed custom post type slug from nte_event to nettertech_event (16 chars; the originally-planned 23-char name exceeded WP core’s 20-char register_post_type() limit and would have silently failed registration)
• Compliance: Renamed taxonomies to nettertech_event_category and nettertech_event_tag for safer headroom under WP’s 32-char taxonomy slug limit
• Compliance: Renamed style handle nte-public-ticket to nettertech-events-public-ticket
• Compliance: Sanitization fixes — added wp_unslash() and sanitize_text_field() to 13 superglobal access points flagged by WordPress.Security.ValidatedSanitizedInput sniff (Rentals: 11 sites; Seating: 2 sites)
• Migration: New PrefixMigrationManager class (Step 2 migration, separate from the existing legacy ve_* → nte_* MigrationManager) automatically renames all DB-persisted artifacts on plugin upgrade — custom tables (RENAME TABLE), wp_posts.post_type, wp_term_taxonomy.taxonomy, options (exact-match per key, no broad REPLACE), wp_postmeta/wp_usermeta/wp_woocommerce_order_itemmeta keys, transients (cache vs stateful classification), cron hook reschedule with cadence preserved, and shortcode rewrites in wp_posts.post_content
• Migration: Conflict-detection rule — if both old and new tables exist, migration logs the conflict and aborts rather than auto-merging (per data-safety policy); transient lock prevents parallel runs
• Migration: Per-addon migrators (Pro, Rentals, Seating) listen on the base completion action AND run a plugins_loaded priority 20 fallback check, so addons activated after base migrate independently. Each addon has its own completion flag and log option.
• Note for site owners: existing sites running the in-review v1.0.0 should run update_option( 'nettertech_events_prefix_migration_complete', '' ) before upgrade only if they want the migration to re-run; otherwise the migration runs automatically on plugin update.
• BREAKING — Yoast SEO templates: The three custom title-template variables registered via wpseo_register_var_replacement() were renamed from %%nte_event_date%%, %%nte_event_venue%%, %%nte_event_organizer%% to %%nettertech_events_event_date%%, %%nettertech_events_event_venue%%, %%nettertech_events_event_organizer%%. Sites with the legacy variable names in their Yoast title templates will need to update those templates after the upgrade — the old names no longer resolve and will render as the literal string. Rank Math equivalents were already migrated and are unaffected.
• Cleanup: Swept all stale nte_* references out of comments, PHPDocs, local PHP variable names, test fixtures, block render templates, Beaver Builder module render templates, and the uninstall handler. The only remaining nte_* strings in the codebase are inside MigrationManager.php (Step-1 ve_* → nte_* migrator, never executes on a fresh install) and PrefixMigrationManager.php (Step-2 input keys for the rename map). Both are documented carve-outs.
• Fix: uninstall.php was deleting transients matching _transient_nte_% (the pre-1.0.1 prefix) which would have left nettertech_events_* transients orphaned on uninstall after the migration ran. Pattern updated to match the post-migration prefix.
• Fix: uninstall.php was filtering shadow posts by the post-type slug 'nettertech_events_event' (23 chars; exceeded WP’s 20-char limit and was never the live slug). Replaced with the canonical ShadowPostType::POST_TYPE constant so it stays in sync with the registered slug.

1.0.0

• Feature: Category system migrated from WordPress taxonomy to internal tables with dedicated editor
• Feature: Event reminder emails with configurable timing and cron scheduling
• Feature: GDPR privacy tools — WordPress privacy exporter/eraser for attendee data
• Feature: Event card redesign with full-tile clickability and responsive images
• Feature: Category checkbox UI in event editor sidebar
• Feature: WooCommerce event_id meta on cart items for integration support
• Feature: Distribution packaging with .distignore and GPL v2 LICENSE
• Enhancement: God class decomposition — 8 large classes refactored into focused modules
• Enhancement: PHPStan Level 7 static analysis with zero-error baseline
• Enhancement: CSS custom properties for themeable colors (date badge, ticket area, borders)
• Enhancement: 12px minimum font floor enforced; systemic rem-to-em CSS conversion
• Enhancement: Test suite of over 5,000 unit tests with over 17,000 assertions
• Fix: Event time not saving correctly (BUG-001)
• Fix: Past events AJAX pagination missing parameter (BUG-002)
• Fix: Category filter dropdown empty after iCal import (BUG-003)
• Fix: Ticket quantity buttons non-functional due to script timing (BUG-004)
• Fix: Event editor browser tab title stuck on “All Events” (BUG-005)
• Fix: Category UI missing from event editor (BUG-007)
• Fix: ActivityLogHooks signature updated to accept Attendee model
• Fix: Admin bar “Edit Event” hover color
• Security: Compatible with WooCommerce High-Performance Order Storage
• Security: OWASP 2025 compliance verified across all endpoints

0.9.0

• Feature: Multi-organizer support with junction tables
• Feature: Categories and tags junction tables for scalability
• Enhancement: Test coverage improved to 29.30% (1,077 unit tests)
• Enhancement: E2E test suite expanded to 53 Playwright tests
• Enhancement: Schema version bump with automatic migration
• Security: Check-in codes generated via random_bytes (16-hex-char codes, cryptographically secure per OWASP 2025)

0.8.0

• Feature: ServiceRegistry DI pattern with 7 contracts
• Feature: Denormalized counter caching for ticket sales
• Feature: N+1 query prevention with identity maps
• Security: OWASP 2025 compliance (authorization order fixes)
• Enhancement: 887 unit tests + 51 E2E Playwright tests
• Enhancement: Beaver Builder modules with direct class invocation
• Enhancement: Gutenberg blocks for Calendar, Carousel, and Grid

0.7.0

• Feature: QR code generation with color customization
• Feature: Atomic check-in operations (race-condition safe)
• Feature: Email confirmations with ICS attachments
• Feature: Series passes for recurring events
• Feature: Template tickets with automatic propagation
• Enhancement: Centralized capacity service

0.6.0

• Feature: WooCommerce ticketing integration
• Feature: RSVP form shortcode
• Feature: Theme-overridable template system
• Enhancement: Event categories taxonomy

0.5.0

• Feature: Recurring event frontend pages
• Feature: Occurrence-specific pages with tickets
• Feature: Event carousel shortcode
• Feature: Event list shortcode with AJAX filters

0.4.0

• Feature: REST API endpoints
• Feature: Calendar shortcode with multiple views
• Enhancement: Frontend router for clean URLs

0.3.0

• Feature: Admin event editor with metaboxes
• Feature: Events list table with bulk actions
• Feature: Recurrence rule builder UI

0.2.0

• Feature: RFC 5545 RRULE parser
• Feature: Occurrence generation service
• Feature: Pre-computed occurrence storage

0.1.0

• Initial pre-release
• Custom database tables for events, occurrences, tickets, attendees
• Basic event CRUD operations