Events

What it does

Sell admission to performances, workshops and other timed events. Events links an event_ticket product to a ticket type and performance, then issues individually identifiable tickets after payment. Capacity belongs to the performance and can also be constrained for a ticket type. 2

Requirements

Agovena Core ^0.0.1. The manifest declares no additional package dependency. Use the matching Core release and apply the module migrations. 1

Set up the package

Enable Events and run its migrations. Create an event, performance and capacity, then map the product to the correct ticket type. Add the event_ticket capability and verify the schedule shown to customers. Give door staff access to check-in and test a ticket against the intended performance, not just against its public number.

Operation and failure handling

A missing product mapping or insufficient capacity prevents normal admission sales. Paid-order handling issues only the shortfall for each order item. Check-in accepts a ticket token or public ticket number, rejects void tickets and the wrong performance, and reports an already checked-in ticket without admitting it twice. Resolve a payment-to-ticket discrepancy before promising entry; a paid order alone is not the ticket. 2

Sources

• Package manifest
• Browse package source
• EventService.php
• EventsModule.php