Documentation /Reference
Shortcode reference
| Shortcode | Attributes | Renders |
|---|---|---|
[eventnetic_ |
limit, search, past, category |
A grid of upcoming events |
[eventnetic_ |
event (required), date, package |
The booking form for one event |
[eventnetic_ |
view, date, category, switcher, paging |
A calendar of what is coming |
[eventnetic_ |
none | Booking lookup by code and email |
[eventnetic_ |
none | The confirmation after paying |
[eventnetic_events]
limit — how many to show. Default 9, allowed 1 to 48.
search — yes or no. Default yes.
past — yes or no. Default no.
category — comma-separated category slugs. Pins the widget to those
categories permanently.
[eventnetic_events category="cinema,tours" limit="12" search="no"]
[eventnetic_booking]
event — the event id, required. The event editor's Public page field
creates a page carrying this for you.
date — one of the event's dates, by its id. The form opens on that date.
package — one of the event's packages for the dates (a run, a pass, the
whole series), by its id. The form opens with it chosen. A package that is off
sale or sold out opens the form with nothing chosen.
date and package are for a page that lists the dates or the runs itself and
gives each row its own Book button. The ids come from the
public REST API: dates[].id, and tickets[].id
where kind is package, on the single event.
[eventnetic_booking event="12" date="345"]
[eventnetic_booking event="12" package="77"]
A link does the same with ?evntc_occurrence=345 or ?evntc_package=77 on the
page that carries the form. On that page, a popup can put in a fresh form for
the row that was clicked, and its own attributes win over the link:
<div class="eventnetic-mount" data-eventnetic-booking="12" data-eventnetic-package="77"></div>
The shortcode also outputs schema.org Event markup, so search engines can read
the date, the venue and the price without being told twice.
If the id is missing, or the shortcode is on a page that is not a single post, an administrator sees a hint. Visitors see nothing.
[eventnetic_my_bookings]
The lookup: a Booking code and an Email. It is also where a payment
provider returns the customer, via ?evntc_order=, so this page must be set
under Settings → General settings → Public pages.
With the customer panel (Pro and Elite), a customer who is signed in sees all their bookings here instead of the lookup. See The customer panel.
From here a customer can download tickets, add the date to a calendar, follow the joining link for an online event, and — if you allow it — cancel.
[eventnetic_thank_you]
The page shown straight after paying: the codes, the tickets, the calendar file and the joining link. Also set under Public pages.