Eventotron

Eventotron is a festival and season management service used by arts festivals, fringes and venues. This plugin connects a WordPress site to a season in your Eventotron account and publishes it on the site.

What it does

• Imports events, performances, venues and merchandise from your season as WordPress content, with the fields you choose mapped onto each page.

• Adds searchable “What’s On” listings for events, performances and venues, filterable by date, genre, venue, keyword, your own custom fields, and distance from a typed location.

• Shows a map of the results and of each venue.

• Adds a “departure board” shortcode of the next performances starting near the visitor, using their browser’s location if they allow it.

• Keeps the site in step with Eventotron: refresh a season by hand, or let a background sync pick up changed events and venues every 15 minutes.

• Sells tickets and merchandise through the Eventotron checkout. Buying happens inside Eventotron’s own window; this plugin does not take payment details.

• Lets buyers sign in to their Eventotron account from your site with the [etron_account] shortcode, so they can see their orders. Sign-in happens inside Eventotron’s window too.

• Lets you tailor every listing and page layout from the settings screens, or override the templates from your theme.

You need an Eventotron account. The plugin does nothing until it is connected to a season with an API key from your Eventotron dashboard. com for plans and terms.

Third-party code

• Leaflet 1.9.4 (https://leafletjs.com), BSD-2-Clause, bundled unminified in assets/lib/leaflet.

• The distance search is adapted from WP Geo Query by Greg Schoppe (https://gschoppe.com/wordpress/geo-searches/).

External services

This plugin relies on the services below. Nothing is sent to anyone else, and no usage data is collected by the plugin itself.

com) — the service this plugin exists to publish. It is used for three things:

• Importing your season: the plugin fetches your season’s events, performances, venues and merchandise from Eventotron’s API ( https://eventotron.com/api/wp-bridge/ ) using the season API key you enter in the settings. This happens when you connect or refresh a season, and every 15 minutes if background sync is switched on. Only the API key is sent.

• Selling tickets: pages that sell tickets load Eventotron’s checkout script from https://eventotron.com/embed/v1/embed.js. Ticket selection, buyer sign-in and payment all happen inside Eventotron’s own window; this plugin never sees payment details or buyer accounts.

• The “Where” filter: the place name a visitor types is sent to Eventotron to be turned into map coordinates. Nothing else about the visitor is sent, and results are cached for a day.

com/terms. com/privacy. You need an Eventotron account for any of this to work.

net ) into your media library, and built-in listings, maps and social-image metadata use that media-library copy. If the image import fails, these views omit the image rather than loading the original remote URL. Custom template fields styled as images, custom HTML and theme overrides may still load URLs supplied by the site owner or the imported data directly; those image hosts then receive the visitor’s IP address and normal browser request headers.

Covered by the Eventotron terms and privacy policy above.

org) — map tiles are loaded from OpenStreetMap’s public tile servers when a page shows a map, which means those servers receive the visitor’s IP address as part of the request. org/policies/tiles/. org/wiki/Privacy_Policy.

Busy sites should use the etron_map_tile_url and etron_map_tile_attribution filters to point at a hosted tile provider of their choice.

com ), which loads only when that page is viewed. com/privacy. com/privacy.

The visitor’s browser location — the departure board’s “Nearest” option asks the browser for the visitor’s location. The browser asks the visitor for permission first, and the coordinates are used only to order results on that page; they are not stored.