Event Tickets With Ticket Scanner Update – 20260511

= 3.0.8 – 2026-05-11 =

• Fix: On variable products, the parent’s “Request a value per ticket”, “…mandatory” and the matching name-per-ticket checkboxes silently turned themselves back ON every time anything on the product was saved (e.g. flipping a variation’s stock status). Root cause: each variation row submits an override <select name="<key>[<i>]"> under the same root name as the parent’s checkbox/input, so on a variable-product save $_POST[<key>] arrived as an array. The save handler treated “key is present in POST” as “checkbox is checked” and overwrote the parent meta with yes — which is also why the cart kept asking customers to fill in a value field even when, in the admin, the boxes looked unchecked. The handler now ignores array values for parent-level fields (request_name/value_per_ticket(_mandatory|_label|_def), ticket_start/end_date/time, ticket_amount_per_item, and Premium’s expiration_days). After updating, simply uncheck the affected boxes once and they will stay unchecked. No data migration is required.
• Fix: Fatal TypeError when adding products to cart from a wishlist (or any 3rd-party plugin that calls WC_Cart::add_to_cart() without supplying $variation as an array). The internal handler used a strict array type-hint and aborted the whole cart operation — it now accepts any input and normalizes defensively. Affects sites running WooCommerce Wishlists.
• Fix: Ticket configuration fields (date, dropdown, name-per-ticket, etc.) no longer appear on every variation of every variable product in the admin. They are now only rendered when the parent product is explicitly marked as a ticket — same UX rule that already applies to simple products. Catalogs with thousands of non-ticket variable products no longer have to opt out per variation.
• Fix: Cart and checkout no longer render ticket-specific input fields (name-per-ticket, value-per-ticket, daychooser, seat info) for products whose parent is not (or no longer) a ticket. The is_ticket flag on the parent product is now the single source of truth — stale variation/product meta from a previous configuration is ignored. Validation at checkout follows the same rule and no longer blocks orders for non-ticket products with leftover meta. Purchase-restriction codes are unaffected and continue to work on any product type.
• Fix: Cart and checkout input fields for the name-per-ticket, value-per-ticket and purchase-restriction features now use standard WooCommerce form-row markup (<p class="form-row form-row-wide"><label>…</label><input class="input-text" />) instead of a custom <small>-label wrapper. This lets the active theme’s CSS apply normally so the fields look consistent with the rest of the cart/checkout form.

= PREMIUM – 1.6.9 – 2026-05-11 =

• Fix: On variable products, the parent’s Days till the ticket expires field silently reset to 1 whenever any save touched a variation (e.g. a stock change). Root cause is the same variation-array collision fixed in basic 3.0.8: each variation row submits saso_eventtickets_expiration_days[<i>], so on the parent save $_POST contained an array under the same root name and intval([...]) returned 1. The Premium save handler now ignores arrays for this key. Pair with basic 3.0.8 (release together).

Want to be listed as an implementation partner?

We want to add a page dedicated to implementation partner and WordPress developer/designer. You can get listed on this page, if you like. It is free and we will forward users that need help with implementing special behavior to this page. So you can get new customers and support the plugin 🙂

Please send an email to [email protected]. We need your name/company name, website, what you are (developer, designer, etc), with what you can help regarding the plugins (serial and/or event) – the idea is that people with issues, like designing a ticket template with twig or so, can get help from you. If you have default prices (hour, project or so) then we can add them also to the page. I will have to evaluate a bit, so that the quality can be checked. We cannot ensure your listing, if it does not match with the needs of our customer and the relevance to my plugins.

In case you want to revert your basic plugin version:

You can download the old basic plugin from the advance tab on the plugin website. Install it manually via the plugin area.

https://plugins.trac.wordpress.org/browser/event-tickets-with-ticket-scanner/tags

Download the version you like and rename the folder to event-tickets-with-ticket-scanner.
Then zip the folder.
Upload the zip file to your WordPress installation using the plugin area.