EventPlus Lite

EventPlus Lite is a modern WordPress event management plugin for organizers who need a fast, professional way to publish events, accept registrations, and manage attendees — without wrestling with outdated admin screens.

Built with a React-powered dashboard, Gutenberg blocks, and REST API architecture, EventPlus feels like a dedicated event platform inside WordPress. Start free with Lite, then scale into EventPlus Pro and optional add-ons when you need tickets, payments, custom forms, maps, and more.

Why choose EventPlus?

• Modern admin experience — Manage events, registrations, and settings in a clean React dashboard designed for speed and clarity
• Built for WordPress — Native Gutenberg blocks, classic shortcodes, and theme-friendly frontend output that works with any well-coded theme
• Publish events in minutes — Guided setup checklist, auto-created calendar and events pages, and step-by-step event creation
• Flexible display options — Month events calendar, categories, featured images, and styling controls
• Registration & attendees — Collect sign-ups with a built-in registration form and manage attendees from one place
• Modular by design — Activate only the features you need; extend with Pro and add-ons as your events program grows
• Developer-friendly — Custom post types, REST endpoints, and a structured codebase that integrates cleanly with the WordPress ecosystem

Perfect for

• Conferences, meetups, and workshops
• Community events and nonprofit calendars
• Classes, webinars, and training sessions
• Churches, venues, and membership organizations
• Any site that needs a reliable WordPress events calendar with event registration

Free in EventPlus Lite

• Unlimited event creation and editing
• Event categories and featured images
• Month calendar view — [eventplus_calendar]
• Basic registration form — [eventplus_registration_form event_id="123"]
• Attendee and registration management
• Gutenberg blocks for calendar and registration form
• Setup checklist and automatic events/calendar pages
• General settings for timezone, date format, and organization details

Grow with EventPlus Pro & add-ons

EventPlus is designed to start simple and scale up. When you outgrow Lite, upgrade to EventPlus Pro to unlock advanced tools and a catalog of optional add-ons, including:

• Registration Forms — Custom fields and flexible registration flows (included with Pro)
• Tickets & Discounts — Ticket types, promo codes, and QR passes
• Payments — Stripe and PayPal checkout for paid events
• Maps Integration — Display events on an interactive map
• Events Carousel & Timeline — Rich visual layouts for event showcases
• Event Coordinators — Highlight speakers and organizers
• Email Templates — Branded transactional emails
• Event Check-In — QR scanning and attendance tracking
• AI Assistant — Optional content help when configured by the organizer

Pro customers install the premium build from their Freemius account after purchase. Lite remains on WordPress.org for free core updates. Compare plans and add-ons on the pricing page.

Technology

• React single-page admin for events, registrations, and settings
• WordPress REST API for structured data and admin operations
• Gutenberg block editor support for no-code page building
• Shortcodes for classic editors, page builders, and legacy content
• Custom post types & taxonomies for events and registrations
• Modular add-on registry so features can be enabled independently

Shortcodes

• [eventplus_calendar] — Month grid calendar with event links
• [eventplus_registration_form event_id="123"] — Basic registration form for a specific event
• [eventplus_single_event] — Single event details

List, grid, and other display shortcodes ship with EventPlus Pro, not with this WordPress.org zip.

Blocks

Gutenberg blocks are included for calendar and registration form. List, grid, map, carousel, timeline, and coordinators blocks ship with EventPlus Pro or the relevant add-on. See the full block and shortcode reference in the shortcodes docs.

Get started

Install EventPlus Lite, open the EventPlus menu in wp-admin, and follow the setup checklist. Add the calendar or list block to any page — or paste a shortcode — and your WordPress events calendar is live.

Start with the getting started guide, browse the docs hub, and compare Pro plans and add-ons when you are ready to grow.

External services

EventPlus connects to several third-party services. Each entry below describes the service, what data is sent, when it is sent, every host the plugin contacts for that service, and links to the service’s terms of use and privacy policy.

1. Freemius (licensing, upgrades & checkout) — Lite + Pro

Freemius powers the optional opt-in, license activation, account management, billing, and Pro upgrade flow that ship inside the plugin (via the bundled Freemius WordPress SDK in vendor/freemius/).

• What data is sent: Site URL, admin email address, WordPress and PHP version, plugin slug and version, license key and activation status, and (when the administrator opens the Account or Pricing screens) basic checkout context. No data is sent if the administrator chooses “Skip” on the opt-in prompt.
• When it is sent: Only when the administrator interacts with the Freemius opt-in prompt, activates / deactivates / syncs a Pro license, opens the EventPlus -> Account / Pricing / License & billing screens, or when the SDK performs its periodic background license check after the user has opted in.
• Hosts contacted (by the Freemius SDK):
  • api.freemius.com — REST API for opt-in, license, account, and update checks.
  • wp.freemius.com — production WordPress endpoints used by the SDK.
  • checkout.freemius.com — embedded checkout iframe loaded on the Pricing screen.
  • users.freemius.com — administrator dashboard links opened on user click.
  • dashboard.freemius.com — marketing/banner assets shown inside the SDK’s Add-ons screen.
  • www.mcafeesecure.com — “Secure HTTPS” verification badge displayed by the SDK on the checkout/pricing header.
