Title: Eventrise
Author: Eventrise
Published: September 28, 2026
Last modified: September 28, 2026
---
Search plugins
# Eventrise
By [Eventrise](https://profiles.wordpress.org/eventrise/)
[Download](https://downloads.wordpress.org/plugin/eventrise.1.3.8.zip)
* [Details](https://wordpress.org/plugins/eventrise/#description)
* [Reviews](https://wordpress.org/plugins/eventrise/#reviews)
* [Installation](https://wordpress.org/plugins/eventrise/#installation)
* [Development](https://wordpress.org/plugins/eventrise/#developers)
[Support](https://wordpress.org/support/plugin/eventrise/)
## Description
The official Eventrise plugin lets you sell tickets right from your own WordPress
site. Connect your Eventrise organization once, then add events anywhere with blocks
or shortcodes.
#### Five ways to embed
* **Inline iframe**: the full Eventrise checkout, right on the page.
* **Popup button**: a “Get Tickets” button that opens checkout in a popup.
* **Events grid**: a card grid of all your published events. Each card opens checkout
in a popup.
* **Events page**: your organizer events page on your own site, with an optional
featured section, upcoming events grouped by day, and a month calendar you can
switch to.
* **Auto-link**: any `` link to your Eventrise checkout opens in a popup. No
setup needed, and it works in any theme, page builder or widget.
#### Events block & shortcode
New in 1.2.0: the **Eventrise Events** block (in the _Eventrise_ block category)
and the matching `[eventrise_events]` shortcode show your organizer events page
on your own site, in the same design as your Eventrise landing page.
It has two parts. The optional **Featured** section shows the events you’ve featured:
one or two as full-width cards, or three in a three-column grid. The **Events**
section below it switches between a list and a calendar. The **list** groups upcoming
events by day and shows the title, short description, date · time · location, and
a **Buy Tickets** button that opens Eventrise checkout in a popup. Once sales end,
a **View Event** link and a “Sales have ended” label take its place. The **calendar**
is a month grid starting on Sunday. Each day links its events to their public event
pages, you can move between months, and it has a compact layout on phones.
Attributes (block attribute / shortcode attribute: default):
* `organization` / `organization`: empty. Uses the organization slug from **Settings
Eventrise**. Set it to show another organization’s public events.
* `showFeatured` / `show_featured`: `true`. The featured events strip. It only
shows when the organization’s Eventrise landing page is turned on. Otherwise
the section is left out.
* `showList` / `show_list`: `true`. The list of upcoming events, grouped by day.
* `showCalendar` / `show_calendar`: `true`. The month calendar. Turn off both the
list and the calendar to show only the featured strip. If featured is off too,
the block shows a notice that only editors can see.
* `defaultView` / `default_view`: `list`. Either `list` or `calendar`, whichever
should open first. If only one is turned on, that one opens.
* `limit` / `limit`: `0`. The most upcoming events to show in the list. `0` shows
all of them (up to 100). This doesn’t affect the featured strip or the calendar.
* `heading` / `heading`: empty, which shows “Events”. The section heading.
* `featuredHeading` / `featured_heading`: empty, which shows “Featured Event” or“
Featured Events”. The featured section heading.
The block also supports wide and full width and an HTML anchor. On/off shortcode
attributes accept `yes/no`, `true/false`, `1/0` and `on/off`. For example:
```
[eventrise_events show_calendar="no" limit="6" heading="Upcoming shows"]
[eventrise_events organization="other-org" default_view="calendar"]
```
#### Built for WordPress.org standards
* Blocks are rendered on the server, which is good for SEO and accessibility.
* All assets are bundled. No scripts load from other sites.
* No tracking and no telemetry.
* Licensed GPL-2.0-or-later.
* Translation-ready.
* Multisite-compatible.
#### External services
This plugin connects only to Eventrise’s own services.
**Eventrise API**: read-only requests for your organization and its events. Without
an API key, the plugin uses four endpoints:
* `GET /api/v1/organizations/{slug-or-id}`: your organization’s name and public
settings (to check your slug on the settings page).
* `GET /api/v1/events?organization_id={slug-or-id}`: the public list of your published
events (Events Grid block, the editor’s event picker, and the Events block’s
list and calendar).
* `GET /api/v1/organizations/{slug}/featured_events`: your featured events (only
for the Events block’s featured section). Returns a 404 when your Eventrise landing
page is turned off, and the section is left out.
* `GET /api/v1/events/{id}`: a single event (used only in the editor, through the
plugin’s REST proxy).
If you add the optional API key, the Events Grid block, the editor’s event picker
and the single-event read use your organization’s authenticated endpoints instead(`
GET /api/v1/organizations/{slug}/events` and `GET /api/v1/organizations/{slug}/events/{
id}`), and send the key as a bearer token. The Events block never does.
The host is `https://api.eventrise.com` (Production) or `https://api.dev.eventrise.
com` (Staging), set by the **Environment** setting.
**Eventrise Checkout** at `https://checkout.eventrise.com` (Staging: `https://checkout.
dev.eventrise.com`): embedded as an iframe to handle ticket purchases.
**Eventrise web app** at `https://app.eventrise.com` (Staging: `https://app.dev.
eventrise.com`): where the Events block’s “View Event” links go. They open the public
event page `https://app.eventrise.com/events/{slug}` in a new tab. Nothing loads
from that host until a visitor clicks one of those links.
By using this plugin, your visitors will load content from `checkout.eventrise.com`
when they reach an embedded checkout. See [Eventrise’s Privacy Policy](https://eventrise.com/privacy-policy)
and [Terms of Service](https://eventrise.com/terms-and-conditions).
#### Third-party assets
The Events block uses two typefaces. Both are bundled with the plugin under `assets/
fonts/` with their license files, and served from your own site, never from a CDN:
* **Bricolage Grotesque**: © The Bricolage Grotesque Project Authors. SIL Open
Font License 1.1.
* **Rethink Sans**: © The Rethink Sans Project Authors. SIL Open Font License 1.1.
## Blocks
This plugin provides 4 blocks.
* Eventrise Get Tickets Button A button that opens an Eventrise checkout in a
popup.
* Eventrise Event Embed Embed a single Eventrise event as an inline iframe.
* Eventrise Events Grid Show a grid of upcoming Eventrise events from your organization.
* Eventrise Events Your organization's featured events, upcoming events list
and calendar, styled by Eventrise so your theme won't change them.
## Installation
1. Upload the plugin in **Plugins Add New Upload Plugin**, or install it from the
WordPress.org plugin directory.
2. Activate the plugin.
3. Go to **Settings Eventrise** and paste your organization slug or ID.
4. Click **Save Changes**. The plugin checks your slug with Eventrise as it saves.
A green _Connected to …_ notice means it worked. If we can’t find the slug, you’ll
see an error and it won’t be saved.
5. Add an Eventrise block to any post or page, or use the matching shortcode.
## FAQ
### Where do I find my organization slug?
Sign in to your Eventrise organizer dashboard. The slug is the part of your organization’s
URL after `eventrise.com/`. Your organization ID works too.
### My iframe shows a blank page. What’s wrong?
Eventrise checkout can be embedded on any site, so there’s nothing to allow-list.
Check your browser console for a `frame-ancestors` Content Security Policy error,
and make sure the event slug is right and the event is published. Your site’s origin
is still shown under **Settings Eventrise Advanced** with a Copy button, in case
Eventrise adds an embed allow-list later.
### Does this plugin handle payments?
No. The plugin embeds Eventrise’s hosted checkout in an iframe, and Eventrise handles
all payments (through Stripe). The plugin never sees card details.
### Can I disable the auto-link feature?
Yes. Turn off **Auto-link conversion** in **Settings Eventrise**. You can also
opt out a single link with the `data-eventrise-no-modal` attribute or `target="_blank"`.
### Will I lose my settings if I deactivate the plugin?
Deactivating keeps your settings. Deleting the plugin (in **Plugins Delete**) removes
them, by design.
### Does this work with page builders (Elementor, Beaver Builder, etc.)?
Yes. Shortcodes work in any page builder that supports them. Auto-link works everywhere:
add a normal link to `checkout.eventrise.com/checkout/{event-slug}` and it’ll open
in a popup.
### Can I restyle the plugin with my own CSS?
Yes, with CSS custom properties. The plugin’s styles are marked `!important` so
no theme can repaint them by accident (many themes style every `button` on the page).
That also means a plain CSS rule of yours won’t win. Instead, set the custom property
you want to change. The plugin’s styles read those properties, so whatever you set
is what shows:
```
:root {
--eventrise-color-primary: #c0392b;
--eventrise-font-body: "Inter", sans-serif;
--eventrise-radius-card: 4px;
}
```
Put that in **Appearance Customize Additional CSS**, or in your child theme’s
stylesheet. Every property below is optional. Leave one out to keep the default.
**Events block** (the Eventrise brand palette)
* `--eventrise-font-display`, `--eventrise-font-body`: the two typefaces.
* `--eventrise-color-primary`, `--eventrise-color-primary-hover`, `--eventrise-
color-primary-active`: the Buy Tickets button and other accents.
* `--eventrise-color-text`, `--eventrise-color-text-muted`, `--eventrise-color-
surface`: body text, secondary text, card background.
* `--eventrise-color-outline-border`, `--eventrise-color-outline-border-hover`,`--
eventrise-color-outline-bg-hover`: the View Event button.
* `--eventrise-color-border`, `--eventrise-color-border-strong`, `--eventrise-color-
grey-100`, `--eventrise-color-grey-500`, `--eventrise-color-purple-25`, `--eventrise-
color-purple-50`: dividers, calendar cells and labels.
**Get Tickets Button and Events Grid**
* `--eventrise-accent`, `--eventrise-accent-hover`: the button and link colour.
* `--eventrise-button-label`: the Get Tickets button’s text colour on a filled
background.
* `--eventrise-ink`, `--eventrise-ink-muted`, `--eventrise-ink-body`: card title,
date, description.
* `--eventrise-card-bg`, `--eventrise-card-border`, `--eventrise-grid-image-bg`,`--
eventrise-empty-border`: grid card surfaces.
* `--eventrise-radius-button`, `--eventrise-radius-card`, `--eventrise-grid-gap`,`--
eventrise-grid-card-padding`: shape and spacing.
**Checkout modal**
* `--eventrise-modal-bg`: the popup’s background, behind the checkout frame.
* `--eventrise-radius-modal`, `--eventrise-modal-backdrop`: the popup’s corners
and the dimmed page behind it.
* `--eventrise-modal-max-width`: how wide the popup can get (720px by default).
The close button sits beside the account avatar in the Eventrise checkout header.
If you make the popup much narrower, check that they don’t overlap.
* `--eventrise-modal-close-hover`: the close button’s hover fill.
* `--eventrise-modal-fallback-bg`, `--eventrise-modal-fallback-border`, `--eventrise-
modal-fallback-text`: the “Having trouble?” bar shown if checkout is slow to
load.
The class names are stable too, all starting with `eventrise-` (`.eventrise-events`,`.
eventrise-grid__card`, `.eventrise-modal__close`), if you need to target something
the properties above don’t cover. You’ll need `!important` on those rules.
### Why is the Featured section missing from the Events block?
The featured strip only shows when your organization’s Eventrise landing page is
turned on (organizer dashboard **Settings Landing page**). When it’s off, Eventrise
doesn’t publish a featured list, so the block leaves the section out. The list and
calendar still show as usual. The section is also left out when you have no featured
events, or when `show_featured` is set to `no`.
### Which events does the Events block show, and how many?
It reads up to your organization’s 100 most recent published events (sorted by start
date, newest first). The list shows the upcoming ones, up to the `limit` attribute
if you set one. The calendar shows all of them, including past months you go back
to. A multi-day event appears once, on its start day, and every time is shown in
that event’s own time zone. Responses are cached in WordPress transients for 5 minutes(
60 seconds for a failed lookup), the same as the rest of the plugin.
### Why does the Events block look different from my theme?
By design. The block uses the same design as your Eventrise landing page, and all
of its styles are scoped under `.eventrise-events`. Your theme can’t restyle it,
and its styles can’t leak into the rest of your page. Its two typefaces, Bricolage
Grotesque and Rethink Sans, ship with the plugin and are served from your own site.
To match your own brand instead, see “Can I restyle the plugin with my own CSS?”
above.
### Does the Events block use my API key?
No. It always reads the public Eventrise catalog and never sends your API key. Its**
Buy Tickets** buttons open the same checkout popup as the Get Tickets Button block(
so the auto-link rules apply), and **View Event** links open the public event page
on `app.eventrise.com` in a new tab.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Eventrise” is open source software. The following people have contributed to this
plugin.
Contributors
* [ Eventrise ](https://profiles.wordpress.org/eventrise/)
[Translate “Eventrise” into your language.](https://translate.wordpress.org/projects/wp-plugins/eventrise)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/eventrise/), check
out the [SVN repository](https://plugins.svn.wordpress.org/eventrise/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/eventrise/) by [RSS](https://plugins.trac.wordpress.org/log/eventrise/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.3.8
* Smaller download: the package no longer includes a copy of its own zip or a test
configuration file.
#### 1.3.7
* Plainer wording in settings help text, block titles and descriptions, editor
notices, and error messages. Block titles drop the dash (for example, “Eventrise
Events”).
* New plugin directory icon and banner.
#### 1.3.6
* Maintenance: updated development tooling. No change to the plugin’s code or behavior.
#### 1.3.5
* Fix: deleting the plugin now also clears its settings from sites that use a persistent
object cache (Redis, Memcached), instead of leaving stale copies cached.
#### 1.3.4
* The plugin’s homepage link now points at the Eventrise developers page.
#### 1.3.3
* Security hardening from the WordPress.org review: all output is escaped at the
point it is printed. No visible change.
* Fix: the Privacy Policy and Terms of Service links pointed at pages that no longer
exist.
* Translations are now loaded by WordPress itself.
#### 1.3.2
* Fix: the plugin failed the WordPress.org automated Plugin Check because the three
starter block patterns were written with heredoc syntax. They are now plain strings;
the patterns themselves are unchanged.
#### 1.3.1
* Docs: the installation steps now describe how the settings page actually validates
your organization: on **Save Changes**. There is no separate “Test connection”
button.
* Docs: the External services section now lists the authenticated endpoints the
plugin uses when you configure the optional API key.
* Docs: corrected the blank-iframe FAQ. Eventrise checkout allows embedding from
any site, so there is nothing to allowlist.
* Change: development tooling moved from npm to pnpm. No change to the plugin’s
behaviour.
#### 1.3.0
* Fix: the checkout modal’s close button, the Get Tickets Button block and the
Events Grid cards rendered in the active theme’s button skin instead of the plugin’s
own. Themes style bare buttons more specifically than a single plugin class,
so the theme supplied their background, text colour and padding. On the close
button that turned a circle into a stretched pill.
* Fix: the modal’s close button no longer covers the account avatar in Eventrise
checkout’s header; it now sits in the gap beside it.
* Fix: Events Grid cards lost their image, description and call-to-action styling
because the stylesheet targeted class names the markup does not use. Compact
cards now correctly drop the image.
* Add: **CSS custom properties for restyling the plugin.** Every colour, font and
corner radius now reads through an `--eventrise-*` property, so you can match
the plugin to your brand from Additional CSS without fighting the plugin’s own
styles. See the FAQ for the full list.
#### 1.2.1
* Fix: the release zip omitted the `assets/` directory (settings-page script, bundled
font license files) and the `LICENSE` file. No functional change to the blocks.
#### 1.2.0
* Add: **Eventrise Events** block and `[eventrise_events]` shortcode: your organizer
events page on your own site, with an optional featured section, upcoming events
grouped by day, and a month calendar behind a list/calendar toggle. Styles are
fully isolated from the active theme and the two typefaces are bundled, not loaded
from a CDN.
* Add: developer-only constants `EVENTRISE_API_BASE_OVERRIDE`, `EVENTRISE_CHECKOUT_BASE_OVERRIDE`
and `EVENTRISE_WEB_BASE_OVERRIDE`, honoured only when `WP_DEBUG` is true, for
developing against a local Eventrise stack.
* Add: `EVENTRISE_WEB_BASE` / `EVENTRISE_WEB_BASE_STAGING` constants for the public
Eventrise website host.
* Fix: the `start_at` sort option on the events grid and REST proxy is now sent
to the API as `start_date`. It silently sorted by name before.
* Fix: `[eventrise_embed]`, `[eventrise_button]` and `[eventrise_grid]` now enqueue
their block stylesheet, so they render styled outside the block editor.
* Fix: block stylesheets were registered without a source (the block manifests
pointed at `style.css` instead of the built `style-index.css`), so the embed,
button and grid blocks were unstyled; all four blocks now load their CSS on the
frontend and in the editor.
* Add: block pattern **Organizer events page**: a heading plus the Events block.
* Change: continuous integration moved to Blacksmith runners.
* Change: tested up to WordPress 7.1; development tooling refreshed (no change
to shipped files).
#### 1.1.0
* Fix: events grid rendered an empty container when the API returned its standard`{
success, data}` envelope.
* Fix: event-embed iframe and Get-Tickets-button noscript fallback now follow the
configured environment instead of always pointing at production.
* Add: Environment setting (Production / Staging) on the settings page; switching
environments flushes the cache and re-validates the org slug.
* Change: cache keys are namespaced by environment so production and staging payloads
cannot collide.
* Change: plugin upgrades flush the API cache automatically.
#### 1.0.0
* Initial release.
* Three Gutenberg blocks: Event Embed, Get Tickets Button, Events Grid.
* Three matching shortcodes: `[eventrise_embed]`, `[eventrise_button]`, `[eventrise_grid]`.
* Vanilla JS modal with full keyboard accessibility and `