=== NetterTech Events ===
Contributors: shawnmcburnie
Tags: events, calendar, tickets, recurring events, rsvp
Requires at least: 6.5
Tested up to: 7.0
Stable tag: 1.1.1
Requires PHP: 8.2
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

A WordPress event management plugin with dedicated database tables, recurring events, RSVP forms, and WooCommerce ticketing for venues and nonprofits.

== Description ==

NetterTech Events stores your events in dedicated database tables rather than WordPress post meta. That architectural choice means calendar queries stay fast whether you have 50 events or 5,000, and it means recurring event schedules are pre-computed rather than recalculated on every page load.

**Recurring events that handle real schedules:** Full RFC 5545 recurrence rule support covers patterns like "every second Tuesday" and "last Friday of the month." Change a rule, and occurrences regenerate automatically.

**Ticketing without per-ticket fees:** Sell tickets through WooCommerce with automatic capacity tracking per occurrence. Series passes let attendees buy once for an entire recurring event run. No external ticketing service means no percentage taken on each sale.

**Free event registration:** RSVP forms work without WooCommerce for events that don't require payment. Attendees register, receive confirmations, and can be tracked through the same admin interface.

**Check-in built in:** Manual attendee check-in by name or email search works from any device. QR code and volunteer check-in workflows can be added with the separate NetterTech Events Pro plugin.

**Spaces and locations management:** Define bookable spaces and physical locations through a dedicated admin interface. Assign spaces to events via the event editor metabox to track which room or area each event occupies.

**Display options for any layout:** Month, week, and day calendar views. Carousel slider for featured events. Filterable grid with live search. Weekly regulars table for recurring events. All three calendar views are available as Gutenberg blocks and Beaver Builder modules.

**Reminder emails that send themselves:** Configure pre-event reminders at any interval you choose. Emails go out automatically via WordPress cron - no third-party service required.

**SEO handled at the source:** Schema.org Event structured data integrates with Yoast SEO and Rank Math's JSON-LD output rather than generating a second duplicate block. Custom sitemap entries cover recurring occurrence URLs individually. Custom SEO title variables (`%%nettertech_events_event_date%%`, `%%nettertech_events_event_venue%%`, `%%nettertech_events_event_organizer%%`) let you build dynamic titles per-occurrence. Breadcrumb trail follows the full event hierarchy. Works without either SEO plugin using built-in Schema.org and Open Graph output.

**Accessibility throughout:** Designed to WCAG 2.2 AA standards with ARIA labels, full keyboard navigation, focus management, and reduced motion support across every public-facing view.

**Your data stays yours:** All attendee, ticket, and event data is stored in your WordPress database. No data is sent to external services. GDPR tools let site administrators export or erase attendee records on request.

**For Developers:**

* Repository and Service patterns with documented hooks and filters throughout
* Theme-overridable templates in `nettertech-events/templates/` - copy to your theme to customize
* REST API for headless or custom implementations
* Over 5,000 automated tests with over 17,000 assertions covering core functionality

== Shortcodes ==

**[nettertech_events_calendar]** - Monthly, weekly, and daily calendar views with navigation.

**[nettertech_events_list]** - Filterable event grid or list with live search and category filters. (Also available as `[nettertech_events_grid]` for grid-only layout.)

**[nettertech_events_carousel]** - Sliding carousel of upcoming events with configurable columns.

**[nettertech_events_rsvp]** - RSVP registration form for free events. Supports party size and custom confirmation messages.

**[nettertech_events_regulars]** - Display weekly recurring events in a compact table grouped by day of week. Replaces manually maintained static HTML with live data from published recurring events. Parameters:

* `limit` - Maximum events to display (default: 50)
* `show_venue` - Show venue name column, true/false (default: true)
* `show_time` - Show event time column, true/false (default: true)
* `show_day` - Show day-of-week grouping, true/false (default: true)
* `heading` - Optional table heading text (default: empty)
* `class` - Additional CSS class for the wrapper (default: empty)

Example: `[nettertech_events_regulars show_venue="false" heading="Weekly Classes"]`

== Installation ==

1. Upload the `nettertech-events` folder to `/wp-content/plugins/`
2. Activate the plugin through the 'Plugins' menu
3. Go to Events > Settings to configure options
4. Create your first event under Events > Add New

**For Ticketing:**

