Eventward

Recurring events and time zones

• Daily, weekly, monthly (“the second Tuesday”, “the last Friday”) and yearly schedules, with intervals, end dates, counts, skipped dates and extra dates.
• A custom option for anything else the iCalendar standard can describe.
• A timezone per event, with correct local times across daylight saving changes.
• Each date of a repeating event has its own page and its own entry in Google’s event data.

Venues, organizers and maps

• Create venues and organizers inline while editing an event. Each gets its own page listing its upcoming events.
• Maps without API keys. OpenStreetMap maps for the calendar, venues and events, with clustered pins, bundled with the plugin.
• Place venues by typing their coordinates, or turn on address lookup (OpenStreetMap Nominatim, off by default) to find them from the address when you save.

Tickets and RSVP

• Free RSVP and paid tickets, several ticket types per event, with capacity per type and per date.
• Stripe Checkout in test and live mode. Connect your Stripe account in one click, or paste a restricted API key.
• Seats are held while a buyer pays and released automatically if they do not finish, so a date does not oversell.
• Confirmation emails with ticket codes, an attendee list with check-in, CSV export, one-click refunds and resending confirmations.
• Your own booking questions on each ticket type (short or long text, dropdown, yes-or-no tick box, phone number), answered once per ticket, with answers on the attendee list, in the CSV and in the emails. Logged-in visitors find their name and email already filled in, which suits membership sites.
• Reports: bookings, check-ins, no-shows and takings by month, by date and by ticket type for any period, with capacity filled per date and a CSV export for your annual figures.
• An optional Stripe webhook for instant confirmations. Without it, payments are still confirmed when buyers return and by a background check.
• Bookings are included in WordPress’s personal data export and erasure tools.

Themes, blocks and page builders

• Native blocks and Site Editor templates for block themes.
• Shortcodes for the calendar, event details, single fields (date, venue, cost and more), tickets and maps, for Bricks, Divi, Elementor and other builders.
• A sortable “next date” field for page builder query loops.

Sharing and SEO

• schema.org Event data on every event: status, attendance mode, location, organizer, price and availability.
• Add to calendar links for Google Calendar, Apple Calendar, Outlook and Microsoft 365, plus subscribable iCal feeds for the whole calendar or any category.
• Event status for cancelled, postponed, rescheduled and moved online events, shown on the page and sent to Google.

Fair by default

• No upsells, no admin banners, no ads and no tracking. Every external service Eventward can use is listed below, with what it sends and when.
• Your data stays yours: deactivating never deletes anything, and uninstalling only removes events if you ask it to.
• Translation ready.

Eventward is made by OmnisWP, the team behind Siteward.

External services

Eventward works on your own site, except for the services below:

• OpenStreetMap Nominatim (geocoding). Off by default: nothing is sent until an admin turns on address lookup under Events > Settings > Maps. When on, it turns venue addresses into map locations. Your site contacts https://nominatim.openstreetmap.org when a venue is saved with a new or changed address, when you press “Find on map”, and in an hourly background check that looks up to 10 venues that have never been looked up (for example imported ones). Venues whose coordinates you typed yourself are never looked up. Each request sends the venue’s address (street, city, region, postcode, country), your site’s address (in the User-Agent, as Nominatim’s policy requires) and your site’s language. Nothing about your visitors is sent. You can turn it off again at any time. Usage policy: https://operations.osmfoundation.org/policies/nominatim/ Privacy policy: https://osmfoundation.org/wiki/Privacy_Policy
• OpenStreetMap map tiles. Pages that show a map load map images from https://tile.openstreetmap.org in the visitor’s browser (only once the map scrolls into view). The visitor’s IP address and the page address are visible to that server, as with any image. Tile usage policy: https://operations.osmfoundation.org/policies/tiles/ Privacy policy: https://osmfoundation.org/wiki/Privacy_Policy You can switch to another tile provider under Events > Settings > Maps.
• Add to calendar links (Google Calendar, Outlook.com, Microsoft 365) are ordinary links: nothing is sent unless a visitor clicks one.
• Stripe (payments). Only when you sell paid tickets. Your site talks to https://api.stripe.com to create Stripe Checkout sessions, confirm payments and make refunds. For each checkout your site sends the buyer’s email address, the event title, date and time, the tickets with their prices, an order reference and the addresses of your event page that Stripe returns the buyer to; card details are entered on Stripe’s own page and never touch your site. If you add the optional webhook in your Stripe Dashboard, Stripe also sends payment and refund notices to your site. Stripe terms: https://stripe.com/legal Privacy policy: https://stripe.com/privacy
• OmnisWP connection service. Only if you choose “Connect with Stripe” instead of pasting an API key. Stripe’s app login needs a secret held by OmnisWP, so https://omniswp.com/wp-json/omnis-connect/v1 is contacted only when an admin presses “Connect with Stripe” (your site first checks the service is available for that mode), and while connected, to renew the short-lived access token: by a background check every 30 minutes, and on demand if the token has run out when your site next talks to Stripe (for example during a booking). When connecting, the admin’s browser takes the mode (test or live), a one-time challenge and the address of your site’s Payments screen to omniswp.com, and your site then sends the one-time claim code and its matching secret to collect the tokens. When renewing, your site sends the mode and the refresh token. Like any WordPress request, these carry your site’s address in the User-Agent. The service never sees payments or buyer details, and keeps nothing after handing the tokens to your site. Terms: https://omniswp.com/terms/ Privacy policy: https://omniswp.com/privacy-policy/

Third-party libraries

• Leaflet 1.9.4, BSD 2-Clause licence, https://github.com/Leaflet/Leaflet (bundled in assets/vendor/leaflet, minified build from the official npm package)
• Leaflet.markercluster 1.5.3, MIT licence, https://github.com/Leaflet/Leaflet.markercluster (bundled in assets/vendor/leaflet-markercluster)