=== Plugoza Event Ticketing ===
Contributors: hkhandev007, plugoza
Tags: event booking, event tickets, qr tickets, booking manager, pdf tickets
Requires at least: 6.2
Tested up to: 7.0
Requires PHP: 8.4
Stable tag: 1.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Create events, sell tickets, manage bookings, send PDF tickets, and verify ticket QR codes.

== Description ==

Plugoza Event Ticketing provides a complete local event-booking workflow for WordPress.

Features include:

* Event creation with descriptions and per-event terms, privacy, and refund-policy links.
* Multiple ticket types with availability management.
* Manual Pay with an optional customer message shown during booking.
* Responsive event lists and booking forms using shortcodes.
* Booking confirmations with PDF tickets and QR codes.
* Public QR ticket verification and entry-quantity display.
* Admin dashboards for events, orders, customers, tickets, and payment settings.

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.

== Development assets ==

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.

== Installation ==

1. Upload the plugin ZIP from **Plugins > Add New > Upload Plugin**, then activate it.
2. On activation, the plugin creates the following pages only when a page with the required slug does not already exist:
   * **Events**: `[plugoza_ett_event_list]`
   * **Book Events**: `[plugoza_ett_event_booking]`
   * **Booking Success**: `[plugoza_ett_event_booking_success]`
3. The Book Events page is automatically selected in **Event Booking > Booking Page**. Change this setting only if you use a different booking page.
4. Go to **Event Booking > Settings** and configure the currency.
5. Go to **Event Booking > Payment Gateways**. Manual Pay is enabled by default. Optionally add a customer message that will be displayed before a customer completes a booking.
6. Create an event in **Event Booking > Events**, then add one or more ticket types in **Event Booking > Tickets**.
7. Add the Events page to your site navigation if required. The Book Events and Booking Success pages are functional pages and normally do not need to be added to navigation menus.

== Configuration ==

= Events =

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.

= Tickets =

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.

= Payments =

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.

= Required pages and shortcodes =

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**.

== Frequently Asked Questions ==

= Does the plugin send tracking data? =

No. The plugin does not include usage tracking or analytics requests.

= Where is booking data stored? =

Booking, customer, ticket, and event data are stored in custom tables in the WordPress database on your site.

= How are PDF tickets delivered? =

The customer receives a booking-confirmation email with a PDF ticket attachment. The Booking Success page also provides a secure download link.

= What should I do if the booking form says booking is unavailable? =

Make sure the event is published, has at least one active ticket with availability remaining, and has Manual Pay enabled in **Event Booking > Payment Gateways**.

= Does the plugin delete data on deactivation? =

No. Data is removed only if an administrator enables removal before uninstalling the plugin.

== Shortcodes ==

* `[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.

== Privacy ==

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.

== Changelog ==

= 1.0 =
* Initial WordPress.org release.