1. Install and activate WooCommerce 8.5+
2. NetterTech Events will automatically create products for ticket types
3. Configure ticket types in the Event Editor

== Frequently Asked Questions ==

= Does this plugin require WooCommerce? =

No. WooCommerce is optional and only needed for paid ticketing. The plugin works without it for event display, calendars, and free RSVP registration.

= What's included in the free version? =

The free version includes unlimited events, recurring event support, RSVP forms, manual attendee check-in by name or email search, all three display views (calendar, grid, carousel), SEO integration, and full GDPR tools. QR code check-in, volunteer check-in mode, and QR code generation for promotion are available in NetterTech Events Pro.

= Can I import events from The Events Calendar? =

Yes. The companion plugin **NetterTech Events Migrator** supports bidirectional migration with The Events Calendar. Import and export cover all 13 entity types including recurring events, venues, organizers, categories, tickets, and attendees with lossless round-trip fidelity.

= How do recurring events work? =

NetterTech Events pre-computes occurrences using RFC 5545 recurrence rules (the same standard used by Google Calendar and iCal). Rules support patterns like "every second Tuesday" and "last Friday of the month." When you change a rule, occurrences regenerate automatically.

= Can attendees buy a ticket to an entire recurring event series? =

Yes. Series passes grant access to all occurrences of a recurring event with a single purchase. They're configured as a ticket type in the event editor.

= Will this slow down my site as the event count grows? =

Event data is stored in dedicated database tables with indexes built for calendar queries. Calendar views query by date range against pre-computed occurrences rather than scanning post meta. The query load does not scale with total event count the way post-meta-based plugins do.

= Can visitors subscribe to a calendar feed? =

Yes. Published events are available as an iCalendar (.ics) feed that calendar apps (Google Calendar, Apple Calendar, Outlook) can subscribe to. For high-traffic sites you can optionally enable **Static iCal Feed** under **Events - Settings - Email & Advanced**: the feed is then served from a prebuilt file at `/{your-events-base}.ics` (for example `/events.ics`), rebuilt automatically when events change. This serves polling calendar clients with almost no PHP or database work and is edge-cacheable. The option is off by default; while off, the feed is generated on demand, and that dynamic feed also remains as an automatic fallback if the static file is ever unavailable. A large site (thousands of occurrences) produces a feed file of a few megabytes.

= Can I link to all past events from a particular year? =

Yes. Append a four-digit year to the past-events archive URL — for example `/events/archive/2024/` — to show every past event from that year on one shareable page, with the archive's normal pagination. The page title reflects the year. The unscoped past-events archive (without a year) continues to list all past events.

= How do I customize the event display templates? =

Copy templates from `nettertech-events/templates/` to `your-theme/nettertech-events/` and modify as needed. Templates exist for single event pages, occurrence lists, event cards, the calendar view, grid view, and carousel. Your customizations are preserved across plugin updates.

= Is the plugin accessible? =

Yes. NetterTech Events is designed for WCAG 2.2 AA compliance with ARIA labels, keyboard navigation, focus management, and reduced motion support across all public-facing views.

= How are event categories managed? =

Categories are managed through a built-in editor at **Events - Categories** in the admin menu. They use dedicated database tables rather than WordPress taxonomies, support parent/child hierarchy, and are available as frontend filters in event lists and calendars.

= What PHP version is required? =

PHP 8.2 or higher. The plugin uses strict types, enums, and constructor property promotion throughout.

= Will this plugin conflict with other event plugins? =

NetterTech Events uses its own custom tables and a dedicated URL namespace (`/events/` by default). If you have The Events Calendar or another plugin registered to the same URL prefix, there will be a conflict. The plugin detects this on activation and displays a notice with instructions for resolving it.

== Screenshots ==

1. Monthly calendar with month, week, and day views
2. Upcoming events archive with search, category filters, and responsive card layout
3. Single event page with featured image, date, price, and site navigation
4. Weekly regulars table and calendar with event detail popup on hover
5. Admin event editor with recurring event patterns and capacity settings
6. Admin events list with status filters, event types, and bulk actions
7. Display settings with drag-and-drop layout builder for single event pages
8. Advanced settings showing rate limits, lookahead controls, and the opt-in attribution badge (disabled by default)
9. Mobile-responsive archive page with event cards
10. Mobile single event page with ticket type selector and add-to-cart

