Warp Calendar Events

Warp Calendar Events helps you publish and organize events in WordPress. Manage events, venues, organizers, categories and tags from an interactive dashboard, then display published events on your website.

• Month, List, Day, Week, Week list, Week timeline and Upcoming views.
• Classic, Minimal and Compact templates with light, dark and device-based appearance options.
• Daily, weekly, monthly-date and yearly recurrence, interval/count/end-date limits and individual occurrence changes.
• Twelve Gutenberg blocks, an event-layout pattern, shortcodes and an upcoming-events widget.
• Dedicated Calendar, Upcoming Events and Event Details integrations for Elementor and Bricks, when installed separately.
• Public iframe and script embeds for another website.
• Manual CSV and public HTTPS ICS preview/import, preserving previously imported records and local edits.
• ICS downloads, rolling subscriptions, Google Calendar compose links and event structured data.
• Optional mapping of existing public post types and date fields into the calendar.
• Registration: free RSVP or paid tickets per event, per-occurrence capacity, group bookings, guest self-service links, confirmation emails and private attendee lists with CSV export.
• PayPal tickets using your own PayPal business account — no WooCommerce, no platform fee. Verified captures, webhooks, full and partial refunds and reconciliation.
• Migration from The Events Calendar 6.x and Pie Calendar 1.x with inventory, dry run, batched import, rerun safety, optional URL redirects and rollback.

JavaScript and CSS source files are included locally; no build step or external CDN is required. Elementor and Bricks are optional and are not bundled. Core features, RSVP, PayPal tickets and migrations work without builders or the separate Warp Calendar Events Pro add-on. Events stay display-only until you enable registration.

External services and privacy

This plugin does not send telemetry or contact an activation, licensing or external update server. WordPress.org handles updates to the directory version. Optional external interactions are:

• ICS import: when an administrator enters a public HTTPS feed URL and requests a preview, the site server contacts that provider, following safe HTTP redirects. The provider receives the request and server IP. No feed request runs automatically. Use feeds you are authorized to import and review that provider’s policies.
• Google Calendar: clicking its event link opens calendar.google.com with the event title, dates, description, public occurrence URL and venue location encoded in the link. Data is sent when opened; this is not background sync. Google Calendar, Privacy, Terms.
• Google Maps: when an editor enables venue directions, clicking the public link sends the venue address to Google Maps. Maps are not loaded in the background. Google Maps, Privacy, Terms.
• PayPal (paid tickets only): when an organizer enables paid tickets and a visitor reserves a place, the visitor can continue to PayPal’s hosted checkout (www.paypal.com or www.sandbox.paypal.com); the site server calls PayPal’s REST API (api-m.paypal.com or api-m.sandbox.paypal.com) to create, capture, verify and refund payments, and to verify webhook signatures. PayPal receives the booking reference, amount, currency and event description, plus whatever the buyer enters at PayPal. Nothing loads on pages without paid ticket forms. PayPal, Privacy, Terms.
• External embeds: a site owner may place a public calendar iframe/script on another website. Visitors then request calendar assets and data from this WordPress site, exposing normal HTTP request information to its server. No embed host is preconfigured. The optional auto-height script sends only the public frame height to the parent page.

Organizer/venue names, addresses, phone numbers, websites and emails are stored in WordPress post metadata. Email display is opt-in; published contact details can appear on event pages. Import previews use per-user transients for 20 minutes, query caches for two minutes, and a bounded administrator-visible import log records source labels and activity. Site administrators control backups, retention and deletion. When registration is enabled, purchaser names and emails, attendee names, optional attendee emails and answers, booking dates and payment states are stored privately in dedicated database tables. They never appear in public pages, feeds or calendar data, are available to administrators with the booking capability, and are included in WordPress’s personal-data export and erasure tools (payment amounts and PayPal transaction IDs are kept for accounting). Guest booking links carry their secret in the URL fragment, which browsers do not send to servers or other sites. Booking data remains after deactivation or deletion.