NetterTech Events
| 开发者 | shawnmcburnie |
|---|---|
| 更新时间 | 2026年5月22日 02:44 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
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
安装:
- Upload the
nettertech-eventsfolder to/wp-content/plugins/ - Activate the plugin through the 'Plugins' menu
- Go to Events > Settings to configure options
- Create your first event under Events > Add New
- Install and activate WooCommerce 8.5+
- NetterTech Events will automatically create products for ticket types
- Configure ticket types in the Event Editor
屏幕截图:
常见问题:
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.
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.
更新日志:
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_ksesallowlist helper (ShortcodeOutput::get_allowlist()) preserves SVG, ARIA, and data-* attributes thatwp_kses_postwould 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):
SecurityHeadersre-anchored tocurrent_screen+WP_ScreenAPI (was reading$_GETonadmin_initpriority 1). - Compliance (Wave B): Calendar shortcode URL parameters migrated from
?month=/?date=to registered query varsnettertech_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 viamap_deep( ..., 'sanitize_textarea_field' ); type-specific tightening continues inSettingsSanitizer. - Compliance (Wave B):
TicketCartAjaxsanitizes 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 fixedHooks::*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):
AdminMenuexposes explicitSUBMENU_NEW,SUBMENU_EDIT,SUBMENU_ATTENDEES,SUBMENU_QR_GENERATOR,SUBMENU_CSV_IMPORT,SUBMENU_ACTIVITY_LOG,SUBMENU_SETTINGSconstants. Eight callsites refactored. - Compliance (Wave C):
MigrationManager(legacyve_*→ canonical) state-option keys renamed fromnte_rebrand_migration_*tonettertech_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 canonicalnettertech_events_legacy_rebrand_completeaction fires on completion; the legacy bridge hook was removed for the initial WP.org submission. - Compliance (Wave C):
PrefixMigrationManagerloads its old/new prefix maps fromconfig/legacy-prefix-map.jsoninstead of carryingnte_*literals in PHP source. The remainingnte_*mentions in production source are confined to theMigrationManagerlegacy-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 theve_*→ canonical rename, and docblock examples documenting them. Nonte_*literal is emitted at steady-state runtime. - Compliance (Wave C): Template loader now passes a typed
TemplateContext(orEmailContextfor email templates) as a single$contextparameter instead of injecting locals viaextract(). Thirty-two templates refactored to property-style access ($context->event). TheNonPrefixedVariableFoundsuppressions acrosstemplates/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 thisreadme.txtis the authoritative attribution surface (a standaloneCREDITS.mdwas previously used and has been inlined here). License selected for the dual-licensedchillerlan/php-qrcodedependency: MIT (GPL-2.0 compatible). - Compliance (Wave D):
.eslintignoreremoved from the distribution (Plugin Check's "hidden files are not permitted" rule).
- Compliance: Renamed all
nte_*prefix identifiers tonettertech_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_eventtonettertech_event(16 chars; the originally-planned 23-char name exceeded WP core's 20-charregister_post_type()limit and would have silently failed registration) - Compliance: Renamed taxonomies to
nettertech_event_categoryandnettertech_event_tagfor safer headroom under WP's 32-char taxonomy slug limit - Compliance: Renamed style handle
nte-public-tickettonettertech-events-public-ticket - Compliance: Sanitization fixes — added
wp_unslash()andsanitize_text_field()to 13 superglobal access points flagged byWordPress.Security.ValidatedSanitizedInputsniff (Rentals: 11 sites; Seating: 2 sites) - Migration: New
PrefixMigrationManagerclass (Step 2 migration, separate from the existing legacyve_* → 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_itemmetakeys, transients (cache vs stateful classification), cron hook reschedule with cadence preserved, and shortcode rewrites inwp_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_loadedpriority 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 remainingnte_*strings in the codebase are insideMigrationManager.php(Step-1ve_*→nte_*migrator, never executes on a fresh install) andPrefixMigrationManager.php(Step-2 input keys for the rename map). Both are documented carve-outs. - Fix:
uninstall.phpwas deleting transients matching_transient_nte_%(the pre-1.0.1 prefix) which would have leftnettertech_events_*transients orphaned on uninstall after the migration ran. Pattern updated to match the post-migration prefix. - Fix:
uninstall.phpwas 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 canonicalShadowPostType::POST_TYPEconstant so it stays in sync with the registered slug.
- 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
- 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)
- 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
- 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
- Feature: WooCommerce ticketing integration
- Feature: RSVP form shortcode
- Feature: Theme-overridable template system
- Enhancement: Event categories taxonomy
- Feature: Recurring event frontend pages
- Feature: Occurrence-specific pages with tickets
- Feature: Event carousel shortcode
- Feature: Event list shortcode with AJAX filters
- Feature: REST API endpoints
- Feature: Calendar shortcode with multiple views
- Enhancement: Frontend router for clean URLs
- Feature: Admin event editor with metaboxes
- Feature: Events list table with bulk actions
- Feature: Recurrence rule builder UI
- Feature: RFC 5545 RRULE parser
- Feature: Occurrence generation service
- Feature: Pre-computed occurrence storage
- Initial pre-release
- Custom database tables for events, occurrences, tickets, attendees
- Basic event CRUD operations