My Tickets: DocumentationIn any post type that you’re allowing to be used to sell tickets for events, you’ll have a section labeled “My Tickets Purchase Data” in a metabox for that post type. By default, it should appear underneath your main content area; although it’s impossible to control exactly where it will sit on that screen from a plug-in.
When you click on the checkbox to have sales on this post, the full set of sales options will open:
This form differs from what you see when using My Calendar. In My Calendar the date, time, and location information are all pulled from the event. When creating a ticketed event from a post type, however, you need to set that information in the ticket config.
Location is only available by default if you also have My Calendar installed; it pulls locations from the My Calendar Locations database table. You don’t need to be using My Calendar to use My Tickets, but some features in My Tickets use features in My Calendar.
For advanced users, you can also write a custom function to map another set of location data into a format that My Tickets will understand using the ‘mt_create_location_object’ filter, and define a function called ‘mc_location_select’ that provides the dropdown menu to choose your locations.
The other options when creating events include:
Date-based or General Admissions
Date-based tickets will have a specific date attached to them. They’re good for an event at a specific time. Concert tickets, theater tickets, etc., are common examples of date-based tickets.
General Admissions are tickets that are available at any time within a window. You can purchase the ticket, then it’s good to visit at any time until it expires.
Ticket Model
My Tickets supports three different ticket models: Continuous, Discrete, or Event. These relate to how groups of available tickets are set up. For this type, there’s a single field for tickets available.
Continuous events can have multiple types of tickets, such as “Adult”, “Senior”, or “Child”. These types aren’t all counted as a single group. If you have 100 tickets available for the event, they’re all sold in the same group, regardless of type.
Discrete events have multiple types of tickets, but each type is counted separately. This is where the event seating is separate areas: “Gallery”, “Balcony”, “VIP”, etc. The tickets sold are removed from the pool for that section. Ticket availability is set separately for each date. The number of tickets available needs to bet set separately for each type.
Event types are sold by date. In this scenario, an event doesn’t have separate types of tickets, but has multiple dates and times. An example would be different screenings for a film or theater production.
Other Settings
- Ticket sales end – Set an amount of time before or after the event when you no longer want sales to be possible. It’s always possible to add another sale when you’re logged in as an administrator.
- Allow multiple tickets/ticket type per purchaser – Purchasers can buy multiple tickets for an event – (e.g. 2 adult tickets and one child) in a single cart purchase. If disabled, purchasers can buy only one ticket for an event. Instead of a text input to choose a number of events, they will see a checkbox to select a ticket.
- Type of Sale – This simply toggles the language in use for add to cart forms. E.g. “Buy a Ticket” vs. “Register”
- Ticket Counting Method – Effects whether tickets are counted as a single total or per section.
- Event specific notes – Notes that you can add to the purchase email notification that are specific to this event.
- Don’t display form on event – You can use the ‘ticket’ shortcode to customize where your order form is displayed. If you’re using this in the event post, you may not also want to see the default form.
- Delete ticket sales data on this post: If you’re reusing an existing event, you may want to remove old sales data.