• Freemius Terms of Service: https://freemius.com/terms/
• Freemius Privacy Policy: https://freemius.com/privacy/

2. Google Calendar (Add to Calendar link) — Lite

The single-event frontend includes an optional “Add to Google Calendar” link for site visitors.

• What data is sent: Event title, start/end date-time, location, and description, encoded in a URL query string and passed to calendar.google.com only when the link is clicked.
• When it is sent: Only when a visitor explicitly clicks the “Add to Google Calendar” link. Nothing is sent automatically on page load.
• Host contacted: calendar.google.com (on click).
• Google Terms of Service: https://policies.google.com/terms
• Google Privacy Policy: https://policies.google.com/privacy

The following services are used only in EventPlus Pro and its optional paid add-ons. They are never active in EventPlus Lite.

3. Stripe (Pro — Payments add-on)

Used to process paid ticket and event purchases through Stripe Checkout.

• What data is sent: Payment card details are entered directly into Stripe’s JavaScript library (loaded from js.stripe.com) and tokenised in the visitor’s browser — no raw card numbers reach the site server. The plugin server sends order amount, currency, item description, event/registration identifiers, and the organizer’s Stripe secret key to the Stripe API in order to create a Checkout Session. After session creation the visitor is redirected to Stripe’s hosted checkout page to complete payment.
• When it is sent: Only when a visitor submits a paid registration form on an event page, and only after the organizer has configured the Payments add-on with a Stripe account and API keys.
• Hosts contacted:
  • js.stripe.com — Stripe.js client library loaded in the visitor’s browser on payment pages.
  • api.stripe.com — server-side REST API for creating Checkout Sessions and verifying payments.
  • checkout.stripe.com — Stripe’s hosted checkout page that the visitor is redirected to.
• Stripe Terms of Service: https://stripe.com/legal/ssa
• Stripe Privacy Policy: https://stripe.com/privacy

4. PayPal (Pro — Payments add-on)

Used as an alternative payment gateway to process paid ticket and event purchases through the PayPal Orders API.

• What data is sent: Order amount, currency, item description, event/registration identifiers, return / cancel URLs, and the organizer’s PayPal client ID and secret are sent to the PayPal Orders API to create and capture a payment. The visitor is then redirected to PayPal’s approval page to authorize the payment.
• When it is sent: Only when a visitor initiates a PayPal checkout on a paid event page, and only after the organizer has configured the Payments add-on with PayPal API credentials.
• Hosts contacted:
  • api-m.paypal.com — production REST API (server-side).
  • api-m.sandbox.paypal.com — sandbox REST API (only when the organizer enables PayPal test/sandbox mode).
  • www.paypal.com — visitor redirect to PayPal’s hosted approval page (production).
  • www.sandbox.paypal.com — visitor redirect in sandbox/test mode.
• PayPal User Agreement: https://www.paypal.com/us/legalhub/useragreement-full
• PayPal Privacy Statement: https://www.paypal.com/us/legalhub/privacy-full

5. OpenStreetMap & Leaflet (Pro — Maps add-on, default provider)