== Changelog ==

= 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

== Upgrade Notice ==

= 1.0.0 =
Major release: category system migrated to internal tables, event reminders, GDPR privacy tools, 7 bug fixes, 8 UX improvements. Database migration runs automatically. Requires WordPress 6.5+.

= 0.9.0 =
Schema improvements for multi-organizer support. Database migration runs automatically on activation.

= 0.8.0 =
Security update with OWASP 2025 compliance fixes. Recommended for all users.

= 0.7.0 =
Adds QR check-in and email confirmations. Database migration runs automatically.

== Third Party Services ==

This plugin does not connect to any external third-party services by default.

= WooCommerce Integration (Optional) =

When WooCommerce is installed and activated, this plugin integrates with it to provide paid ticketing functionality. WooCommerce is a separate plugin that handles payment processing through payment gateways you configure.

* WooCommerce is developed by Automattic
* [WooCommerce Terms of Service](https://woocommerce.com/terms-conditions/)
* [WooCommerce Privacy Policy](https://automattic.com/privacy/)

No data is sent to WooCommerce servers by this plugin. All ticket and order data remains in your WordPress database.

= QR Code Generation =

QR codes are generated entirely on your server using the bundled PHP QR Code library. No external API calls are made.

= Bundled Third-Party Libraries =

NetterTech Events is licensed under GPL-2.0-or-later. The plugin bundles the following GPL-compatible third-party libraries via Composer. The authoritative dependency list and resolved versions live in `composer.json` and `composer.lock` (both shipped with the plugin so reviewers can verify vendor contents).

* `chillerlan/php-qrcode` 6.0.1 — MIT (selected from the upstream dual MIT / Apache-2.0 license). Used for QR code rendering on tickets and check-in flows. Source: https://github.com/chillerlan/php-qrcode
* `chillerlan/php-settings-container` 3.3.0 — MIT. Transitive dependency of `php-qrcode`. Source: https://github.com/chillerlan/php-settings-container
* `symfony/polyfill-mbstring` 1.33.0 — MIT. UTF-8 string-function polyfill (transitive). Source: https://github.com/symfony/polyfill-mbstring

The MIT license is selected for the dual-licensed `chillerlan/php-qrcode` because Apache-2.0's patent-retaliation clause is GPL-3.0+ compatible but not GPL-2.0 compatible. MIT keeps the bundled code consistent with the plugin's GPL-2.0+ choice.

== Privacy Policy ==

NetterTech Events collects and stores the following data in your WordPress database:

= Data Collected =

* **Attendee Records**: Name, email address, and ticket details when users purchase tickets or submit RSVPs
* **Check-in Data**: Timestamps when attendees are checked in at events
* **Event Data**: Event details, occurrences, and ticket configurations created by administrators

= Data Storage =

* All data is stored locally in your WordPress database in custom tables prefixed with `nettertech_events_` (e.g. `{$wpdb->prefix}nettertech_events_events`)
* No data is transmitted to external servers by this plugin
* Data retention is controlled by you; delete events and ticket records to remove associated data

= Data Export and Erasure =

* Attendee data integrates with WordPress's built-in privacy tools
* Site administrators can export or erase attendee data on request
* Event organizers should document ticket/RSVP data collection in their site privacy policy

= Cookies =

This plugin does not set any cookies.

== Source Code & Build ==

The plugin ships pre-built block assets under `blocks/*/build/` (compiled from
`@wordpress/scripts`) so it runs without requiring users to install Node.js or
run a build step. The human-readable source for every compiled file is
included in the same distribution under `blocks/*/src/`:

* `blocks/calendar/src/index.jsx` — source for `blocks/calendar/build/index.js`
* `blocks/carousel/src/index.jsx` — source for `blocks/carousel/build/index.js`
* `blocks/event-grid/src/index.jsx` — source for `blocks/event-grid/build/index.js`

To rebuild from source after editing any `*.jsx` file:

`npm install && npm run build`

The build configuration lives in `package.json` (`scripts.build`) and uses the
official `@wordpress/scripts` toolchain with no custom webpack config.

== Additional Resources ==

* [Plugin Homepage](https://nettertech.com/plugins/events/)
* [Support Forum](https://wordpress.org/support/plugin/nettertech-events/)
