Installation
Eventonomy overviewFree + ProGet Eventonomy →
Get Eventonomy running on your WordPress site in under five minutes. This guide covers system requirements, how to install, and what the plugin sets up automatically on first activation.

What You Will Learn
Section titled “What You Will Learn”- Whether your server meets the requirements
- How to install Eventonomy (Free and Pro)
- What Eventonomy creates automatically on activation
Requirements
Section titled “Requirements”| Requirement | Minimum |
|---|---|
| WordPress | 6.5 or higher |
| PHP | 8.1 or higher |
| MySQL | 5.7 or higher (or MariaDB 10.4+) |
| Browser | Any modern browser (Chrome, Firefox, Safari, Edge) |
Eventonomy works with any WordPress theme. It integrates visually with BuddyX and Reign: the plugin adopts the theme’s accent colour and dark-mode signal automatically.
Note: Eventonomy does not use WordPress custom post types. All event data lives in its own custom tables (
wp_evnm_*). This is intentional: it gives your events the query performance and scalability that CPT-based plugins cannot match at scale.
Installing Eventonomy Free
Section titled “Installing Eventonomy Free”Eventonomy is distributed from wbcomdesigns.com. Both the free plugin and Pro come from the same downloads page, so start by downloading the ZIP: searching the WordPress plugin directory will not find it.
Method 1: Upload from WordPress Admin (Recommended)
Section titled “Method 1: Upload from WordPress Admin (Recommended)”- Go to Plugins → Add New Plugin → Upload Plugin.
- Choose the ZIP you downloaded.
- Click Install Now, then Activate.
Method 2: WP-CLI
Section titled “Method 2: WP-CLI”Point WP-CLI at the ZIP rather than at a slug. A bare slug is resolved against the WordPress plugin directory, where Eventonomy is not published, so it fails.
wp plugin install /path/to/eventonomy.zip --activateInstalling Eventonomy Pro
Section titled “Installing Eventonomy Pro”- Purchase Eventonomy Pro from wbcomdesigns.com.
- Download the Pro ZIP from your account.
- Go to Plugins → Add New Plugin → Upload Plugin, upload the ZIP, and activate.
- Both Free and Pro must be active; Pro extends Free and cannot run standalone.
After activation, a Manage License link appears on the Plugins page. Click it and enter your license key to enable automatic updates from the Wbcom store.
Eventonomy → License & add-ons shows one status card: Pro is active either way, and the line under it says whether the license is active (automatic updates on) or not activated, expired or invalid (updates off until you fix it).
What Happens on Activation
Section titled “What Happens on Activation”Eventonomy sets everything up automatically the first time you activate it.
Pages created:
Eventonomy creates three WordPress pages:
- Events (
/events/) - hosts the calendar, events list, and view switcher blocks. - Manage Events (
/manage-events/) - the member dashboard where organizers manage their events and RSVPs. - Submit Event (
/submit-event/) - kept for compatibility only. Event creation now lives inside the dashboard, so this page redirects there and is not linked from the front-end navigation. Safe to leave alone; old links and bookmarks keep working.
Why
/manage-events/and not/dashboard/? “Dashboard” is an extremely common page slug that collides with membership and LMS plugins, so new installs use a distinct/manage-events/slug to avoid a permalink clash. Upgrading from an earlier version? Your existing dashboard page and its slug are left untouched; the activator only creates the page on sites that don’t already have one mapped.
Single-event URLs (e.g. yoursite.com/event/my-event/) are handled by a virtual template, so no separate page is created for each event.
Database tables created:
Eventonomy creates its own tables with the evnm_ prefix:
| Table | Purpose |
|---|---|
evnm_events |
Core event records |
evnm_occurrences |
Materialized occurrences (one per instance, including recurring) |
evnm_rsvps |
Attendee RSVPs |
evnm_tickets |
Ticket types per event |
evnm_orders |
Order records (free and paid) |
evnm_meta |
Extensible key/value metadata |
evnm_venues |
Shared venue catalog |
evnm_organizers |
Shared organizer catalog |
evnm_notifications |
In-app notification feed (also read by the mobile app) |
Pro adds five more:
| Table | Purpose |
|---|---|
evnm_follows |
Organizer / space / category / event follows |
evnm_earnings |
Per-order organizer earnings and platform fee ledger |
evnm_payouts |
Recorded payouts to organizers |
evnm_payout_debts |
Refund-after-payout netting |
evnm_pro_feeds |
Calendar Sync subscriptions |
All of these are removed on uninstall only if you opt in to data deletion - see Privacy & GDPR.
WordPress capabilities registered:
Eventonomy does not create new WordPress roles. It defines its own capabilities and maps each one onto a capability your existing roles already have, so whoever can already do the equivalent thing in WordPress can do it in Eventonomy. This is the authoritative map as of version 1.3.0.
| Eventonomy capability | Maps to WordPress capability | Which default roles have it |
|---|---|---|
evnm_create_events |
read |
Every logged-in user (Subscriber and up) |
evnm_edit_events |
read |
Every logged-in user (Subscriber and up) |
evnm_edit_others_events |
edit_others_posts |
Editor, Administrator |
evnm_delete_events |
delete_posts |
Contributor, Author, Editor, Administrator |
evnm_manage_rsvps |
edit_others_posts |
Editors and Administrators |
evnm_manage_orders |
manage_options |
Administrator only |
evnm_manage_settings |
manage_options |
Administrator only |
Who can manage an event’s attendees and orders
Section titled “Who can manage an event’s attendees and orders”The table above answers only half the question, and it is the half that surprises people. Eventonomy always checks who owns the event first.
- The person who created the event manages it. For their own event, the organizer can edit it, see the attendee list, change RSVP statuses, email registrants, and see the orders - even if they are a plain Subscriber with no WordPress editing permission at all. Ownership is the permission.
- Acting on an event you did not create is a different matter. That is where the capabilities above apply. Managing the attendees of somebody else’s event (the list, the export, check-in) needs
edit_others_posts, the same right that lets you edit it, so Editors and Administrators have it by default. Managing its orders (refunds, marking paid) needsmanage_options, which by default only an Administrator has.
So on a default WordPress site: an Administrator can manage every event; an Editor can edit other people’s events and see, export and check in their attendees, but cannot refund or confirm payment; an Author or Subscriber can create events and fully manage the ones they created.
Changed in 1.9.2. Attendee access follows the right to edit other people’s events. Between 1.3.0 and 1.9.1 it needed
manage_options. A site that wants the stricter rule back can setevnm_manage_rsvpstomanage_optionsthrough theevnm_capabilitiesfilter.
Developers can remap any of this with the evnm_capabilities filter, and override a single decision with evnm_user_can_manage_event. See Hooks & Filters.
Permalink rules flushed:
Rewrite rules are registered and flushed immediately. No manual permalink reset is needed.
Background jobs scheduled:
Eventonomy schedules three recurring jobs:
- Reminder dispatch (hourly) - sends the built-in event reminders (1 day + 1 hour before each event starts).
- Occurrence maintenance (daily) - extends recurring events up to the horizon window as time passes.
- Import cleanup (daily) - clears out finished import jobs.
Pro adds two more: an hourly payment reconciliation pass, and an hourly calendar-sync refresh for any connected feeds.
If Action Scheduler is available on your site, Eventonomy uses it instead of WP-Cron for the hourly jobs.
Already Have Events in Another Plugin?
Section titled “Already Have Events in Another Plugin?”You don’t have to start from zero. Eventonomy imports your existing events, from The Events Calendar, EventON, Events Manager, WP Event Manager, or Sugar Calendar (read directly from your database, whether or not the old plugin is still active), or from a CSV / iCalendar file.
Go to Eventonomy → Setup & Health → Importer, scan to preview exactly what will be created, then import. Old event URLs are redirected automatically, and the whole migration can be undone. If Eventonomy detects another events plugin’s data on your site, it offers the migration in a wp-admin notice too.
Full walkthrough: How to Migrate from Another Events Plugin.
Updating
Section titled “Updating”Updates arrive on the normal WordPress Plugins and Updates screens, for Free and Pro. Each update package is signed by Wbcom, and your site checks that signature before it installs the update. A package that fails the check is recorded in the package_signatures_log option, and the update still installs, so a signing problem never leaves you stuck on an old version. Update Free and Pro together, since each release pair shares the same version number.
Uninstalling
Section titled “Uninstalling”Deactivating Eventonomy preserves all data. Only a full uninstall (delete the plugin) removes the evnm_* tables, options, and capabilities, but only if Settings → General → Site & data → Delete all Eventonomy data when the plugin is uninstalled is enabled. This setting is off by default, so your data is safe unless you explicitly opt in.
What’s Next?
Section titled “What’s Next?”Check the Setup & Health screen to confirm everything is wired correctly.

