Plugoza Event Ticketing provides a complete local event-booking workflow for WordPress.
Features include:
The plugin stores booking and customer data in the site’s WordPress database. It does not send usage tracking or analytics data to external services.
All plugin JavaScript and CSS files in the assets/ directory are included as human-readable source files. This plugin does not use a JavaScript or CSS build, minification, or compilation step. Composer is used only to install the included PHP libraries for PDF and QR-code generation.
Create an event, enter its description, date, location, policy links, and any other event details. Each event has its own shortcode, available in the Events list and on the Event edit screen.
Create ticket types for each event. Ticket availability is reduced as bookings are made. If all tickets in a type are sold, the booking form displays that ticket type as sold out.
Manual Pay is the built-in payment option in version 1.0. It is enabled automatically after activation and is assigned to new events. Use Event Booking > Payment Gateways to disable it or set the customer-facing payment instructions.
The three required pages are created automatically on activation when absent. If you create pages manually instead, add the appropriate shortcode from the list below and select your Book Events page in Event Booking > Booking Page.
[plugoza_ett_event_list] – Displays published events as booking cards.[plugoza_ett_event_booking] – Displays the event selected from an Event List booking button.[plugoza_ett_event_booking event_id="1"] – Displays a booking form for a specific event.[plugoza_ett_event_ticket id="1"] – Displays a booking form for a specific event.[plugoza_ett_event_details id="1"] – Displays event details and description.[plugoza_ett_event_booking_success] – Displays the booking confirmation and ticket download link.[plugoza_ett_my_tickets] – Displays tickets for the currently logged-in customer.Plugoza Event Ticketing stores the customer name, email address, mobile number, booking details, payment reference, and policy acceptance timestamps that are required to operate event bookings. This data remains on the site’s WordPress installation unless the site administrator configures an external email delivery service.