Event Tickets with Ticket Scanner
| 开发者 |
Saso Nikolov
sasonikolov |
|---|---|
| 更新时间 | 2026年10月28日 18:58 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
标签
下载
1.4.6
1.1.5
1.3.15
1.2.5
1.2.6
1.4.8
2.2.6
1.3.6
1.5.5
1.3.0
1.1.0
1.3.13
2.6.10
1.5.2
1.5.3
1.0.11
1.3.5
1.3.7
1.5.8
1.4.5
1.3.2
1.4.0
1.3.4
1.3.8
1.5.7
1.5.9
2.1.2
2.4.3
1.0.12
1.2.7
1.2.8
1.2.9
1.3.11
1.3.12
1.3.9
2.6.3
1.0.0
1.0.1
2.2.5
1.1.10
1.1.9
1.2.0
1.5.6
2.5.6
2.5.7
1.4.2
3.0.8
3.2.9
1.0.2
1.0.4
1.0.5
1.4.10
1.0.3
1.0.6
1.4.9
1.0.7
1.0.8
1.0.10
1.0.9
1.1.2
1.1.4
1.1.3
1.1.6
1.1.7
1.1.8
1.2.1
1.2.2
1.2.3
1.2.4
2.0.4
2.5.3
2.5.5
1.2.10
1.2.11
2.8.5
1.3.1
1.3.3
1.4.1
1.3.10
1.3.14
1.4.3
1.4.4
1.4.11
1.4.7
1.5.1
2.2.4
2.3.3
2.3.8
1.4.12
1.5.4
2.1.1
2.1.9
2.1.5
2.6.11
2.1.7
2.0.6
2.6.5
2.7.2
2.0.3
2.6.1
2.6.4
2.1.11
2.2.7
2.2.8
2.3.0
2.1.10
2.1.3
2.1.4
2.2.3
2.3.7
2.1.0
2.2.0
2.2.1
2.2.2
2.3.1
2.3.10
2.3.9
2.0.7
2.3.6
2.5.1
2.5.4
2.1.6
2.3.11
2.3.2
2.4.0
1.5.10
2.3.12
2.3.5
2.4.1
2.0.1
2.0.2
2.0.5
2.1.8
2.4.4
2.5.2
2.5.0
2.7.10
2.6.6
2.7.1
2.7.7
2.6.7
2.6.8
2.6.9
2.6.2
2.9.8
2.9.9
3.1.2
3.2.10
3.2.5
3.0.5
2.7.6
2.9.2
3.1.10
3.1.11
2.7.3
2.7.8
2.8.3
2.8.4
2.8.6
3.0.9
2.7.5
3.1.0
3.1.1
2.9.6
3.0.0
2.8.1
2.8.10
2.8.8
3.1.3
2.7.0
2.7.9
2.8.0
2.8.7
2.9.0
2.9.5
3.1.4
3.1.5
3.1.6
2.8.9
2.9.7
3.0.4
3.1.7
3.1.8
3.1.9
2.9.3
3.0.2
3.0.3
3.1.13
3.2.0
3.2.1
2.8.2
3.0.1
3.2.4
3.2.7
3.2.8
3.0.7
3.1.14
3.2.2
2.6.0
2.7.4
2.9.4
3.0.6
3.1.12
3.2.3
3.2.6
详情介绍:
Run your entire ticketing workflow inside WordPress. No platform service fees, no per-ticket commissions — you only pay your payment processor (Stripe, PayPal, etc.).
Event Tickets with Ticket Scanner turns your events into scannable tickets — complete with QR code, downloadable PDF, and a built-in mobile ticket scanner for your team at the door.
Unlike ticketing platforms that charge service fees on paid tickets, this plugin adds no per-ticket commission — you keep your ticket revenue (minus your payment processor's standard fee). Unlike other WordPress plugins, you get a visual seating plan designer and a ticket PDF designer included — not as expensive add-ons.
https://youtu.be/uWSdKdOyn70
Active on 1,000+ WordPress sites — from small community events to large concert venues.
Who is this for?
- Selling at the door — evening box office (POS)? The built-in Kasse is a complete point of sale: sell tickets, memberships, day passes, ride tickets and entries at the counter, with ticket types, automatic totals and a cash change calculator. No event, no online shop required
- Concert & festival organizers — sell general admission or assigned seats with interactive seat selection
- Theaters & venues — design your seating layout with drag & drop, let customers pick their seats
- Sports events & arenas — handle high scan volumes with rapid-scan queueing and team scanner access
- Conferences & congresses — give attendees a private companion portal with programme, speakers, downloads and time-controlled access, opened straight from the ticket (see "Congress & Attendee Portal" below)
- Single events with an info app — any event, not just big congresses: build a mobile info page (schedule, speaker info, downloads, support pages) your visitors open with their ticket — no separate app to install
- Clubs, spas, gyms & theme parks — sell multi-entry passes, family tickets, or memberships with expiration
- Community events & fundraisers — get started in minutes with the free version (up to 50 tickets)
- Install the plugin and create a ticket list under "Event Tickets"
- Enable "Ticket Sales" on any WooCommerce product
- Customers receive a unique QR code ticket — scan and redeem at the entrance
- Drag & drop seats, shapes, labels, and text onto your canvas
- Upload venue floor plans as background images
- Rotate, duplicate, and bulk-edit elements
- Color-code seat categories and pricing tiers
- Customers see a real-time interactive seat map during checkout
- Seats are automatically blocked during checkout and released on cancel/refund
- Add your logo, custom colors, header and background images
- Position QR codes exactly where you want them
- Create event badges for staff and VIP passes
- Multi-page PDF support with attached documents
- Full bleed mode for edge-to-edge designs
- Scan QR codes with your phone camera — works on iOS and Android
- Install as PWA — add to home screen for instant launch without browser chrome
- Fullscreen mode — immersive scanning with a single tap
- Haptic feedback — vibration confirms valid/invalid tickets instantly
- Grant team members scanner access via Auth Tokens (no WordPress login needed)
- See ticket details, seat position, and venue map instantly after scan
- Voice output confirms valid/invalid tickets for fast processing
- Protection against fake tickets, double redemption, and brute-force attempts
- Supports hardware barcode scanners for high-traffic entrances
- Customizable theme color to match your brand
- Vollstart Wallet at wallet.vollstart.com — a Progressive Web App that works on iOS, Android, and desktop
- Tickets are added with one click from the ticket page or order email
- QR code always available — even offline
- Privacy first — ticket data flows directly from your shop to the customer's browser. Vollstart never receives or stores any data
- Learn more about security & privacy
- Organize content into pages — a start page plus as many pages as you need (Speakers, Programme, Downloads, Sponsors …), with a sidebar on desktop and a hamburger menu on mobile
- Rich section types — formatted text, a day-by-day programme schedule, downloadable files, link lists, image galleries, single images, and embedded videos (paste a YouTube/Vimeo link or upload your own)
- Password-protect individual sections for VIP or speaker-only content
- Fast by design — the start page loads instantly and other pages are fetched on demand, so even congresses with dozens of speakers stay snappy
- Installable & offline-friendly — the portal ships as a mini Progressive Web App
- Time-controlled access — open the portal a set number of hours before the event and keep it available for a chosen number of days afterwards
- Recurring events — duplicate a congress as a "new edition" in one click
- Single entry — classic one-time event ticket
- Multi-entry passes — allow multiple scans (configurable limit)
- Family tickets — generate multiple tickets per order item
- Memberships & season passes — set expiration dates
- Day chooser tickets — let customers pick their event date at checkout
- Purchase allowance codes — require a valid ticket or access code before a product can be bought. Use it for presale and access codes, or to require a ticket from an earlier event (for example a group-stage ticket in order to buy the final). Per product you decide whether a code unlocks one purchase or several
- Works with product variants (e.g., VIP vs. General Admission)
- Tickets auto-generate on order completion
- Refunded orders automatically recover and recycle ticket numbers
- Compatible with WooCommerce Subscriptions
- Works with WooCommerce PDF Invoices & Packing Slips
- WPML compatible for multilingual stores
- ✅ Ticket generation with QR codes (up to 50 tickets, 5 ticket lists)
- ✅ PDF ticket download (via link in email)
- ✅ Built-in ticket scanner
- ✅ Interactive seating plan designer (1 plan, up to 20 seats)
- ✅ Seat selection at checkout
- ✅ Multi-entry and family tickets
- ✅ Day chooser for date-based events
- ✅ Congress / attendee portal (pages, programme, downloads, media, password-protected sections)
- ✅ Purchase allowance codes (presale/access codes, or require a ticket from an earlier event)
- ✅ Webhooks for third-party integrations
- 🔓 PDF ticket as email attachment (not just a link)
- 🔓 Team scanner access via Auth Tokens
- 🔓 Calendar invites (ICS files) in emails
- 🔓 Custom flyers and multi-page PDFs
- 🔓 CVV security check on tickets
- 🔓 Brute-force IP blocking
- 🔓 Unlimited tickets (removes the 50-ticket free limit)
- 🔓 Advanced shortcodes for ticket display and validation
安装:
Requirements
- WordPress 5.0 or greater
- WooCommerce 6.0 or greater
- PHP 8.1 or greater (PHP 8.4 compatible)
- PHP extensions: php-curl, php-imagick
- Go to Plugins → Add New in your WordPress admin
- Search for "Event Tickets with Ticket Scanner"
- Click Install Now, then Activate
- Go to Event Tickets in your admin menu and create your first ticket list
- Edit any WooCommerce product → open the Event Tickets tab → enable ticket sales
屏幕截图:
常见问题:
Do I need any other plugins?
No. Everything is included — no additional ticketing add-ons required. The built-in checkout (premium) handles payments and orders on its own.
Does this work without WooCommerce?
Yes. The Kasse (direct sales) and the online shop (premium) sell tickets with their own checkout — no WooCommerce needed. And if you already run a WooCommerce store, the plugin supports it as fully as ever.
Can my team scan tickets without a WordPress account?
Yes! Premium includes Auth Tokens that give your door staff scanner access via a simple URL — no login required.
Does the scanner work offline?
By default the scanner validates live against your site (it is browser-based and built for speed: rapid scans are queued automatically, so nothing gets lost while a result is still on screen, and the app is an installable PWA). Premium adds true offline scanning: enable it on the scanner's auth token, choose which ticket lists get preloaded, and your door team keeps scanning when the venue network drops — scans are validated locally, queued, and synced automatically once the connection returns, with conflict reports when two scanners hit the same ticket.
Can customers choose their own seats?
Yes. Design your venue layout with the drag & drop seating designer, and customers will see an interactive seat map during checkout where they can pick available seats.
What ticket types can I create?
Single entry, multi-entry passes, family tickets (multiple tickets per purchase), memberships with expiration dates, and day-chooser tickets where customers pick their event date.
How are tickets delivered to customers?
In the free version, the order confirmation email includes a link to download the ticket PDF and view the QR code. Premium allows attaching the PDF directly to the email and adding calendar invites (ICS).
What happens when an order is refunded?
The ticket is automatically deactivated, the assigned seat is released, and the ticket number is recovered for reuse.
Is the plugin compatible with WPML?
Yes. WPML is supported for multilingual ticket sales. The plugin also ships translations for German, Spanish, French, Italian, Hungarian, Japanese, Dutch, Portuguese, and Chinese.
What if I exceed the free ticket limit?
The free version supports up to 50 tickets. If you reach the limit, the plugin shows a notice in the admin area (your customers are never blocked from purchasing). Premium removes the limit entirely.
Can I use my own QR code or barcode scanner hardware?
Yes. The built-in scanner page accepts input from hardware barcode scanners in addition to camera-based QR scanning.
How do I prevent ticket fraud?
Every ticket number is unique. The scanner detects duplicate redemption attempts. Premium adds CVV verification and brute-force IP blocking for additional security.
What is the congress / attendee portal?
It's a private event portal you can attach to a ticket product — organized into pages (start page, speakers, programme, downloads, sponsors, etc.) with text, schedules, files, image galleries and embedded videos. Ticket holders open it directly via their ticket, no separate account needed. You can password-protect individual sections, control when the portal opens and how long it stays available, and the page works offline as a mini PWA. It's included in the free version; build it under the Congresses menu and assign it in the product's Event Tickets tab.
更新日志:
3.2.10 - 2026-10-28
- Fix: every WooCommerce checkout failed with a fatal error since 3.2.9 (class-gclid.php) - the Google Ads click tracking read the checkout data array as a session object. Checkouts work again immediately after updating.
- Kasse: touch-friendly minus/plus steppers around each ticket product quantity field.
- Kasse: the change calculator now works like a real calculator — quick buttons add onto the current amount, typed digits append to it, and a backspace key (⌫) removes the last entered digit.
- Kasse: change calculator with keypad and additive quick buttons (5/10/20/50/100) plus a big live change display — payment method and amounts are tracked in the order meta JSON.
- Kasse: ticket products are prefetched once per visit instead of one request per dialog — noticeably faster product display.
- Security: offline scanner sync event IDs are now passed as prepared SQL parameters (hardens the sync endpoint against SQL injection via crafted event payloads). Security: admin table searches (codes, error logs, options history) escape the decoded search term before it enters the query — URL-encoded quotes can no longer break out of the search filter. Security: error messages that echo back scanned or entered ticket codes are HTML-escaped at the source, in the legacy ticket/scanner fallbacks, and are rendered as plain text by the scanner and the public validation widget (protects against malicious QR codes). Security: sensitive admin actions (option changes, code deletion, CSV exports, auth-token management) now require the manage_options capability — plugin admin-area access alone is no longer sufficient. Security: releasing a fresh seat reservation requires the matching ownership token issued when the seat was blocked.* Security: visitor-controlled proxy headers (X-Forwarded-For, Client-IP) are no longer trusted for rate limits and IP blocks. IP-based limits now use the server-side address; sites behind a CDN/reverse proxy can enable the new option "Trust proxy IP headers (X-Forwarded-For)" (trustProxyIpHeaders) to restore proxy resolution.
- Security: the wallet ticket lookup endpoint is now rate-limited per IP to block ticket-ID enumeration attempts.
- Offline ticket scanning (premium): a master option enables the feature; per auth token you choose which ticket lists that scanner preloads. Scanners opened without a token are asked at start whether to preload tickets — all from today onwards, or today only (ask mode, choice remembered for the session, changeable any time). Scans keep working without a connection — validated locally, queued, and synced automatically when the network returns (online event, periodic retry, sync button). Safe with several scanners: the server replays every queued scan through the regular redeem path, retries are idempotent per scan id, and conflicts are reported. With the option off, everything behaves exactly as before.
- Unpaid online-shop orders no longer block contingents: draft orders older than 48 hours (filterable) are cancelled automatically once a day and release their reserved tickets.
- Wallet: tickets sold through the Kasse and the built-in online shop can now be saved into the Vollstart Wallet app — the wallet previously accepted WooCommerce-paid tickets only.
- Google Ads measurement: visits that arrive with a ?gclid= click parameter keep it through the session and store it on the order at checkout (private order meta), so advertising conversions can be measured per order.
- New lists open directly in the edit dialog after saving — ticket products with prices, limits and shop settings are visible immediately instead of showing up only when editing an existing list.
- Ticket types (Kasse and online shop): new optional eligibility-proof switch for discounted types — the ticket scanner asks at the entrance to check the proof (ID, student or retiree pass) before it redeems the ticket.
- Events without WooCommerce: date, times and location now live on the event (ticket list) — tickets sold via Kasse and the online shop print them on the PDF, together with the ticket type each ticket was sold as.
- Admin: when the security session (nonce) expires after a long idle time, a single dialog explains it and reloads the page via OK — instead of an error message on every action.
- Ticket scanner: new per-element large display options — guest name from the order (WooCommerce or the plugin's own checkout), ticket values and ticket type can each be shown in big, clearly visible letters right after validation.
- Ticket scanner, "Redeem Complete Order": the batch now cross-checks the order's tickets in the database — tickets missing from the order item code list (for example after partial refunds) are redeemed too, and the scan answer reports how many were reconciled.
- Own checkout (Kasse and online shop): the buyer's name is now frozen onto every ticket at sale time, so the scanner treats tickets sold without WooCommerce exactly like WooCommerce tickets.
- Own checkout: optional per-type ticket contingent — a maximum sellable quantity per ticket type. The Kasse and the online shop stop automatically at the limit and show how many are already sold; open orders count as reserved.
- Ticket lists: optional overall capacity — set a total maximum on the list and all ticket types share one pool. Mixed sales (regular + discounted) can no longer oversell the venue's seats.
- Ticket lists: new "Show in shop catalog" switch — every list sells in the central ticket shop catalog by default; turn it off per list when an event should not be offered there.
- Fix: When two orders are paid at the exact same moment, a ticket could end up linked to the other order. Ticket generation now locks per order and the ticket data writes are protected against such parallel-payment mix-ups.
- Fix: PDF library compatibility reworked — plugins that bundle their own TCPDF/FPDF (e.g. shipping-label plugins) no longer crash when both libraries load in the same request; the legacy class names are now provided lazily on reference instead of being occupied at load time.
- New: Internal order API for the premium online shop — public sales pages sell ticket products without WooCommerce (premium feature, 1.9.0).
- New: Ticket products (ticket types) with prices — sell different ticket types directly at the Kasse (direct sales) with automatic totals and a cash change calculator, no WooCommerce needed.
- New: Manage ticket products per event in the list editor — name, price, currency and active state; the Kasse switches to them automatically once one exists.
- Fix: The calendar file (ICS) of a variable ticket product now uses the event date of the purchased variation. When event dates were only set on the variations (parent product empty, \"date valid for all variants\" off), the ICS file carried today's date instead of the variation's event date.
- New: The German translation is complete again — 174 previously untranslated strings are now in German, including every new Kasse (direct sales) and ticket scanner text of this version.
- New: Optional auto refresh for the direct sales (Kasse) table — a checkbox in the toolbar reloads the table every 30 seconds, so parallel kassen always see each other's sales. The setting is remembered per browser.
- Fix: Opening the direct sales (Kasse) view a second time fired the orders request twice — the list cache rendered immediately and again after its background refresh. The refresh now updates the cache silently.
- New: A refresh button above the direct sales (Kasse) table reloads the current rows without losing your search, filters or page position — useful when several kassen sell in parallel.
- Fix: The direct sales (Kasse) table in the admin showed no rows while the pager counted many pages — the server response carried a success envelope the table could not read.
- Fix: The ticket list description on the Kasse tiles is now rendered as formatted text — HTML tags are executed (safely sanitized server-side) and stray backslashes before quotes are gone, including for lists saved before this update.
- New: Scanner option "Redeem button at the top" (default active) — shows a redeem button at the top of the redeemed view, right below the ticket information, so staff can read the ticket details and redeem the next admission without scrolling. Can be toggled per device in the scanner options; a new global preset (Events → Settings → Ticket scanner) controls the default for all devices.
- Fix: Scanning the same group ticket again (one QR code, multiple admissions) now reliably redeems the next admission. After a previous fix removed a crash, an internal processing lock could stay engaged, so the second scan of the same code stalled until the page was reloaded. The lock is now released before the re-scan is queued, making back-to-back scans of one group ticket work without reloading. The scanner's timing checks also no longer assume the full ticket data set — a reduced server response used to stop the second scan with a script error.
- Fix: PDF tickets downloaded from the WooCommerce order admin are now saved with the suggested filename (e.g.
tickets_702394.pdf) on every browser, not just most. Some browser-security-plugin combinations used to ignore the inline download and fall back to the request URL as the filename (e.g.admin-ajax.php.pdf). The PDF now carries an explicit attachment header that the browser must honor.
- Fix: PDF library isolation now also keeps the global class aliases for TCPDF and FPDF, so plugins that ship their own PDF subclasses (shipping label generators, invoicing, etc.) keep working without changes on their side. After 3.2.5 introduced the underlying isolation, the legacy class names are restored alongside it. Shops without such plugins see no change.
- Tweak: The "Show seating plan link in shop overview" option has moved to the Seating Plan settings section, where it belongs next to the other seat-map behaviour switches. Setting value is preserved.
- Tweak: The "Congress" portal has been renamed to "Event Guide" across the admin area, options headings, and the public ticket-link view label. Internal option keys, database columns and REST namespaces stay the same for backward compatibility.
- Fix: Resolved a scanner crash on servers returning partial ticket metadata. The scanner now safely handles responses where the ticket's redemption metadata is missing — instead of stopping with an error, it falls back to the operator-driven redeem path. No action needed for previously-working tickets; the behaviour is unchanged for them.
- Fix: Ticket scanner no longer traps multi-redeem tickets in the self-redeem echo. Scanning a group ticket (one QR for N guests) for guest #2..N now flows through to the next redeem instead of locking on "already redeemed by this scanner a moment ago" until a manual browser refresh. Single-redeem tickets still show the calm echo — that protection is unchanged.
- Fix: PDF library isolation — the bundled TCPDF classes and constants are now prefixed (SASOET_TCPDF*) and the loader no longer falls back to system-wide TCPDF installations. Fixes fatal "Cannot redeclare class TCPDF_FONT_DATA" crashes when another plugin also bundles TCPDF (e.g. DPD Connect shipping labels) — whoever loads first, both plugins keep working.
- New: Deleting a ticket list that still contains tickets is now blocked by default. The list delete dialog has a new checkbox "Block if list still contains tickets" (checked by default) — unchecking it allows the delete anyway. Prevents accidentally orphaning tickets whose QR code, PDF and scanner checks depend on the list.
- New: You decide how long the ticket scanner ignores a repeated scan of the same ticket — set the waiting time in seconds in the global options (default 7 seconds), so the camera never picks up the same ticket twice by accident.
- New: The seat map opens as a fullscreen overlay on every device. The confirm buttons sit in a footer that stays visible at the bottom edge, so they can no longer be cut off on small phone displays. Close anytime with the large X in the top right corner.
- New: Zoom buttons beside the seat map. Stacked vertically in a narrow bar on the right, they never cover the map. Zooming is useful on phones to pick the right seat on large plans.
- New: Global option "Confirm seat selection automatically once complete" (default off) — the seat map confirms as soon as the customer has picked all seats, one less tap on mobile.
- Fix: Redeem operations are now protected against parallel scanner writes (optimistic locking). When two devices redeem or edit the same ticket code at the same moment, the second write is detected, re-read and safely retried instead of silently overwriting the first one's redeem entry.
- New: Admin notice on the product edit screen when the product's seating plan has seats but was never published — until now the product page simply showed no seat selection, with no hint why. The notice links straight to the plan for publishing.
- Fix: On MariaDB servers without strict mode, a never-published seating plan could be treated as published ("0000-00-00" zero-date) — the product page then rendered an empty plan instead of none. Zero dates are now handled correctly.
- Fix: Publishing a seating plan did not sync the seats table — after deleting and re-creating seats in the designer, the shop showed only a fraction of the seats (or none) while the designer showed them all. Publish now re-activates the plan's seats so the shop matches the designer.
- Fix: The seat statistics ("total seats / available") counted inactive and deleted seats, reporting seats as available that the shop could not sell. Counts now match what the seat selector actually offers.
- Fix: Seating-plan JSON exports are timestamped down to the second in the download filename so multiple exports on the same day do not overwrite each other.
- Fix: The seat-map selector endpoint could still show deleted decorations (rect9) because getPlanForProductFrontend merged with array_replace_recursive directly instead of using the helper that replaces element lists. The selector now renders exactly the published decorations.
- Fix: The shop's seat map could show deleted decorations and seats from an old layout version (e.g. overlapping "ghost" seats) although the designer showed the current plan — the page merged the plan's legacy meta column into the current published version, and list-merging resurrects deleted elements. The seat map now renders exactly the published version.
- Fix: Seat maps stayed empty on MySQL 8 servers with strict SQL mode — comparing the (empty) event date against a DATE column aborted the seat query with "Incorrect DATE value" while the shop showed no error. Empty and zero dates are now normalized before every seat query. The support info block additionally shows the server's SQL mode.
- New: "Import Plan (JSON)" next to "Add Seating Plan" — restores a plan export in one click. Two clearly explained modes: create a new plan (gets "(imported)" added, stays unpublished for review) or replace the draft of an existing plan (published version stays live until you publish; sold tickets are never touched). Seat dates are now stored and compared as integer timestamps with self-healing backfill of existing rows — MySQL 8 strict mode can no longer break seat maps.
- New: The seating plan designer and the seat list show an approximate element limit ("n / ~2000") — plans are stored as JSON and saving extremely large plans can fail silently depending on the server configuration. The counter turns red with a warning when the approximate maximum is reached.
- New: Seating plan designer: "Navigator" — a collapsible element list between the properties panel and the save buttons. Every seat, decoration, line and label is listed by name; click a row to select the element (works for overlapping elements that are hard to click on the canvas), hover to highlight it on the canvas. Essential for debugging customer plans.
- Fix: Deleted elements in the seating plan designer came back after saving and reopening the plan — the server merged the new element list into the stored one instead of replacing it, resurrecting every deleted decoration, line and label. This made plans impossible to clean up (the root cause behind seats never matching the designer). Lists are now replaced on save.
- Fix: Publishing a seating plan raced the draft upload — the publish request fired on a fixed timer instead of waiting for the save to finish, so on slower connections the shop was published with a stale draft while the editor showed "published successfully". Publish now waits for the save roundtrip and aborts with a clear error if saving fails.
- New: "Export Plan (JSON)" button in the seating plan seat view — downloads the complete plan (canvas, decorations, draft, published version and all seats) without any customer data, so a plan can be shared with support and re-created 1:1 for debugging.
- Tweak: The "Starter plugin is installed" warning now recognizes when the full Premium plugin is already installed next to the Starter and tells you to simply delete the Starter, instead of suggesting a Premium upload you do not need.
- Fix: With "Reserve seat only when adding to cart" enabled, the reservation was stored under wrong identifiers — the seat was not reliably blocked for other customers until the order was completed. Reservations created by this option now block the seat correctly.
- Fix: On block themes (like Twenty Twenty-Four) the public ticket page fell back to a deprecated WordPress legacy template and printed a deprecation notice — the page now renders a clean minimal shell there.
- New: The print preview in the Kasse opens the ticket as a PDF.
- Fix: Selling a ticket crashed with a server error when the ticket list used a code format — the format reached the code generator in the wrong shape; the generator now handles both shapes.
- New: The Kasse area shows one button per ticket list — a single click opens the sale popup with the list preselected (switchable inside the popup), amount, payment note and customer name.
- New: Sell tickets directly at the counter — the new "Kasse" area issues tickets from a ticket list without a shop order, attaches an internal sale number to every ticket and confirms payment with one click. Sales can be cancelled or partially refunded; cancelled tickets are freed for reuse. Print preview opens each ticket in the browser. The sale confirmation is checked at the scanner: a ticket whose direct sale was not confirmed yet does not redeem.
- New: Kasse is now switchable (default on) — turn the whole Kasse tab off as a safety stop or for handheld-only shops.
- New: The Kasse ticket-list overview is switchable (default on) — disable to open the sale popup directly on touch screens.
- New: The Kasse orders table now uses server-side DataTable processing (search / paging / sorting), status pills, and per-row Confirm / Cancel / Refund / Partial refund / Print tickets actions. Filtering and ordering are handled on the server.
- New: Filter the ticket list by scanner account — new search filter "AUTHTOKEN:" shows all tickets redeemed by one ticket scanner (enter the id shown in the scanner details), so you can review each entrance team member's activity without opening every ticket.
- New: The scanner makes a successful read unmistakable — the camera area lights up with a green frame (like card payment terminals) and a clear "code read, waiting for server" message the moment a QR code is recognized, followed by a short deliberate pause before the next scan is processed. Queued scans of group members are never lost and keep their order.
- Fix: The ticket scanner silently dropped scans that arrived while the previous ticket was still loading (slow Wi-Fi, fast consecutive scanning of groups) — those guests were never redeemed in the dashboard. Scans are now queued and processed one after another, with a short on-screen note.
- Fix: Re-scanning a ticket that this scanner redeemed moments ago showed a red "ticket already used" error — confusing operators at the entrance. The scanner now recognizes its own successful redeems and shows a calm green confirmation instead.
- Fix: The same seat could be sold twice — a second order (or a double add-to-cart with the same seat) confirmed a seat that already belonged to another order, creating two paid tickets for one seat while the seat map only showed one sale. A seat already confirmed for another order is now refused, and a selection containing the same seat more than once is rejected at add-to-cart with a clear message.
- Fix: When an order was refunded or cancelled, the freed tickets kept a user registration from the previous buyer — the old owner stayed visible on the ticket and could interfere with its next use. Registrations are now cleared together with the other order information, and when a ticket is reused for a new purchase, any leftover registration or usage information is swept automatically.
- New: Tickets without WooCommerce — the big decoupling step. Ticket lists, ticket numbers, PDF tickets and the ticket scanner now work without a WooCommerce order behind them, for printed cards you hand out yourself. (Details follow with the release.)
- New: The PDF path for tickets without an order — the single ticket PDF, the ticket page and the bulk "one PDF" print sheet now render order-less tickets instead of failing with an order error. The ticket shows its own number, its list, the QR code and the redemption state; everything that normally comes from the order (customer, purchase dates) stays empty. With the "allow tickets without order" switch off, everything behaves exactly as before.
- Fix: Order-related errors (#7001/#7002/#8010/#8013/#8020/#8021) no longer appear for tickets that are deliberately allowed to have no order.
- New: The setup wizard now asks whether you will sell or hand out tickets directly, without a WooCommerce order — at the door, by invoice or as printed cards — and explains what the switch does. The option's description in the settings was extended the same way.
- New: The admin area formerly known as "Congresses" is now the "Event App" — the companion page your visitors open with their ticket (programme, speaker info, downloads, support pages; for a congress just as much as for a single event). Each app row has an "Open example" button that opens the visitor view in a new tab, using one of the app's real tickets. The button appears once a ticket exists.
- Tweak: The support info block now reads "Tested up to", "Requires at least" and "Requires PHP" live from readme.txt instead of carrying hardcoded values that lagged behind (it showed 6.9 while the readme said 7.1).
- New: The setup wizard has a fifth use case, "Direct sales — no WooCommerce" — for tickets you sell at the door, by invoice or as printed cards. It switches the without-order path on and carries scanner defaults instead of order-processing options. When WooCommerce is not installed, this use case is preselected automatically.
- Tweak: The "Allow tickets without a WooCommerce order" setting now lives in its own section, "Direct sales (no WooCommerce order)", instead of deep inside the WooCommerce sales section — easier to find, especially on sites without WooCommerce. Nothing about the option itself has changed.
- Security: Added nonce verification to the admin-area AJAX endpoint (executeWCBackend) to block cross-site request forgery. The frontend already shipped the nonce; the server now verifies it.
- Security: Restricted WooCommerce order/product data actions (downloadTicketInfosOfProduct, downloadAllTicketsAsOnePDF, removeAllTicketsFromOrder, removeAllNonTicketsFromOrder, downloadPDFTicketBadge) to users with the manage_woocommerce or edit_shop_orders capability. Without this, a low-privilege role granted admin-area access via the "Allow only specific roles" setting could read or delete every customer's ticket data through the plugin-internal role check.
- Security: Removed an
eval(data)call after$.getScript()in the seating-admin loader (backend.js, _displaySeatingplanArea, line 1288).$.getScript()already executes the loaded script; the extra eval ran every byte of the response through the JS engine again. CWE-95 — a server-side change tojs/seating_admin.jswould have given code-injection on every admin page that opens the seating-plan area. No callers, no behaviour change beyond the redundant execute. - Security: Ticket codes, scanner auth tokens and ticket idcodes are now generated with a cryptographically secure random source (
random_bytes) instead of a hash of the current time (md5(time() ...)). The old values were predictable: two codes created in the same second shared their time component, so anyone who knew roughly when a ticket was issued could narrow the guessing range dramatically. CWE-338. Five generators were changed — the ticket code and the code-list lock in the WooCommerce assignment path, the per-list and per-order idcode, and the ticket-scanner auth token. The printed format is unchanged (same length and character set), existing tickets and tokens keep working, and no migration is needed.
- Tweak: Products with variations no longer show the seat selector on the shop overview page. In the overview no variation is chosen, so the selector could not work there anyway - it only pushed the product image out of its card. The "Select options" link leads to the product page, where the full seat selection (and its validation) lives. Simple products keep the quick selector in the overview.
- Tweak: The premium wizard now says exactly what the "Enable Recommended Settings" button does before you click it: attach tickets as PDF to the purchase email, merge all tickets of an order into one PDF, and raise the attachment limit to 21. Previously the popup only vaguely asked to "enable PDF ticket attachment" and revealed the actual settings only after they had already been changed.
- Tweak: "Skip" in the premium wizard closes the popup instantly instead of waiting for the server. The "don't show again" marker is written exactly once per installation - the first time the wizard is skipped while it is still unset; re-opening the wizard later sends no request at all.
- Fix: In multilingual shops (WPML), the seat check on "add to cart" was silently skipped when the customer bought in a secondary language. The check read the seat settings from the translated product, where they do not exist - a shop could sell numbered-seat tickets without a chosen seat. The check now reads the settings from the original product, like the cart display already did.
- New: A safety net at checkout. If a product with required seat selection reaches the cart or checkout without a seat on its line - possible when the seating plan was still unpublished at add-to-cart, when a seat reservation expired and was removed, or when another plugin rewrote the cart - the order is now blocked with a clear message until a seat is selected. Products with optional seats are unaffected.
- Fix: Adding a ticket with a chosen seat to the cart failed with "Invalid seat selection" on every attempt since 3.1.8. The seat check compared the chosen seat against a value that the variation-plan rework had left behind, so no seat could ever pass - on products with and without variations. Valid seats are accepted again.
- Fix: Two errors that blocked a shop after a staging-to-live database migration. (1) The Event Tickets admin page stayed on the loading spinner and showed "#505 auth token not found" as soon as a ticket in the list referenced a scanner token that no longer existed in the new database - the audit column tried to read the token's name and the missing-row error crashed the whole page. (2) Membership products that were never ticket products suddenly demanded a "ticket or access code" in the cart and at checkout, even though their product settings showed no restriction. Both came from values that the database carried over from staging. (1) is caught and falls back to "AUTHTOKEN DELETED" in the audit column; the migration artefact no longer breaks the page. (2) sits behind the same is_ticket gate that already protects the other ticket-specific cart fields (added in 3.1.8): a stale restriction on a non-ticket product is now ignored, both for the input field and for the checkout validation. The restriction still works as before for real ticket products, including variations, where the parent is walked up first.
- Fix: The "Check License" button in the settings did nothing since 3.1.6 - it showed "Checking..." forever and never contacted the license server, and after saving a license key the page never confirmed the activation. A helper function used by the button was defined in a place the button could not see, so the click stopped with an error before the request was sent. Your license was still checked in the background as before - only the visible check and the confirmation after entering a new key were dead. Moving the helper where every part of the settings page can use it brings both back.
- New: Fields that another plugin adds to an order line - for example the answers of a product add-on plugin - can now be shown as a column in the ticket list. Switch on "Display a column with the extra fields of the order line" in the settings. Until now those answers were only visible by opening each order, which is why shops with more questions than our two per-ticket fields had to build their own list. A second setting hides individual fields by name, for answers that belong in the order but not in a list. The values belong to the whole order line, not to a single ticket: an order line for three tickets carries one set of answers.
- Fix: A seating plan assigned to a single variation is now actually used in the shop. The product editor has offered a "Seating Plan Override" per variation for a while and saved it correctly, but the shop only ever read the parent product: the seat map on the product page never changed when a customer picked another variation, the cart notice and the seat check when adding to cart used the parent's plan as well. Picking a variation now swaps the map to that variation's plan, and a product whose plan only exists on its variations shows a map at all for the first time. Products without variations are unaffected.
- Tweak: In the variations of a ticket product, the label "This variation is NOT a ticket product" no longer sticks to its checkbox. It now keeps a fixed gap, so the line reads as a label and a box instead of one run-on word.
- New: For plugin developers: fields that your plugin collects at checkout can be listed inside Event Tickets, right where our users write their ticket template. Fill the filter saso_eventtickets_template_order_fields with your fields - key and name are enough - and shop owners no longer have to look up a meta key in the database to print your field on a ticket. The heading above them is your plugin name, taken from the plugin your callback lives in; give your own heading once as the array key if you prefer. Fields of different providers are never merged, not even when two of them pick the same heading. Reading the value itself never needed us: a ticket template prints any order meta with {{ ORDER.get_meta("your_key") }}. The list sits under the replacement tags on the options page and stays empty until a plugin registers something - if yours is missing, ask its provider.
- New: A new setting decides from which order status a seat counts as sold: "Mark seats as sold from this order status". Until now a seat only turned red when the ticket number was created, which is when the order is paid - with a cash voucher or a bank transfer that can be days later, and until then the seat stayed available for everyone else. Set the status to "pending payment" and the seat is gone the moment the order is placed, while the ticket still follows on payment. The default keeps the previous behaviour. The ticket number is written onto the same seat afterwards, so cancelling an order still frees it.
- Fix: A seat now turns red on the seat map when the order is paid, even if the customer took their time or paid later. Selecting a seat reserves it for a while - by default a quarter of an hour - and the plugin marked exactly that reservation as sold when the order was completed. If the reservation had run out in the meantime, and it always has when payment arrives days later through a cash voucher or a bank transfer, there was nothing left to mark, and the plugin treated that as done. The order carried the seat correctly, the seat map kept offering it to everyone else, and the same seat could be sold twice. The sale is now written to the seat map in any case, and a second run of the ticket creation cannot enter the same seat twice. Shops with instant card payment were affected as well whenever a checkout took longer than the reservation.
- Fix: A one-day event no longer prints its date twice on the ticket. When no end date is entered, the plugin fills in the start date internally so the ticket stays valid until the end of the event day - and the printed date treated that filler like an entry, so "12.09.2026 19:00" became "12.09.2026 19:00 - 12.09.2026". Only the date you actually entered is shown now: a start alone stays a start, a real end date still produces a range, and an end time on the same day still shows as "19:00 - 23:00". The same applies to the date picker: a ticket for a chosen day shows that day once instead of "15.06.2026 19:00 - 15.06.2026". For template authors: TICKET.end_date is never empty for the same reason, so testing it tells you nothing. Two new variables do: TICKET.is_end_date_set and TICKET.is_end_time_set.
- Fix: Removing a single ticket number from an order left that number on the order line. The number was freed in the ticket list, but the order, the email and the invoice PDF kept showing it, and it no longer lined up with the public ticket numbers next to it. The number was compared in its internal spelling against the one printed on the order, which never matched, so nothing was ever removed. Orders with several tickets on one line are the ones affected.
- New: For developers: the decision whether an order line gets a ticket now lives in one place and can be overruled with the filter saso_eventtickets_wc_order_item_is_ticket. It exists for shops where another plugin splits one product into several order lines - split VAT or invoicing plugins - so that only the original line carries the ticket while the other lines stay bookkeeping. Nothing changes unless the filter is used.
- New: For developers: the order manager now answers, per order line, how many ticket numbers a line is supposed to carry and which lines are still short of them (getExpectedTicketAmountForItem, countOrderItemsWithMissingTicketnumbers, orderNeedsTicketNumbers). Ticket creation uses the same calculation, so a tool that looks for missing numbers and the code that draws them can no longer drift apart. The premium bulk assignment is the first user.
- New: The ticket export now has its own column for the value you ask per ticket (the product setting "Request a value for each ticket from dropdown"). Until now only the name per ticket had one, so the answer was in the export but buried inside the raw meta column, where a spreadsheet cannot filter or sort it. The column stays in the file even when a product does not ask for a value, so the header does not change from export to export.
- Tweak: An extra safeguard so a product that is not configured as a ticket can never receive a ticket number, not even when it sits in the same order as tickets. Selling through the shop was never affected - the check was already made for every single order line - but the entry point that other code (the premium plugin, custom code) can call did not make it itself. It does now.
- Tweak: The admin area was redesigned. The top navigation is now a segmented control, the footer cards sit in a four-column grid, ticket status pills use semantic colors, and the primary action buttons share one style across the whole settings page.
- Tweak: The support footer now has a "Rate this Plugin" card linking to the WordPress.org review page, so the four footer cards fill one row.
- Fix: The "Dismiss" button of the version-notice box sat outside the card; it is now inside the card where it belongs.
- Fix: The Dashicons inside primary (lila) buttons inherited the WordPress default blue and clashed with the background; they are now white.
- Tweak: The ticket scanner and the ticket detail page now feel like one product. A design system was added - CSS custom properties for colors, spacing and radius, a BEM class structure on top of the existing IDs - and the parts that grew ugly over the years were cleaned up (hard-coded black border on the ticket box, the <center> tag on the scanner, the orphaned button_ok.png / button_cancel.png images). Every existing ID and class is still there, so a custom CSS file you wrote for an earlier release keeps working.
- Tweak: On the scanner page the ticket information no longer appears inline after a scan - the event name, date and seat only filled the space between the reader and the buttons, and on a phone the layout jumped around while the answer was on the way. While the scanner is waiting for the answer, the area shows a loading hint; as soon as the ticket is retrieved, a compact summary card appears (heading, title, date) with a color that matches the ticket state - green for valid, orange for expired or not yet redeemable, red for already redeemed. The full details open behind an "Show ticket info" button as a full-screen overlay with a close button, so the scanner display stays clean.
- Tweak: On the scanner the option row was moved up next to the buttons, so the "Scan and Redeem immediately" checkbox and its peers are visible right where the action buttons are. A new "Use classic layout" checkbox sits next to the existing "Use old ticket scanner library" one and toggles the scanner layout via a URL parameter - the same pattern that toggle uses.
- Tweak: The standalone ticket scanner is no longer preceded by a "Ticket Scanner" headline - it looks like a scanner device now, not like a page. On the public ticket view the wrapper no longer carries a hard border; the content sits directly on the page, with only the page's own padding for air. Scanner buttons are now 48 minimum height (56 for primary actions), so the person at the door in January gloves does not have to fight the touch target.
- Fix: The spinner shown while the scanner waits for the server was invisible on the modern layout - the CSS class that animated it lived only inside the legacy HTML page. The animation is now defined in the design system stylesheet, so the spinner shows wherever it is used.
- Fix: Three button styles in the scanner used three different looks - one was a bare HTML button, one used a class the stylesheet had never heard of, and one toggled between gray and green via inline JavaScript. They are now all built on the same BEM class, and the disabled state has a real visual treatment instead of just disappearing.
- Fix: The "Badge" and "PDF" buttons on the scanner did nothing to indicate the download was on the way. They are now disabled while the file is being fetched and show a small spinner inside the button label, restoring the original label as soon as the download is delivered (or fails).
- Tweak: The "AI Support Bot" card is gone from the support view. It answered from a knowledge base we stopped keeping up to date, and an answer about last year's plugin is worse than none. Documentation, release notes and the support address are where they were.
- New: A ticket can be passed along from the ticket page. On a phone the usual share sheet opens - WhatsApp, Telegram, Signal, mail, whatever is installed - on a desktop browser WhatsApp and Telegram are offered as links. That is how the second ticket reaches the friend who is coming along, and how the ticket gets from the laptop to the phone. Your shop sends nothing itself; the customer does. The page says out loud that whoever receives the link can show the QR code. Can be switched off ("Let customers send their ticket on"), and it is shown in every kind of ticket sale, including vouchers.
- Tweak: The last pieces of premium licensing left this plugin. The "Check License Server" button and the update dialog that appeared after entering a license key are gone - both reached out to our server from the free plugin, which is not what a plugin on WordPress.org should do. Updating premium is the premium plugin's own job ("Check license & update" next to the license key, version 1.7.3 and newer). What stays here is the display: the license status and a button to refresh it, which asks the premium plugin to do the checking.
- New: A message you can set for events where tickets are still sold at the door - it is added to the "sales closed" text when the premium version marks a product that way, so a buyer who arrives too late for the online sale is not left with a dead end.
- Fix: Tickets without a WooCommerce order could not be redeemed by typing their number into the scanner - the very way a printed card is meant to be checked at the door. It failed with "#9302" unless a second, separate option was switched on as well. Allowing tickets without an order is now enough.
- Tweak: The scanner said "Ticket is NOT paid ()." for a card that was never sold in the shop - a defect message for the case the feature is made for, with an empty bracket on top. It now says the ticket was handed out directly.
- Tweak: In the product's Event Tickets tab and in the ticket list, option keys no longer appear in customer-facing text. The settings page hides them in the entry view as well and shows them under "All options", where support answers need them.
- Tweak: The "Getting Started" checklist now reads the real state of your installation instead of guessing from counters. Until now it ticked off "assign a list to a product" as soon as any ticket existed anywhere, and it congratulated you for the ticket list that the plugin creates by itself. It also no longer counts a fixed four steps: what needs doing is what is listed.
- Tweak: In the product's Event Tickets tab, the ticket switch and the list now come first and the note about the free ticket limit follows below - it used to be the first thing in the tab, in red, before the setting it belongs to.
- New: After activation the plugin says where to go next, once, with a button - instead of leaving you to find the menu entry at the bottom of the sidebar. Installations that already have tickets are not bothered with it.
- New: The setup wizard now ends by showing what it actually switched on for you ("redemption locked until the event starts", "scan redeems immediately", …). The defaults fit most shops - you just could not see them. It also stops claiming you are all set while listing things you still have to do: what is left is one product, and the button goes straight there.
- Tweak: The warning about "Plain" permalinks was a dialog on every single page load, with no way to act on it. It is now the first step of the setup check, with a button that opens the permalink settings - and it is the one thing that still shows up even after you dismissed the setup check, because without it the ticket page and the scanner cannot be reached.
- Tweak: The setup wizard now remembers which kind of sale you picked. Until now the settings page asked the same question a second time, minutes after the wizard had already asked it.
- Fix: In dialogs, the recommended button is highlighted again instead of whichever button happens to sit on the left. In the setup wizard that meant "Skip" and "Back" looked like the main action while "Start Setup" and "Apply & Finish" looked secondary.
- Fix: A tip in the setup wizard showed "⚡" as plain text instead of the symbol, and the product tab said "Make sure your are not selling" instead of "you are".
- Fix: The free version asked for a premium license key. On a plain installation without the premium plugin, a dialog appeared saying "Thank you for using the Premium version!" and asked for a key that such an installation never had — a comparison error made "no premium version" look like "premium version installed, key missing". The dialog now only appears when the premium plugin is really installed.
- New: The plugin page now shows when the plugin was last updated, next to the version, with a link to the changelog of every release. Whether a plugin is still being looked after is a fair question, and the answer belongs where you are, not on a sales page.
- New: A setting that belongs to a different kind of sale but was changed anyway is now shown in the filtered view instead of being hidden - highlighted, with a note that it can make your shop behave unexpectedly and a "reset to default" button right next to it. Those are exactly the leftovers that cause the "it does something I never asked for" cases.
- New: "Restore the defaults of this view" resets only what is currently in front of you, and lists beforehand which settings would change. The existing button that resets all options is untouched.
- New: Existing installations are asked once which kind of ticket sale they run. Whoever answers gets the filtered view, whoever declines keeps all options and is not asked again.
- New: The settings page can now show only the settings that belong to your kind of ticket sale. Pick your event type once - event tickets, day passes, memberships or vouchers - and the page starts with the handful of settings that decide how your shop behaves (14 instead of 306). From there it is one click to everything that belongs to your event type, and one more to all options; nothing is ever hidden for good. The search always looks through every setting and tells you when a match sits outside your event type.
- New: The settings page has a search field. Type two letters and only the matching settings stay on the page - it searches the name, the description and the option key, so you can also paste the key from a support answer or from the documentation ("wcTicketHideTicketAfterEventEnd"). The number of matches is shown, the search term is highlighted, "Esc" clears the field and the "/" key jumps into it. An empty field brings the page back exactly as it was.
- New: Once the setup check has nothing left to report, you can dismiss it for good with the small x. From then on it is not only hidden but no longer worked out either - a finished installation pays nothing for a check it does not need. Clear "setupStatusDismissed" in the settings export to bring it back.
- New: The settings page now opens with a short setup check that reads your actual installation instead of showing you more options: is a product connected to a ticket list, and does your door team have access to the ticket scanner. Every open step has a button that takes you straight to the right place; once both are done the check simply confirms that you can sell and check tickets.
- New: Tickets can now work entirely without a WooCommerce order, for printed cards you hand out yourself. Create the ticket numbers in a ticket list as before, switch on "Allow tickets without a WooCommerce order" — either globally in the WooCommerce settings or for a single ticket list — and the scanner accepts them, shows them and redeems them. Both switches are off by default. Note what you give up for those tickets: the plugin can no longer verify them against a paid order, only that the number exists, is active, has not been redeemed yet and belongs to its list. Tickets sold through WooCommerce are untouched and keep the full check.
- Tweak: This plugin no longer contacts the license server of the premium version. That check now lives in the premium plugin itself, where it belongs — this plugin only stores the answer and uses it to switch premium features on or off. If you use the premium version, update it to 1.8.0 or newer; until you do, your premium features stay switched on and the plugin asks you to update instead of expiring them.
- New: Scanner auth tokens can now be restricted to ticket lists, not only to products ("Bound to ticket list(s)" when editing a token, comma separated list ids, empty means all). A door team then only redeems the lists it is responsible for — for a venue with its own ticket list, one token per venue. This is also the only restriction that can apply to tickets without an order, because those have no product to bind a token to.
- New: A ticket list can carry its own event window ("From" / "Until" with date and time). It applies to tickets without an order, which have no product to take event times from, and is governed by the same scanner options as before — no redemption before the start, none after the end, or none after the start. Empty means no time limit.
- New: Seat order can now be arranged by hand. A "Seat Order" button above the seat list of a simple (dropdown) seating plan opens a drag-and-drop list; the order you save is the order buyers see in the seat dropdown. Until now the order was fixed to the sequence in which the seats were created.
- Tweak: The action buttons of the seating plan list no longer wrap onto a second line — the column is wider and kept on one line.
- Fix: The "Go to Seating Plans" and "Create one first" links in the product panel, and the admin link passed to the frontend seat selector, pointed to a non-existent admin page (
?page=sasoEventTickets). Following them produced "Sorry, you are not allowed to access this page." The links now use the correct page slug so the seating tab opens as expected. - Tweak: Plugin description and FAQ now clearly state the 50-ticket free-version limit and the exact free-tier caps (5 ticket lists, 1 seating plan with 20 seats, 3 scanner auth tokens).
- Tweak: Removed unverified social-proof claims ("4.9/5" rating, "1,000+ event organizers") and replaced with the verifiable WordPress.org metric ("Active on 1,000+ WordPress sites").
- Tweak: Removed named-competitor comparison (Eventbrite, Ticketmaster) from the plugin description.
- Tweak: "No per-ticket fees" clarified to "No per-ticket service fees" with payment-processor qualifier.
- New: Online sales can now be stopped a set number of hours before the event starts ("Stop online sales before the event starts" in the WooCommerce settings, off by default; when switched on it stops sales two hours before the event unless you change the number). Useful when you also sell at the box office and want the online shop to close first. Products without an event date are never affected; for day-chooser products the date the customer picked counts. Buyers are told when they add the product to the cart, and a cart that was filled before the cutoff is blocked at checkout. The message is configurable.
- Tweak: When online sales have closed for a ticket, the buy button is now hidden on the product page and in product lists, and a short line explains why, instead of letting the buyer add the ticket and only failing afterwards. This also covers direct "add to cart" links. Products without an event date, day-chooser products (the buyer picks the date later) and everything that is not a ticket are never affected, and the shop admin still sees the normal buttons in the backend.
- Tweak: If a buyer leaves a ticket in the cart until online sales close, WooCommerce drops it from the cart — the wording is now yours instead of WooCommerce's "please contact us if you need assistance", and can be changed in the settings ("Message when a closed ticket is dropped from the cart"). Items removed for any other reason keep the WooCommerce text.
- Fix: The "Same-day cutoff time" of day-chooser products was evaluated in the server's timezone instead of the shop's, so on a site ahead of UTC it took effect hours too late — with a shop in Central European Summer Time, a cutoff set to 17:00 only blocked today's date from 19:00 on. It now applies at the time you entered, in the timezone configured in WordPress, both in the date picker and when the cart is checked. The date picker previously also used the buyer's own browser clock, which gave visitors abroad a different cutoff than the one enforced at checkout; it now follows the shop's clock as well.
- New: Optionally require a valid ticket or access code to purchase a product. Pick the required event/code list in the product's Event Tickets tab — until you do, nothing changes for any product. Buyers enter their code in the cart and can only check out with a valid, unused code from that list. Use it for presale and access codes, or to require a ticket from an earlier event — for example a group-stage ticket in order to buy the final. Free.
- New: Per product, the same code can optionally unlock several purchases ("Allow the same code for several purchases"). Off by default, so each code unlocks exactly one purchase.
- New: The cart tells the buyer straight away whether the entered code was accepted, is already used, or is not valid for that product — instead of only failing at checkout.
- Fix: The global switch "Allow requiring a ticket or access code to purchase" now really disables the feature everywhere when switched off. Previously it only controlled the cart script, while checkout still demanded a code for any product that had a list assigned — which, combined with the cart field not submitting the code, could make such a product impossible to buy.
- Fix: On hosting accounts where the server's temporary directory cannot be written to (common with Plesk, open_basedir or PHP-FPM private temp directories), ticket PDFs were never created. The plugin still passed the file path on, so the PDF merge failed and the order email was sent without the ticket and without the calendar/info attachment — with no visible error. The plugin now falls back to a folder inside the WordPress uploads directory, and reports a clear, actionable error if no writable location exists at all. The same fallback now applies to badge PDFs and to all email attachments, which previously failed silently on these hosts as well.
- Fix: Merging ticket PDFs no longer aborts completely when a single source file is missing. Unreadable files are skipped and logged individually, so the remaining tickets are still delivered.
- Fix: The "Delete All Tickets" button on a ticket list failed with a server error instead of deleting anything. The button never worked since it was introduced; it now removes all tickets of the selected list, including their WooCommerce order data. Long lists are deleted in small batches with a progress bar, so even lists with many thousands of tickets no longer run into a server timeout.
- Fix: On hosts that run a different PHP version for WP-CLI than for the website (IONOS and similar split-PHP setups), the plugin's template-engine PHP 8.1 check no longer aborts WP-CLI runs with a fatal error. Ticket and scanner pages are never rendered from WP-CLI, so the check is now skipped in CLI mode. This prevents some hosts from auto-disabling the plugin after a WP-CLI or cache-build run. Website behaviour is unchanged — the actionable PHP 8.1 notice still appears when a ticket or scanner page is opened under an older PHP in the browser.
- New: Interface translations expanded to the full language set — added Arabic, Czech, Danish, Greek, Hindi, Korean, Norwegian Bokmål, Polish, Romanian, Russian, Swedish, Turkish, Ukrainian, Traditional Chinese, plus corrected Japanese (ja) and French (fr_FR) locale files.
- Fix: When a server runs the plugin folder under PHP below 8.1 (required by the bundled template engine) — which can happen for files opened directly from the plugin folder even when the main site runs a newer PHP — the ticket and scanner pages now show a clear, actionable message instead of a blank 500 error. The message points to the "Ticket detail URL path" option and to enabling PHP 8.1+ for the whole hosting account.
- Fixed: Support info no longer shows a broken "Own URL" with a double slash when no ticket detail URL path (compatibility mode) is set — both the displayed cards and the copy-to-clipboard text now show "(not set)" instead.
- New: Event portals — the Congress tool now works for any event (opera, zoo, festival, …).
- New: Optional card-grid landing showing each page as a card with an icon or image and a short description.
- New: Customizable portal label per portal (with a global default, "Infos") — used on the page, in the wallet action and the order email.
- New: Back-to-home control in the portal view.
- New: Insert ticket/order/product/customer variables into info and custom section text; they are filled with the visitor's data when the page is opened.
- Improvement: Internal data and links are unchanged — existing congresses keep working exactly as before.
- Improved: Cleaner admin dashboard — moved the "List of tickets" description into the list card next to its buttons and removed the redundant heading and divider.
- New: Speaker sections — add one or more speakers (photo, name, title, short bio). A single speaker is shown in full; multiple speakers appear as a grid of cards with a detail view and a back control.
- New: "My ticket" entry in the portal always shows the ticket's QR code, so attendees without a printed badge can present it at the entrance.
- New: Portal entries (such as "My ticket") also appear as cards on the card-grid landing.
- Improvement: The portal title is now clickable and returns to the start page; the "Add to Vollstart Wallet" link moved from the header into the "My ticket" view.
- New: View access toggles (security) — each output reachable through the ticket link (ticket detail view, PDF, ICS calendar, badge PDF, all-tickets-in-one-PDF, event portal/congress) can now be switched off individually. When off, the view is no longer rendered and a short "deactivated" notice (or 403 for downloads) is shown. All default to on, so existing installs are unaffected. Unlike the older "hide button" options, this actually blocks the URL.
- New: Optional "Allow redemption by plain ticket number" (off by default). When enabled, a ticket can additionally be redeemed using only the plain ticket number printed on the card; the full ticket id keeps working as before. Note: for the plain number the copy protection does not apply, and it is unsafe together with ticket reuse (a warning is shown on both options).
- Fix: Settings checkboxes whose default is "on" (e.g. the new view-access toggles, the QR scanner on the validation form, the seating-plan/venue buttons) could appear unchecked until the settings page was saved once. The admin UI compared a boolean default too strictly; it now renders the correct checked state. The actual behaviour was always correct (the option was on) — only the checkbox display was wrong.
- New: Congress mode — organizers create congress objects (programme, downloads, texts, media) and assign them to WooCommerce products.
- New: A dismissible "What's New" banner in the admin introduces the Congress feature (shown once per version).
- New: Ticket holders open the congress page via their ticket ID. Like the ticket detail and scanner pages it is served from the plugin path (
…/ticket/{ticket-id}?congress, query fallback…/?code={ticket-id}&congress), so it is compatibility-mode aware and never collides with shop page slugs. - New: Offline-capable congress page with a Web App Manifest (installable as a mini PWA).
- New: Sections with optional password protection (server-side transient, 1h TTL).
- New: Programme sections with a day/slot structure, plus download and media sections (WordPress Media Library).
- New: "New edition" button for recurring congresses — duplicates the congress and sets an automatic expiry date on the original.
- New: Option to activate/deactivate the public congress page (default: active); the admin area stays available either way.
- New: Event-relative access window — optional event start/end time per congress; global options control how many hours before the start access opens and how many days after the end the data stays available.
- Improvement: Congress assignment now lives directly in the Event Tickets product tab (instead of a separate tab); the dropdown shows the event/expiry date for easier selection.
- New:
congress_urlin the Wallet API response — the Wallet app shows an "Open congress" button when the product is assigned to an active congress. - New: Congress URL pattern listed on the Support/System Info page (adapts to the site location); the admin ticket detail shows a direct "Open congress page" link for tickets whose product is assigned to a congress.
- Fix: Congress access now accepts the public ticket ID (as used by the Wallet/QR), not only the internal code — so the Wallet/customer link works reliably.
- New: Congress section editor with full input masks per type — Info/Custom use a visual editor, Download picks files from the media library, URL with internal/external link option, Program with day & time-slot structure, Media gallery.
- New: Congress sections now track and display created/updated date and the editing user.
- New: Visual text editor (TinyMCE) for the "Additional text on PDF ticket" and "Ticket Badge HTML" options instead of a plain textarea.
- New: Tag picker dropdown inside the Ticket Badge editor — insert replacement tags ({TICKET.}, {ORDER.}, {PRODUCT.*} …) at the cursor instead of copy-pasting from the list below.
- Improvement: Modernized admin UI — compact buttons, lightweight ghost-style table action buttons grouped together, navigation menu with active highlight, modern DataTables styling.
- Improvement: Congress editor redesigned as a clean card layout; all native browser confirm/prompt dialogs replaced with the plugin's own styled dialogs and loading spinner.
- New: Congress pages — sections are now grouped into pages (the first page is the start page). Visitors get a sidebar (desktop) / hamburger drawer (mobile) navigation; the start page loads instantly and other pages are fetched on demand, so large congresses stay fast.
- New: Congress section types Image (from the media library, with caption) and Video (paste a YouTube/Vimeo link for automatic embedding, or upload a video file).
- New: Image sections have a display-size option — full width (default), original size, or a custom width (px or %).
- New: Image sections can optionally open full size in a lightbox when clicked (default off).
- New: Download files can be set to "open inline" (PDF/images open in the browser) instead of forcing a download.
- New: Admin can create, rename, delete and reorder congress pages (drag & drop) and move a section to another page; sections are drag-sortable within a page.
- Security: All HTML content is sanitized with
wp_kses_post()— no JavaScript allowed in congress content; video embeds are generated server-side via WordPress oEmbed. - i18n: All new congress strings (admin editor + visitor page) translated into 11 locales (de_DE, de_CH, es_ES, fr_FR, hu_HU, it_IT, ja_JP, nl_NL, pt_BR, pt_PT, zh_CN), including the JavaScript UI (script-translation JSON).
- Performance: Transient cache (5 min) for access checks; ETag/Last-Modified for browser cache invalidation.
- Fix: Same-day cutoff time was not working when the product also had a fixed start date configured. The absolute start date was applied after the cutoff check and silently overrode it, leaving today selectable past the cutoff time. Cutoff check now runs after all date overrides and correctly disables today in every configuration.
- Fix: Same-day cutoff time is now validated server-side at checkout. A customer who selected today's date before the cutoff and held the cart past it is now blocked at checkout.
- New: Congress can be switched active/inactive per congress (on top of the global on/off) — hide it everywhere without unassigning, e.g. to publish the info only later after purchase.
- New: The Vollstart Wallet shows a congress button on the ticket; it enables/disables on the next refresh based on the global switch, the per-congress active flag, the order status, and the access window (which now derives the event date from the ticket's product). Outside the window it shows a disabled "available from …" hint.
- Changed: Wallet API now returns a generic, extensible
actionsarray (future content types reuse it) instead of the singlecongress_urlfield. - Changed: Removed the redundant per-congress "Event start/end" fields from the congress editor — the event date comes from the WooCommerce product. Older entries are archived in changelog.txt shipped with the plugin.