Installation

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

• Whether your server meets the requirements
• How to install Eventonomy (Free and Pro)
• What Eventonomy creates automatically on activation

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

Method 1: WordPress Admin (Recommended)

1. Go to Plugins → Add New Plugin in your WordPress admin.
2. Search for Eventonomy.
3. Click Install Now, then Activate.

Method 2: Upload a ZIP File

1. Download the Eventonomy ZIP from wbcomdesigns.com.
2. Go to Plugins → Add New Plugin → Upload Plugin.
3. Choose the ZIP file and click Install Now, then Activate.

Method 3: WP-CLI

wp plugin install eventonomy --activate

Installing Eventonomy Pro

1. Purchase Eventonomy Pro from wbcomdesigns.com.
2. Download the Pro ZIP from your account.
3. Go to Plugins → Add New Plugin → Upload Plugin, upload the ZIP, and activate.
4. 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.

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)
evnm_webhook_events	Payment-webhook log, used to make gateway callbacks idempotent

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	manage_options	Administrator only
evnm_manage_orders	manage_options	Administrator only
evnm_manage_settings	manage_options	Administrator only

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 or orders of somebody else's event needs manage_options, which by default only an Administrator has.

So on a default WordPress site: an Administrator can manage every event; an Editor can edit and delete other people's events (they have edit_others_posts) but cannot see or act on the attendees and orders of an event they did not create; an Author or Subscriber can create events and fully manage the ones they created.

Changed in 1.3.0. Managing the attendees of an event you do not own now requires site-manager permission (manage_options). Previously it only required edit_others_posts, which meant any Editor could read every organizer's attendee list, cancel registrations, email those attendees, and redeem check-in tokens on events they had nothing to do with. If a non-administrator on your site relied on that reach, you have two remedies: grant that person the Administrator role (or manage_options via a role editor), or leave them as the author of the events they are responsible for and let ownership do the work.

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?

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 → Tools → 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.

Uninstalling

Deactivating Eventonomy preserves all data. Only a full uninstall (delete the plugin) removes the evnm_* tables, options, and capabilities, but only if Settings → Advanced → 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?

Check the Setup & Health screen to confirm everything is wired correctly.

Setup & Health →