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 <a> 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 and Terms of Service.

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.

Technical details