The Maps add-on uses OpenStreetMap as its default mapping and geocoding provider, and renders interactive maps with the open-source Leaflet library, which is bundled inside the plugin (no CDN is used). The organizer can opt in to Google Maps instead (see entry #6 below).

• What data is sent:
  • Nominatim geocoding: the event’s venue address is sent server-side to nominatim.openstreetmap.org so the Maps add-on can look up its latitude and longitude.
  • Tile rendering: the visitor’s browser loads vector/raster map tiles directly from *.tile.openstreetmap.org when viewing a page that displays the map. The OpenStreetMap Foundation may receive standard browser data (IP address, user-agent, referrer) at that point.
• When it is sent: Address geocoding occurs when the organizer creates or updates an event that includes a venue address. Tile requests happen in the visitor’s browser when they open a page that contains a map embed.
• Hosts contacted:
  • nominatim.openstreetmap.org — server-side geocoding.
  • a.tile.openstreetmap.org, b.tile.openstreetmap.org, c.tile.openstreetmap.org — tile servers loaded by the visitor’s browser.
  • www.openstreetmap.org — copyright link and optional admin preview embed.
• OpenStreetMap Copyright & Licence: https://www.openstreetmap.org/copyright
• OpenStreetMap Privacy Policy: https://wiki.osmfoundation.org/wiki/Privacy_Policy
• Nominatim Usage Policy: https://operations.osmfoundation.org/policies/nominatim/
• Leaflet (BSD-2 licence, bundled with the plugin): https://leafletjs.com/

6. Google Maps (Pro — Maps add-on, optional alternative provider)

When the organizer opts in to Google Maps (instead of the default OpenStreetMap provider) and supplies their own Google Maps API key, the Maps add-on geocodes addresses and renders maps with Google’s services.

• What data is sent:
  • Event venue addresses are sent server-side to the Google Maps Geocoding API to obtain coordinates.
  • The visitor’s browser loads the Google Maps JavaScript API and Static Maps API; Google may collect standard browser data (IP address, browser information) at that point.
  • The administrator’s API key is sent with the “Test API key” admin validation request when they click the test button on the map settings screen.
• When it is sent: Address lookup occurs when the organizer saves an event with a venue address. Map rendering and static-map previews occur in the visitor’s / administrator’s browser when they view a page or admin screen containing the map embed. Requires the Google Maps provider to be selected and an API key to be configured.
• Hosts contacted:
  • maps.googleapis.com — Geocoding API (server), Maps JavaScript API and Static Maps API (browser), and API key validation (admin browser).
  • console.cloud.google.com — opened only when the administrator clicks a documentation link in the admin map settings.
• Google Maps Terms of Service: https://cloud.google.com/maps-platform/terms
• Google Privacy Policy: https://policies.google.com/privacy

7. OpenAI (Pro — AI Assistant add-on)

The optional AI Assistant add-on generates suggested event descriptions and other content in the admin using the OpenAI Chat Completions API.

• What data is sent: The text prompt entered by the administrator (for example a draft event title, summary, or notes) plus the organizer’s OpenAI API key are sent to the OpenAI Chat Completions API. No site visitor data is ever sent.
• When it is sent: Only when the administrator explicitly clicks the “Generate” button inside the event editor. Requires the AI add-on to be active and the organizer to supply their own OpenAI API key in the plugin settings.
• Hosts contacted:
  • api.openai.com — Chat Completions API endpoint (server-side from the admin request).
  • platform.openai.com — opened only when the administrator clicks the “Get your API key” documentation link in the AI settings screen.
• OpenAI Terms of Use: https://openai.com/policies/terms-of-use/
• OpenAI Privacy Policy: https://openai.com/policies/privacy-policy/

8. goQR.me / QR Server (Pro — Tickets add-on)

The Tickets add-on uses the goQR.me public API (api.qrserver.com) to render QR-code images that are embedded in attendee confirmation emails and ticket pass pages.

• What data is sent: Only a registration-specific opaque token (a one-way hash — not the attendee’s name, email, or any other personal data) is sent to api.qrserver.com as the QR code’s data string. The image is requested directly by the email client or visitor’s browser when the confirmation email or success page is opened.
• When it is sent: Only when a confirmation email or success page containing a QR ticket pass is rendered after a successful registration, and only when the Tickets add-on is active.
• Host contacted: api.qrserver.com (operated by goQR.me / Foundata GmbH).
• goQR.me Privacy & Usage Policy (covers privacy practices and acceptable use of the public API; goQR.me does not publish a separate Terms of Service page — usage is described in this combined policy and on the goQR.me homepage FAQ): https://goqr.me/privacy-safety-security/

9. CodeCanyon / Envato (admin marketing links) — Lite + Pro

The EventPlus admin displays a small number of “Upgrade” and “Add-on” links that point to product pages on CodeCanyon. These are plain <a href="..."> links — they do not transmit any data unless the administrator clicks them.

• What data is sent: Nothing automatically. Standard browser request data (IP address, user-agent, referrer) is sent to CodeCanyon only if the administrator clicks one of the links.
• When it is sent: On user click only.
• Host contacted: codecanyon.net.
• Envato Market User Terms (apply to CodeCanyon purchases and browsing): https://themeforest.net/lp/market-user-terms-updated/
• Envato Privacy Policy: https://www.envato.com/privacy/

Development

EventPlus Lite is developed and maintained by EventPlus
(WordPress.org account: digdan).
Documentation: wpeventsplus.com/docs. Support: wpeventsplus.com/support.

EventPlus Lite is built with React, TypeScript, Vite, Tailwind CSS, and the WordPress REST API.

Readable assets

• Public CSS/JS ships unminified: public/css/eventplus-public.css and public/js/eventplus-public.js
• Admin UI is a production Vite bundle: build/assets/index.js and build/assets/index.css
• Gutenberg blocks are a production bundle: build/blocks/index.js

Source code

The complete uncompiled human-readable source for every compiled file in this
plugin — the React/TypeScript sources (src/), the Vite and Node build
configuration, and package.json — is published under GPLv2 (or later) at:

https://github.com/elbisnero/eventplus-lite

Those sources are not bundled in this WordPress.org zip to keep the download
small; the repository above is public, free to access, and requires no account.

Build from source

Clone the repository above (not this zip), then:

1. Install Node.js 18+ and npm 9+
2. Run npm install --legacy-peer-deps
3. Run npm run build:wordpress:full to compile the admin UI into build/assets/index.js and build/assets/index.css
4. Run node scripts/wp-blocks-build.mjs --lite to compile the Lite Gutenberg blocks into build/blocks/index.js

Those three files are the only compiled files in this plugin, and the commands
above reproduce them byte for byte. Everything else in this zip — all PHP, plus
public/css/eventplus-public.css and public/js/eventplus-public.js — already
ships as human-readable source.