Title: My Tickets &#8211; Accessible Event Ticketing
Author: Joe Dolson
Published: <strong>جنوری 31, 2015</strong>
Last modified: پروری 24, 2026

---

Search plugins

![](https://ps.w.org/my-tickets/assets/banner-772x250.png?rev=1097581)

![](https://ps.w.org/my-tickets/assets/icon-256x256.png?rev=1097581)

# My Tickets – Accessible Event Ticketing

 By [Joe Dolson](https://profiles.wordpress.org/joedolson/)

[Download](https://downloads.wordpress.org/plugin/my-tickets.2.1.2.zip)

[Live Preview](https://bcc.wordpress.org/plugins/my-tickets/?preview=1)

 * [Details](https://bcc.wordpress.org/plugins/my-tickets/#description)
 * [Reviews](https://bcc.wordpress.org/plugins/my-tickets/#reviews)
 *  [Installation](https://bcc.wordpress.org/plugins/my-tickets/#installation)
 * [Development](https://bcc.wordpress.org/plugins/my-tickets/#developers)

 [Support](https://wordpress.org/support/plugin/my-tickets/)

## Description

Sell tickets or take reservations for events easily! My Tickets integrates with 
[My Calendar](https://wordpress.org/plugins/my-calendar/) or can be used for ticket
sales as a stand-alone plugin. Sell tickets for box office pick up, shipping, or
accept print-at-home and e-tickets for an easy experience for your ticket holders!

My Tickets ships with PayPal Standard payments, so you can sell tickets immediately.
You can also take offline payments, to use My Tickets as a reservation tool while
you handle payments by mail or at the door.

Explore the [premium add-ons for My Tickets](https://www.joedolson.com/my-tickets/add-ons/)!

Premium event ticketing add-ons include:

 * Offer a variety of secure ticket payments with premium gateways, including [Stripe](https://www.joedolson.com/awesome/my-tickets-stripe/),
   [PayPal Pro](https://www.joedolson.com/awesome/my-tickets-paypal-pro/), and [Authorize.net](https://www.joedolson.com/awesome/tickets-authorize-net/).
 * Encourage users to support your organization by taking [in-cart donations](https://www.joedolson.com/awesome/my-tickets-donations/).
 * Offer your customers special discount opportunities with [discount codes and coupons](https://www.joedolson.com/awesome/my-tickets-discounts/)
 * Improve conversion and avoid lost opportunities with [automatic waiting lists](https://www.joedolson.com/awesome/my-tickets-waiting-list/).

#### Basic Features:

For buyers:

 * Create an account to save your address and shipping preferences
 * Automatically convert shopping carts to your account if you log-in after adding
   purchases
 * Buy tickets for multiple events, with multiple ticket types.

For sellers:

 * Get reports on ticket sales by time, event, or specific ticket options within
   an event.
 * Easily add new ticket sales from the box office, when somebody pays in person,
   by phone, or by mail.
 * Use your mobile phone and a standard QRCode reader to verify print-at-home tickets
   or e-tickets
 * Send email to a single purchaser with questions about their ticket purchase, 
   or mass email all purchasers for an event.
 * Select default event settings grouped by audience type (Adult, Student, Child),
   seating sections (Section 1, Section 2, Section 3) or individual event dates.
 * Offer member-only discounts for logged-in users
 * General Admission tickets: Sell tickets for events without dates, valid for days,
   weeks, or months after purchase.

My Tickets is flexible and easy to extend – check out the [library of Premium add-ons](https://www.joedolson.com/my-tickets/add-ons/)!

#### Accessibility

My Tickets is built with accessibility in mind, and tested using assistive technology.

#### Documentation

Read the [My Tickets online documentation](http://docs.joedolson.com/my-tickets/).

## Screenshots

 * [[
 * Add to Cart Form
 * [[
 * Shopping Cart
 * [[
 * Payment Admin

## Installation

 1. Upload the `/my-tickets/` directory into your WordPress plugins directory.
 2. Activate the plugin on your WordPress plugins page
 3. Configure My Tickets using the following pages in the admin panel:
 4. My Tickets -> Settings
     My Tickets -> Payment Settings My Tickets -> Ticket Settings
    My Tickets -> Reports My Tickets -> Ticketing Help
 5. With [My Calendar](https://wordpress.org/plugins/my-calendar/), add ticketing to
    an event. Without My Calendar, choose what post types will support tickets from
    My Tickets -> Settings, and add ticketing to any post or Page!

## FAQ

### I’m trying to sell tickets with My Calendar, but can’t see how to add sales information

The My Tickets sales information is entered in the ‘Registration Information’ panel
of the My Calendar add event screen. This may be turned off in your installation.
There are two places to look to enable it. First, go to My Calendar > Settings and
go to the Input Settings section. If the ‘registration’ option isn’t checked, check
it and save settings. Second, go to the Add Event screen. If the registration options
still aren’t visible, you may need to enable them in your personal Screen Options.
Open the Screen Options panel and check the option there – these are settings that
apply only to your account.

### I’m trying to sell tickets on a recurring event in My Calendar, but all the dates are the same

My Tickets data is associated with post IDs, and My Calendar’s recurring events 
are all based off the same event post. As a result, My Tickets doesn’t work with
recurring events in My Calendar.

### If I visit the ‘Tickets’ or ‘Receipts’ pages, I end up on the Purchase page. What’s happening?

The Tickets and Receipts pages are only for displaying purchased tickets or purchase
receipts. If no valid ID for one of those resources is included, then they’ll redirect
to the shopping cart.

### How do I scan QR Codes for events?

You can use any QR Code scanning app for a mobile phone or other mobile device with
a camera. In order to get the ticket status confirmation, you’ll need to be connected
to a network.

### Is the “number of tickets available” field required?

Yes. My Tickets won’t sell an unlimited number of tickets for an event; in order
for My Tickets to sell anything, you need to specify how many tickets it’s allowed
to sell.

## Reviews

![](https://secure.gravatar.com/avatar/0bb3145d3f81130f2606b5bc4461f390891bc96f45780b74ea1bec64961b0b6a?
s=60&d=retro&r=g)

### 󠀁[won’t work](https://wordpress.org/support/topic/wont-work-38/)󠁿

 [ourlocalyarn1912](https://profiles.wordpress.org/ourlocalyarn1912/) جُلائی 5, 
2023 1 reply

Ever since this new plug-in update i am not able to edit my website. The happiness
engineer said it was an issue with this plug-in update. Have tried to contact Joe
via the forum but no response. Am going to cancel my Wordpress account if I can’t
get this fixed.

![](https://secure.gravatar.com/avatar/6804c0db027fbb5e4f6b8d22dc0748ca948514d298ecbdfbaf0e4688d9a475ce?
s=60&d=retro&r=g)

### 󠀁[Works flawlessly](https://wordpress.org/support/topic/works-flawlessly-180/)󠁿

 [RMWeb Elements](https://profiles.wordpress.org/rivermobstermedia/) اکتوبر 18, 
2022 1 reply

Thank you for the great product!!!

![](https://secure.gravatar.com/avatar/136c7ff84d50bb2db15d03634ec7c7c77c6c29446baec6e55de1383a6c069630?
s=60&d=retro&r=g)

### 󠀁[It works!](https://wordpress.org/support/topic/it-works-2248/)󠁿

 [polehamster](https://profiles.wordpress.org/polehamster/) پروری 11, 2022 1 reply

Very impressed with this plugin. We use it for ticketing to events and a visitor
attraction. It’s easy to set up a new event, set different prices for different 
categories of visitors, get reports on how many have booked in. We use the Stripe
add-on, so money goes straight into the bank account, less Stripe’s fees of course.
On the gate, the QR code scanning works perfectly, and the system can be accessed
on a phone – if someone has booked their ticket while waiting in the queue, you 
can get into the system in real time and check what they have booked. We did have
some problems in the early stages with some software bugs, but Joe gives exemplary
support – he gets back to you quickly, and because he built the system he know the
issues and context. It might be nice to have easy ways to customize the appearance
of the tickets sent out, and of other messages, but this is a trivial detail – other
systems are weighed down with stupid eye-candy that does not improve the functionality,
but leaves lots of places for bugs to lurk.

![](https://secure.gravatar.com/avatar/dfa1efef51191c2e46cf876d034e36ae0c655287d939d6d0ab0c522caf08bd77?
s=60&d=retro&r=g)

### 󠀁[Simple clever](https://wordpress.org/support/topic/simple-clever-2/)󠁿

 [Jose Lazo](https://profiles.wordpress.org/jose-lazo/) جُون 17, 2021

Great FREE plugin! Congratulations to @joedolson for it.

![](https://secure.gravatar.com/avatar/b2630f1635f046600af04302e27abeafd14f91d0e121e157288d6189c02214cf?
s=60&d=retro&r=g)

### 󠀁[Lightweight and well thought-out](https://wordpress.org/support/topic/lightweight-and-well-thought-out/)󠁿

 [efrap](https://profiles.wordpress.org/efrap/) اگست 12, 2020 5 replies

I have been testing various ticketing plugins, My Tickets really stands out. Lightweight,
well thought out, simple but with the right features. Great work. Taxes is the only
option missing for me. I need two different ones. I will include taxes in the total
price and have succeeded in displaying tax details in the receipt template by including
some of the functions found in mt-templating.php. A minor improvement would be currency
symbol positioning, as I need the dollar symbol to be placed after the amount with
a space (French standard). Overriding currency symbol by manual input would also
be useful (for CAD, ‘C $’ is confusing for my users, just need ‘$’).

![](https://secure.gravatar.com/avatar/556932dfe9feba6bccb25e3ccd8a94018920f40cad0d093aa348d8646922f7de?
s=60&d=retro&r=g)

### 󠀁[great event management free plugin](https://wordpress.org/support/topic/great-event-management-free-plugin/)󠁿

 [gustohe](https://profiles.wordpress.org/gustohe/) مارچ 20, 2019 1 reply

Thanks a lot for the development of this nice plugin, it helps solve my demands 
for event management once and for all. I have downloaded many other event management
plugins, but for the registration, especially the bar code email notification part,
every plugin will ask for premium upgrades. Although I fully support that every 
developer should get paid for their work, but they should state it clearly in their
plugin introduction. But for My Tickets, what it can do is exactly what it states
in the description. JOE DOLSON, Thanks for your great work.

 [ Read all 27 reviews ](https://wordpress.org/support/plugin/my-tickets/reviews/)

## Contributors & Developers

“My Tickets – Accessible Event Ticketing” is open source software. The following
people have contributed to this plugin.

Contributors

 *   [ Joe Dolson ](https://profiles.wordpress.org/joedolson/)

“My Tickets – Accessible Event Ticketing” has been translated into 6 locales. Thank
you to [the translators](https://translate.wordpress.org/projects/wp-plugins/my-tickets/contributors)
for their contributions.

[Translate “My Tickets – Accessible Event Ticketing” into your language.](https://translate.wordpress.org/projects/wp-plugins/my-tickets)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/my-tickets/), check
out the [SVN repository](https://plugins.svn.wordpress.org/my-tickets/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/my-tickets/) by 
[RSS](https://plugins.trac.wordpress.org/log/my-tickets/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 2.1.2

 * Security: Protect against a race condition when adding tickets to shopping cart.
   Props @patchstack and Tarcísio Luchesi.
 * Change: Minor style change to prevent bootstrap CSS from breaking Add to Cart
   layout.
 * Change: replace `stripcslashes` with `wp_unslash`.

#### 2.1.1

 * Security: Payments shortcode Broken Access Control vulnerability. Props @patchstack
   and Daroo.
 * Security: Receipt views vulnerable to data exposure. Props @patchstack and Daroo
 * Change: Support bulk tickets view on etickets type.
 * Change: Improve review cart text when offline.
 * Bug fix: Wait to hide spinner until after query is completed.

#### 2.1.0

 * Add additional wrappers for formatting ticket titles in cart.
 * Update receipt and ticket default templates and styling.
 * Add custom CSS variables for receipt and ticket templates.
 * Remove unused CSS files.
 * Fix accessibility issues in tabpanel implementation.
 * Update settings page organization and structure.
 * Only render cart in user profile when populated.
 * Add notice in editor if editing a required page.
 * Hide ‘Trash’ option in posts list for required pages.
 * Prevent Yoast Duplicate Posts from duplicating ticket sales data when duplicating
   an event.
 * Update QR Code library to latest.
 * Change QR Code output from PNG to SVG.
 * Remove QR Code quiet zone.

#### 2.0.23

 * Security: Authenticated XSS Vulnerability in `remaining` shortcode. Props @Muhammad
   Yudha through Patchstack.

#### 2.0.22

 * Bug fix: “Only singular pages” option check as a boolean, but was actually a 
   string.
 * Bug fix: Mark dividers in mini cart with `aria-hidden="true"`.

#### 2.0.21

 * Bug fix: Fix undeclared variable notice for close date value.
 * Bug fix: `mt_format_if_datetime()` could return an invalid value.
 * Bug fix: Update screen reader text class CSS.
 * Change: Remove obsolete Chrome `beforeunload` hack.
 * Change: Update fonts in templates to use common system font stack.
 * Change: Support earlier exits in template constructor.

#### 2.0.20

 * Bug fix: Remove some self-contradictory logic.
 * Bug fix: Omit purchase path after purchase completion.
 * Bug fix: Handle ticket type closure when hiding ticket fields.
 * Change: Pass the payment ID into the `mt_response_messages` filter.
 * New filter: `mt_confirmed_transaction_before` to insert content before the transaction
   confirmation.

#### 2.0.19

 * Bug fix: Restore functionality to close ticket sales when a number of percentage
   of tickets have been sold.
 * Bug fix: Add to Cart form should not be displayed when the post is hidden due
   to post password protection.

#### 2.0.18

 * Bug fix: When tickets were moved to another event, they only appeared in reports
   if the same payment also purchased tickets on that event.
 * Bug fix: Sorting events by date in reports lists only used date, not time, causing
   some events to be omitted.
 * Bug fix: Public display dates for event-date subtypes not using `date_i18n`.
 * Bug fix: If purchaser changes name after initial payment creation, payment title
   not updated.
 * Change: Move payment status into payment date field.

#### 2.0.17

 * Security: Authenticated (Subscriber+) Privilege Escalation. Responsibly disclosed
   by Le Ngoc Anh through Wordfence.

#### 2.0.16

 * Bug fix: Inconsistent return behavior in `mt_save_data()`. Props https://github.
   com/ben-abrams
 * Bug fix: Only expire carts if a value exists for data age.
 * Bug fix: Don’t check for expired carts while in the admin.
 * Feature: Add settings for default report view and type.

#### 2.0.15

 * Bug fix: Returned before refreshing cache when saving data.
 * Bug fix: Omit a duplicate cache refresh triggered when deleting data.
 * Bug fix: Improve logic for checking cart integrity.
 * Bug fix: Use general admission rolling ticket availability when checking ticket
   availability.
 * Bug fix: Clearer heading text on Payment settings screen.
 * Bug fix: Clearer styling for field descriptions.
 * New: Function that verifies cart integrity to ensure all checks are identical.
 * Docs: Add docs for a handful of filters.
 * Feature: Settings to change the output of the event selector in reporting.
 * Performance: Don’t fetch ticket objects when counting tickets used for payments
   screen columns.

#### 2.0.14

 * Bug fix: Reverse auto-triggering of sold out state introduced in 2.0.13.

#### 2.0.13

 * Bug fix: Missing empty value in event selector for reports.
 * Bug fix: Set event ID when modifying selected event to send test emails.
 * Bug fix: Improved clarity in cart modified notifications.
 * Bug fix: Correct default value for `mt_show_form_when_soldout` to match documentation
   and intent.
 * Add: `available_tickets` template tag for My Calendar.
 * Docs: Improve code documentation for template tags added to My Calendar.

#### 2.0.12

 * Bug fix: Mismatched logic between admin and front-end for My Calendar events 
   when disabling tickets.
 * Update shipped .pot file.

#### 2.0.11

 * Bug fix: Event lookup when moving tickets queried posts instead of ticketed events.
 * Bug fix: Fix logic so ticket sales can be turned off.
 * Bug fix: Ensure expire_date is numeric before turning into a date.
 * Bug fix: Check for the loop before rendering the shopping cart.
 * Bug fix: Don’t modify the total number of tickets when moving tickets between
   events.
 * Change: Add general class for shopping cart field rows to make layout easier 
   to style.
 * Change: Sort reports event list alphabetically by event title.
 * Change: Expire unique ID cookies after the current cart life plus one week. The
   unique ID should always be longer than the cart.
 * Docs: Add filter documentation for a handful of additional filters.

#### 2.0.10

 * Security: Fixes a Broken Access Control in reporting. Props Mika & Patchstack.
 * Bug fix: Broken ID attribute in metabox ticket creation form.
 * Replace uses of `json_encode` with `wp_json_encode`.
 * Add file size and name verification before importing settings files.
 * Use WP_Filesystem to handle settings imports.

#### 2.0.9

 * Bug fix: Limit how long a cart expiration can be extended.
 * Filter: add `mt_virtual_inventory` filter to dynamically modify the virtual inventory.

#### 2.0.8

 * Bug fix: Add to cart forms checked submitted count incorrectly for making availability
   comparisons.
 * Improved JS event isolation for individual ticketing forms.

#### 2.0.7

 * Bug fix: Don’t send ticket type closed messages if they were closed well in the
   past.
 * Bug fix: Don’t attempt to display ticket fields if options array is incomplete.
 * Bug fix: Ensure returned close date is an integer.

#### 2.0.6

 * Remove textdomain loader (Obsolete since WP 4.6)
 * Bug fix: issue where hidden ticket creation fields still marked as required.
 * Bug fix: Update payment data when moving tickets to a different ticket type.
 * Bug fix: Incorrect variable reference in `mt_handle_expiration_status()`.
 * Bug fix: Ensure remaining count doesn’t display negative numbers.
 * Bug fix: Check virtual inventory when adding tickets to cart, to see if it has
   changed since page was loaded.
 * Bug fix: Remove `remove_filter` on add to cart form.
 * Change: Set default installation behavior to only display forms on singular views.

#### 2.0.5

 * Bug fix: Ticket creation form should not show in My Calendar Pro’s front-end 
   submissions form.
 * Change: `[ticket]` shortcode no longer requires the current page’s ID to render
   the form.
 * Feature: `[ticket_venue]` shortcode to render an event’s hcard on the page.
 * Feature: Attribute ‘location’ added to `[ticket]` shortcode with options ‘false’,‘
   before’, and ‘after’.

#### 2.0.4

 * Bug fix: Hiding remaining tickets failed because I passed the summary value instead
   of the individual event value.
 * Bug fix: Support using HTML in the offline gateway payment notes field. Props
   https://github.com/Martin-OHV
 * Accessibility: Save address action should use a button.
 * Docs: Added filter documentation for add to cart form filters.

#### 2.0.3

 * Bug fix: Individual event type email notifications not sent if entire event has
   closed.
 * Bug fix: Current ticket group not marked as selected in reports.
 * Bug fix: Custom field headers inserted one space too far to the left.
 * Add: filter `mt_field_paramters` to dynamically change custom field characteristics.
 * Add: filter `mt_after_remaining_text` to append text after the remaining tickets
   in cart.
 * Add: action `mt_custom_field_saved` executed after a custom field is saved to
   a payment.
 * Add: support for `report_callback` for custom fields for displaying in reports.
 * Docs: Document `mt_cart_custom_fields` filter.
 * Docs: Document `mt_show_in_cart_fields` filter.
 * Docs: Document `mt_purchase_completed` action.
 * Change: Pass additional arguments to `mt_show_in_cart_fields` filter.
 * Change: Pass payment ID into `mt_generate_cart_table()` when available.
 * Change: Remove filter on `the_content` after running to prevent duplication.

#### 2.0.2

 * Bug fix: Reports on tickets didn’t limit by ticket groups.
 * Bug fix: If label not retrieved from post meta, admin tickets render with incorrect
   time.
 * Bug fix: Don’t use the virtual inventory when sending admin notifications.
 * Bug fix: If a ticket type was not already in the sold cart, switching a ticket
   to that ticket type failed in the admin.
 * Bug fix: If ‘all’ passed as ticket type, tickets reports were empty.
 * Bug fix: Moving tickets between events was broken due to invalid falsey value
   check.
 * Bug fix: Don’t run ticket type expired action during cart processing, only check
   existing values.
 * Documentation: Add filter docs on closed and sold out admin email filters.

#### 2.0.1

 * Enhancement: Add email & purchaser name to purchase when moving a cart from public
   to admin.
 * Enhancement: Styling for ‘create admin cart’ link.
 * Enhancement: Move admin cart listing to top of create payment screen.
 * Change: Update readme for new version.
 * Change: Add field styling for inline report forms.
 * Change: Move daily cron to an hourly cron.
 * Document: `mt_confirmed_transaction` filter.
 * Document: `mt_successful_payment` action.
 * Document: `mt_link_title` filter.
 * Bug fix: Move price label out of remaining tickets filter.
 * Bug fix: Total incrementor displayed in wrong location in purchase list.
 * Bug fix: Apply cart styling in admin cart creation.
 * Bug fix: Send Playground preview link to page list rather than direct to edit,
   as page ID not dependable.
 * Bug fix: Add to cart was hidden if ticket count selector changed to `select` 
   input.
 * Bug fix: Reports of purchases with multiple ticket types only listed the last
   type purchased.
 * Bug fix: Function to update virtual inventory failed during cron because data
   about what to remove was not passed.
 * Bug fix: If mt_is_cart_expired() is executed with a cart ID and a logged-in user,
   the cart ID was ignored.
 * Bug fix: After sales are closed, only display the real inventory, not the virtual
   inventory.

#### 2.0.0

 * Feature: Set dates as ticket types with independent expirations.
 * Feature: Introduce virtual inventory option to remove tickets from inventory 
   when added to cart.
 * Feature: Add setting to control cart expiration time.
 * Feature: Add setting to extend expiration of cart when less than 60 minutes remaining.
 * Feature: Add ability to switch between different saved default ticket models 
   when creating new event.
 * Feature: Add ability to set general admission tickets with no expiration.
 * Feature: Add ability to set a specific custom expiration date for general admission
   tickets.
 * Feature: Bulk ticket check-in for groups.
 * Feature: Reports specific to ticket groups.
 * Feature: Individual date-based ticket groups send sold-out and sales expired 
   messages independently.
 * Feature: Add ability to move ticket between different ticket groups.
 * Feature: Improved templating and template filters for HTML email messages.
 * Change: Move ticket label index to post meta.
 * Change: Add custom buttons to increment ticket count due to incredibly small 
   browser input design.
 * Change: Revamp data storage model for public users.
 * Change: Secret keys displayed as password fields when filled.
 * Change: Match fields displayed in admin view reports & CSV downloads.
 * Design & visual changes.
 * Rename ticket types from ‘Discrete’ and ‘Continous’ to ‘Seating Sections’ and‘
   Audience Types’.
 * Wide variety of miscellaneous bug fixes that would be difficult to isolate.
 * Remove payments JS not used in core plugin.

#### 1.11.2

 * Change: Add cache-control headers to prevent browser caching of cart pages.
 * Bug fix: Fix minor misnamed variable reference.

#### 1.11.1

 * Bug fix: Misnamed variable in ticket templates displayed wrong expiration date
   for fixed date events.
 * Bug fix: Cart handling charges generated error in offline payments.

#### 1.11.0

 * Feature change: Extend General Admission tickets to set specific expiration dates.
 * Feature: Option to ignore cart-wide ticket handling fees for specific gateways.
 * Feature: Add autocomplete on move ticket feature.
 * Bug fix: No default padding on cart handling costs.
 * Bug fix: Incorrect permission check for ticket check-in in admin.
 * Bug fix: Setting the number format in the total paid field breaks values with
   thousands separators.
 * Bug fix: Counting error after moving tickets between events.
 * Change: Add payment gateway into purchase report download.
 * Change: Change default colors to use WordPress palette colors.
 * Change: Default event report changed to purchases & download instead of tickets&
   view.

#### 1.10.2

 * Bug fix: Stripslashes before sending payment confirmation to PayPal.
 * Improve: Prefix some invalid nonce errors.

#### 1.10.1

 * Bug fix: List of payment tickets sourced from event instead of payment.
 * Change: refactor payment storage of ticket IDs.

#### 1.10.0

 * Feature: UI to move tickets from one event to another on a payment.
 * Feature: Show tickets used in payments view.
 * Feature: Remove tickets from a payment.
 * Bug fix: Minor styling improvements for shopping cart.
 * Bug fix: Exit early if ticketing options do not exist.
 * Bug fix: Hide short cart when empty.
 * Bug fix: Correctly handle singular/plural values in quick cart.
 * Change: Add script debugging to break caches on styles and scripts.
 * Change: Style – wider price column.
 * Change: Expand information shown on verification views. Props @masonwolf.

#### Future

 * Improve options when there are multiple dates available for a specific event.
   Multiple ticket patterns w/separate pricing & availability options, etc.?
 * Add option to use radio buttons instead of checkboxes
 * Email QR code for e-tickets
 * Server-side validation of required fields in purchase process
 * Make admin-only ticketing options configurable in settings
 * Limit number of discount tickets per event for registered users
 * Add filter to pull user data into ticketing reports if user is registered.
 * Make address fields required & validated
 * BUG FIX: problem with passing address fields to notifications when shipping off
   but collect address on using PayPal (and other gateways?)
 * TODO: add ability to add or remove tickets from an existing payment
 * TODO: option to filter ticket purchasers by ticket type purchased (requires JS)

## Meta

 *  Version **2.1.2**
 *  Last updated **2 months ago**
 *  Active installations **700+**
 *  WordPress version ** 6.4 or higher **
 *  Tested up to **6.9.4**
 *  PHP version ** 7.4 or higher **
 *  Languages
 * [Dutch](https://nl.wordpress.org/plugins/my-tickets/), [English (US)](https://wordpress.org/plugins/my-tickets/),
   [French (Canada)](https://fr-ca.wordpress.org/plugins/my-tickets/), [French (France)](https://fr.wordpress.org/plugins/my-tickets/),
   [German](https://de.wordpress.org/plugins/my-tickets/), [Spanish (Chile)](https://cl.wordpress.org/plugins/my-tickets/),
   and [Spanish (Spain)](https://es.wordpress.org/plugins/my-tickets/).
 *  [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/my-tickets)
 * Tags
 * [accessibility](https://bcc.wordpress.org/plugins/tags/accessibility/)[Event Tickets](https://bcc.wordpress.org/plugins/tags/event-tickets/)
   [registration](https://bcc.wordpress.org/plugins/tags/registration/)[reservations](https://bcc.wordpress.org/plugins/tags/reservations/)
   [ticket sales](https://bcc.wordpress.org/plugins/tags/ticket-sales/)
 *  [Advanced View](https://bcc.wordpress.org/plugins/my-tickets/advanced/)

## Ratings

 4.9 out of 5 stars.

 *  [  26 5-star reviews     ](https://wordpress.org/support/plugin/my-tickets/reviews/?filter=5)
 *  [  0 4-star reviews     ](https://wordpress.org/support/plugin/my-tickets/reviews/?filter=4)
 *  [  0 3-star reviews     ](https://wordpress.org/support/plugin/my-tickets/reviews/?filter=3)
 *  [  0 2-star reviews     ](https://wordpress.org/support/plugin/my-tickets/reviews/?filter=2)
 *  [  1 1-star review     ](https://wordpress.org/support/plugin/my-tickets/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/my-tickets/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/my-tickets/reviews/)

## Contributors

 *   [ Joe Dolson ](https://profiles.wordpress.org/joedolson/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/my-tickets/)

## Donate

Would you like to support the advancement of this plugin?

 [ Donate to this plugin ](https://www.joedolson.com/donate/)