Tickets & Passes for WooCommerce
| 开发者 | macvej |
|---|---|
| 更新时间 | 2026年10月18日 05:59 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Ticket - plain admission with a validity window and a set number of uses. Day tickets, entry tickets, gift admission. The customer can pick their own start date within a range you set, or you fix the date yourself.
- Timeslot Ticket - admission for a specific date and time, with a capacity per slot. Generate slots on a repeating schedule instead of building next month by hand. Unpaid reservations are released automatically, so an abandoned checkout never sits on a seat.
- Pass - valid across a period rather than a single visit: season passes, memberships, annual cards. Passes can include guest passes the holder gives away, carry a cardholder photo, and enforce a cooldown between scans.
- A scanner page on your own domain, at
/check-in/. Full screen, no admin bar, nothing for door staff to get lost in. - No app to install. Any modern mobile browser works. Where the phone has a native barcode detector the scanner uses it, otherwise it decodes in the page.
- Colour-coded results you choose: valid, already used, expired, on cooldown, or not found.
- Photo check on passes. Staff see the cardholder photo beside the scan result and can compare it with the person in front of them.
- A Scanner user role that grants check-in and nothing else in wp-admin.
- Every decision is made on your server, never on the phone, so a cancelled ticket cannot be waved through by putting the phone in airplane mode.
- A REST check-in API underneath, so a third-party or native scanner app can use the same endpoints.
- A dashboard per product type - Tickets, Timeslot Tickets and Passes - each with search, manual check-in, resend, reset and cancel.
- Manual check-in for when there is no phone at the door.
- Analytics charting check-in activity by day and by hour, with a CSV export.
- Per-type colours and hint text, so a ticket looks like part of your site rather than part of a plugin.
- Shop Manager friendly. Everything is gated on
manage_woocommerce; nobody needs an Administrator account to run the door.
- Tickets and Passes tabs on the standard WooCommerce My Account page.
- The QR code on screen plus a printable PDF download.
- Live status on every ticket - active, used, expired, cancelled or not valid yet - with uses remaining.
- Add to Calendar on timeslot tickets, as a normal
.icsfile. - Guest passes handed out from the account page, and a photo upload where a pass asks for one.
- The WooCommerce order confirmation and completed order emails are extended with ticket, timeslot ticket and pass details.
- Resend Ticket and Resend Pass templates for a re-sent QR code.
- Gifted pass emails: when a buyer enters someone else's email for a pass, that person receives it. If the address has no account, one is created and they get a link to choose a password.
- Every subject and body is edited in wp-admin and supports merge tags for order and ticket details.
- WooCommerce HPOS (High-Performance Order Storage) and the block-based cart and checkout.
- Block themes and classic themes.
- Translation ready - every string is translatable, and the plugin ships translations for 25 languages plus a POT file for any other language.
- No build step. All PHP, JavaScript and CSS ships readable and editable.
- WooCommerce, installed and active. WordPress will not let the plugin activate without it.
- PHP 8.0 or newer.
- HTTPS, because phone browsers only give camera access to secure pages.
安装:
/wp-content/plugins/ over FTP. Activate from the Plugins screen with WooCommerce already active. Activation creates the plugin's database tables and refreshes permalinks, so the My Account tabs and the scanner URL work straight away.
2. Turn on the product types you need
Go to Ticket & Passes > Settings. Tick Enable on the Ticket, Timeslot Ticket and Pass tabs. Anything you leave off stays out of your way.
3. Turn on the scanner
On the Scanner / API tab, make sure the built-in scanner is on. Leave the API off unless an external scanner app will check tickets in; the built-in scanner does not need it. The tab then shows your scanner URL, which is /check-in/ on your own domain.
4. Create a product
Products > Add New, then pick Ticket, Timeslot Ticket or Pass from the Product data dropdown - the same dropdown that holds Simple and Variable. Validity, uses, capacity, recurring schedule and QR design appear below it.
5. Give door staff access
Edit the user under Users and set their role to Scanner. They can then open /check-in/ on a phone and check people in, and see nothing else in wp-admin. Administrators and Shop Managers already have access.
Settings at a glance
Settings live under Ticket & Passes > Settings in six tabs. Only the tabs for the product types you sell need touching.
- General - the date and time format used across the plugin, and the switch for the Analytics screen.
- Ticket - enable the product type, its accent colour and its date picker styling.
- Timeslot Ticket - enable the product type, the date picker hint text, and seven colours for the date and timeslot picker.
- Pass - enable the product type, the hint text above the person fields, and five colours for the per-person cards.
- Scanner / API - the API switch, the built-in scanner switch, the scanner URL, the three scan-result colours, and an API endpoint reference.
- Email - the six editable templates and their merge tags.
屏幕截图:
常见问题:
Does it need WooCommerce?
Yes. The plugin adds WooCommerce product types and will not activate without WooCommerce active.
Are there any per-ticket fees?
No. There is no external service and nothing to sign up for. You sell through your own WooCommerce checkout, and what you charge is what you keep.
Can I sell tickets and passes in the same shop?
Yes. All three product types can be on at once, and they can sit in the same cart and the same order as your normal products.
Do door staff have to install an app?
No. The scanner is a web page that uses the phone camera. It needs a browser and HTTPS, which is what the camera API requires.
Does the scanner work offline?
No. Every scan is checked against your site as it happens, so the phone needs a connection at the door. That is also why nobody gets a cancelled ticket through by putting the phone in airplane mode.
Who is allowed to check people in?
Users with the Scanner role, and users with the manage_woocommerce capability, which covers Administrators and Shop Managers. The scanner page turns everyone else away.
How do door staff use the scanner?
- Give them a user with the Scanner role (Users > edit user > Role). They need no other access.
- On their phone, open
/check-in/on your site (for examplehttps://example.com/check-in/) and log in. Add the page to the home screen for one-tap access. - Allow camera access when the browser asks. The camera only works over HTTPS.
- Point the camera at the QR code on the ticket or pass. The scanner locks onto the code and shows who it belongs to. Tap Check In to confirm, or Cancel to scan again.
- The result is shown in the colour you chose on the Scanner / API tab: valid, already used, expired, on cooldown or not found.
- If a code will not scan, open the menu and type it in by hand. The menu also lists recent check-ins and has Log out.
Can I check people in without a phone?
Yes. Each dashboard in wp-admin has a manual check-in action, so you can find the ticket and let someone in from a computer.
Can I use my own scanner app instead?
Yes. Check-in runs through a REST API, and the endpoints are documented on the Scanner / API settings screen. The built-in scanner page and the API are independent switches, so you can run the API on its own.
Can the same ticket be used twice?
That is up to the product. Each ticket and pass has a maximum number of uses, and passes can have a cooldown so the same code cannot be scanned again immediately.
Is the QR code on its own enough to let someone in?
The QR code identifies the ticket. On passes that carry a photo, staff also see the cardholder photo at check-in and can compare it with the person in front of them.
I run nginx (or IIS). Is anything needed for the private files?
Not for the plugin to work: QR codes, PDFs and photos live under a folder with a random name and are served through the plugin, which checks the caller on every request, so a direct URL is not guessable. On Apache and LiteSpeed the plugin also drops an .htaccess deny into that folder as a second line of defence.
You do not need to work this out yourself. Tickets & Passes > Settings > General has a "Private file protection" panel that detects your server and either tells you there is nothing to do, or shows the exact line to paste - click it to select it.
nginx and IIS ignore .htaccess, so if you want the same belt-and-braces there, add this inside the server { } block that serves WordPress and reload nginx:
location ^~ /wp-content/uploads/tpfw- { deny all; }
It blocks direct HTTP to the plugin's upload folders only - not the rest of the media library, and not the plugin's own file route, which is PHP.
On IIS, the equivalent goes in web.config as a URL Rewrite rule:
<rule name="TPFW deny static tpfw uploads" stopProcessing="true"><match url="^wp-content/uploads/tpfw-" /><action type="CustomResponse" statusCode="403" statusReason="Forbidden" statusDescription="Forbidden" /></rule>
Leave index.php?tpfw_file=... alone in both cases - that is the route customers' links actually use.
Does it work with HPOS and the block checkout?
Yes. The plugin declares compatibility with WooCommerce High-Performance Order Storage and with the block-based cart and checkout, and the timeslot date picker works on block themes.
What happens to my data if I delete the plugin?
Settings, scheduled tasks and the Scanner role are removed. Your tickets, passes and check-in records are kept, so removing the plugin to test a conflict cannot wipe a season of admission history.
If you do want all of it gone, add this to wp-config.php before you delete the plugin:
define( 'TPFW_REMOVE_ALL_DATA', true );
That drops the plugin's database tables and deletes the generated QR codes, guest passes, PDFs and pass photos. It cannot be undone. Take a backup first.
Can customers print their tickets?
Yes. Every ticket, timeslot ticket and pass has a printable PDF download alongside the QR code on screen, from the Tickets or Passes tab in My Account.
Does deactivating remove anything?
No. Deactivating stops the plugin and clears its scheduled tasks. Settings and records are left alone, and reactivating picks up where you left off.
更新日志:
changelog.txt in the plugin folder.
2.1.1
- Security: refunds and revokes that fail on a database error are now retried; an order-screen Cancel that was locked still cancels on retry; deleting a refund restores the codes it had revoked.
- Security: the legacy
scannerrole is only migrated or honoured when this plugin created it. - Fix: a timeslot's start and end are locked while places are held, not only once sold; cancelling releases a saved hold even if reservations were switched off.
- Fix: the cart's reservation countdown uses the hold's own duration; a failed check-in read no longer yields an incomplete privacy export.
- New: picking a timeslot's start or end time fills the empty other side an hour away (start + 1h, end - 1h) until you edit it yourself.
- Security: cancel and refund revoke every code on a line under the issue and check-in locks, retry when locked, and fail on a failed read; timeslot seats can't be double-booked; slot and series cancels check database errors.
- Security: scanner API returns correct 401/403 and accepts only a login cookie when off; dashboard PDF links checked per row; pass photos lose EXIF, GPS and XMP data.
- Fix: recurring timeslots generate once per series, follow rule edits, keep cancelled slots cancelled, use ISO weeks; cancelling a series keeps slots that have started.
- Fix: Reset refuses a ticket whose slot was cancelled; transfer emails greet the new holder and hide the buyer's order number.
- Fix: guest passes, plain-text and failure emails, Add to Calendar, daylight-saving reservations, type-off behaviour, Privacy tools, My Account, scanner camera states, analytics year, gift accounts, #rgb colours and limit validation.
- Fix: network activation and deactivation cover every site and require WooCommerce on each.
- Accessibility: labelled guest pass dialog, labelled settings fields, text equivalents for analytics charts.
- Performance: dashboard and CSV queries load orders per page in one read; assets are versioned by plugin version; datepicker CSS is scoped under
.tpfw-datepicker.
- New: translations for 23 more languages - Arabic, Chinese (Simplified and Traditional), Czech, Dutch, Finnish, French, German, Greek, Hungarian, Icelandic, Indonesian, Italian, Japanese, Korean, Norwegian (Bokmål), Polish, Portuguese (Brazil), Romanian, Russian, Spanish, Turkish and Ukrainian. They are machine translations with a hand review of plurals and formatting; corrections are welcome on translate.wordpress.org, where a community translation still wins over the one shipped here.
- Fix: the Danish and Swedish translations now cover the strings added in 1.6.0, which were showing in English.
- Fix: every shipped translation now declares its language's plural rules, so counts such as "3 spots left" use the correct word form in languages with more than two forms.
Older releases: see
changelog.txt.