Events
An eventA single ticketed offering that people register for: one camp, one party, one conference, or one run of a show. Your site usually runs many events, and each is normally used once and then archived rather than reused (an annual festival creates a new event each year). Each event has its own page on your site, for example example.com/summercamp. When your site has only one active event, EventDrake automatically presents it as the site's main page and keeps the multi-event navigation out of the way. is one ticketed offering on your site, such as one camp, one conference, or one festival year. This page covers creating an event and using its Enabled and Visible switches to decide who can see it and book it.
Create an event
Section titled “Create an event”The new event form, with a General tab and a Dates tab.
- Go to Settings → Events and choose New Event.
- On the General tab, set the URL KeyThe short, web-friendly name that sets where something lives in a web address, made of lowercase letters, numbers, and hyphens. Each event has a URL key: an event with the URL key summercamp appears at example.com/summercamp. URL keys are used across EventDrake wherever something needs a stable, readable address., the Title, and a Short Title for places where space is tight.
- Set Sort Order. Events with higher numbers are listed first, so you can use the year.
- On the Dates tab, set Event Start, Event End, and the Ticket Edit Deadline. Each has a date and a time. When you pick a date first, the time fills in for you: the start of the day for start dates and 11:59 pm for end dates and deadlines. Change the time if you need to.
- Choose Create Event.
The admin opens your new event straight away and selects it in the event list at the top of the sidebar, so you can carry on setting up registration.
Control who can see and book an event
Section titled “Control who can see and book an event”Two switches on the General tab work together:
- Enabled decides whether the event is open to the public at all.
- Visible decides whether the event is listed on your site.
| Enabled | Visible | On your site’s event listings | Event pages | Booking tickets, add-ons, and merch |
|---|---|---|---|---|
| On | On | Listed | Anyone | Anyone |
| On | Off | Not listed | Anyone with the link | Anyone with the link |
| Off | On | Listed as Coming Soon, and can’t be opened | Staff only | Staff only |
| Off | Off | Not listed | Staff only | Staff only |
An event that is enabled but not visible is unlisted. Use this to share an event with a particular group: send them the link, and it stays off your listings and out of search engines.
An event that is turned off is for staff only. People who hold an Administrator, Editor, or Registration roleAn area of access you grant to a person, such as running registration or editing your website. Roles are built in: each one opens a set part of the product. You grant roles to people, and remove them to take access away, but you do not configure what a role can do. A role is either global (applying across your whole site) or event-specific (granted for one event)., either for the whole site or for this event, can open its pages. Only Administrator and Registration can book tickets, add-ons, or merch on it, which lets your team test registration before you open it. Everyone else sees a page not found message.
Search engines are asked not to index an event that is unlisted or turned off.
When changes show up
Section titled “When changes show up”Your public site keeps a short-lived copy of pages so they load quickly. After you switch Enabled or Visible, it can take up to about 15 minutes for your event listings, the event’s pages, and your home page to catch up. This includes the case where your site has one active event and shows it as the home page: after you hide or turn off that event, the home page can keep sending visitors to it for a short while.
An event’s URL key also takes priority over a custom pageA content page you write yourself and publish on your site, such as an About, venue, or privacy page, each at its own web address. Custom pages are separate from the pages EventDrake builds for you, such as registration or the homepage. A site-wide page sits at the top level (example.com/about); an event page sits under its event (example.com/summercamp/venue). with the same address, even while the event is turned off. Give your custom pages addresses that no event uses.