| 开发者 | garethtempo |
|---|---|
| 更新时间 | 2026年9月11日 19:20 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
No. A unique database index makes it impossible for a seat to be sold twice, however many people click at the same moment. The loser of a race is told immediately and the map updates.
Their seats are held for ten minutes and then go back on sale automatically. The countdown buyers see is a courtesy; the server decides.
Event and countdown pages are fully cacheable and do no database writes, and live availability comes from one small cached endpoint. On-sale times flip themselves at the appointed moment, so nobody has to press publish at 9am.
Yes. A venue that no performance uses can be binned from the Venues screen; one that is still in use says so. Cancelled and past performances can be removed from the event's performances list; their orders and reports are kept. Binning or deleting an event takes its performances with it.
Give your stewards the Tempo door role (or one shared login). They log in and land on the Door screen: the attendee list for the next performance, with search and one-tap mark in. Scanning the QR code on any ticket with an ordinary phone camera opens that booking on the same screen, and the party pass QR checks a whole group in at once. Door users see nothing else: no orders, prices or buyer emails.
Yes. Performance, Seat, Attendee, Ticket, Venue, Section, Row and Event can all be renamed under Settings, Branding and vocabulary, and your words are used everywhere buyers look, including emails and PDF tickets.
Nothing is deleted unless you opt in first under Settings, Privacy. Buyer data also plugs into the WordPress privacy tools for export and erasure, and you can set a retention period after which attendee details are anonymised automatically.
No. The free plugin sells tickets end to end, including QR check-in with a phone camera. Pro adds capabilities such as the drag-and-drop designer and a dedicated continuous scanner; it never unlocks something already installed.
[tempo_box_office_events title=""] hides the grid's own heading; any other value replaces it.wp tempo-box-office demo-seed, or set the TEMPO_BOX_OFFICE_DEMO_SEED constant and call the seeder; it never runs on a real site by accident and running it twice does nothing.tempo_box_office_demo_seeded action fires after the demo story is built, with every id it created.tempo_box_office_order_pricing filter adjusts an order's price (or refuses it) before it is created, tempo_box_office_promo_codes_enabled shows the box, and POST /pricing/quote prices a basket without creating anything. Database update 3 adds the discount columns (runs automatically).PickerPage::markup() / enqueue()), and hold requests carry the REST nonce when one is configured; new filters tempo_box_office_nav_items, tempo_box_office_enforce_on_sale and tempo_box_office_order_requires_email, and the tempo_box_office_door_toolbar action.tempo_box_office_hold_budget filter) so a script cannot hoard a whole show while ordinary buyers, including many behind one office or mobile network address, are unaffected.