Eventnetic - Event Tickets, Booking and Calendar
| 开发者 | eventnetic |
|---|---|
| 更新时间 | 2026年9月30日 21:55 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Eventnetic turns a WordPress site into a box office. Create an event, decide what a
ticket costs and how many there are, put the booking form on a page, and take the
money. Nothing else has to be installed and there is no account to open anywhere.
It is a plugin for events rather than appointments: people buy a ticket for a date,
not a slot with a member of staff. A cinema showing a film on five Sundays, a venue
with a support act and a headliner, a workshop with eight benches and a deposit up
front: that is the shape it is built around.
The plugin is free with no cap on how many events you run or how many tickets you
sell, and Eventnetic takes no cut of the money.
If you later add a card gateway, that company charges its own processing fee, but
nothing comes to us per ticket. You can see it running before you install anything.
Why Eventnetic is different
- Standalone. No WooCommerce, no page builder, no form plugin, no calendar plugin underneath it.
- No per-ticket fee, ever. Not in the free plugin and not on a paid plan.
- Your data, your server. Customers, bookings and money stay in your own database.
- One screen, not twelve settings pages. Lists that filter and sort, a calendar, and forms that tell you what is wrong before you save.
- No theme can break the booking form. It renders inside a shadow root, so the theme's CSS cannot reach into it and it cannot reach out.
- Unlimited events, tickets, bookings and customers. Nothing is capped.
- Single-day, multi-day and full-day events
- Capacity per event, counted as bookings arrive, and it refuses to drop below what is already sold
- Status per event, open or closed or cancelled, with the reason shown to the visitor
- Events at a venue, online, or both, with a joining link and password released a set number of minutes before the start
- A timezone per event, for when one of them is somewhere else
- Categories with colours, venues and staff, all reusable across events
- A cover image, a colour and a gallery per event
- Duplicate an event; delete in bulk
- One click builds the WordPress page for an event with the booking form already on it
- An admin calendar with month, week and day views: drag an event to another day, click a day to create one
- schema.org
Eventdata on the page, so search engines read the date, the venue and the price
- Several ticket types per event, in the order you want them
- Each type either draws on the event's capacity or holds a quota of its own
- A sale window per ticket type: when it goes on sale and when it stops
- Minimum and maximum per order
- Deposits per ticket type, a percentage or a fixed amount, with the balance left owing on the order
- Ask each attendee for their own name, email and phone, per ticket type
- 151 currencies, with symbol position, thousands and decimal separators, and 0 to 4 decimal places
- A ticket type that has already sold cannot be deleted by accident
- A step at a time: date, tickets, your details, attendees, payment, confirmation. A step that means nothing for an event is not shown.
- Prices are quoted by the server. Nothing the browser says about money is believed.
- Tickets are held while somebody is checking out, with a countdown, and released if they wander off
- Guest booking, with no WordPress account needed
- Pay a deposit or pay in full, whichever you make the default
- Sold out and booking-closed states that say why
- Find my booking by code and email: status, amount due, ticket codes, the joining link for an online event, Add to Google Calendar and an
.icsfile - Customers can cancel their own booking, if you switch it on. It is off until you do.
- Rate limiting, a honeypot and a minimum fill time as standard, plus optional Google reCAPTCHA v3 or Cloudflare Turnstile
- A bookings list with search and filters: booking status, payment status, event, date, category, booked between two dates
- Take a booking by hand from the desk, choosing what was paid and how
- A door list per event: search by code, name, email or phone; filter by date, ticket type and who is already inside
- Check people in by typing a code or with a keyboard-wedge barcode scanner. One code is one seat, and it is used once.
- A booking is marked as arrived once its last seat is in
- CSV export of bookings and of attendees, honouring whatever you have filtered
- Customer records built as bookings arrive; a customer who has bookings cannot be deleted by accident
- A payments screen: record a payment, refund it, void it, and read the transaction log for any order
- A workflow builder rather than a fixed set of emails: pick a trigger, add actions, test each one
- 15 triggers, including booking created, status changed, payment received, refunded, attendee checked in, event starts, event ends, date cancelled, date reopened and customer created
- Time offsets on triggers, so a reminder can go three days before the event or an hour after it ends
- Filters on triggers, so a workflow only runs for the status or payment method you mean
- Around 60 merge placeholders across event, booking, customer and attendee, each with a sample
- One-click links in your own email to approve, reject or cancel a booking without logging in
- Three workflows are set up on install: booking confirmation, payment received and booking cancelled
- A queue screen showing what is planned, what ran, what failed and what can be retried
- Mail through
wp_mailor your own SMTP server
- Pay at the door with no gateway and no account: cash, a card machine at the venue, or a bank transfer you mark as paid by hand
- Your own wording for the payment instructions the customer sees
- Orders with lines, totals, what is paid and what is still due
- Refunds, voids, and rules enforced on the server so an order cannot be overpaid or over-refunded
- Drag the payment methods into the order the customer sees them in
- Five shortcodes:
[eventnetic_booking],[eventnetic_events],[eventnetic_calendar],[eventnetic_my_bookings],[eventnetic_thank_you] - The same five as Gutenberg blocks, in their own block category
- The same five as Elementor widgets, in their own widget category
- A calendar with month, week, day and list views, rendered on the server, so it is readable by search engines and works with JavaScript off
- An event catalogue with search, category filters and a "from" price
- Named appearance styles with eight colour tokens and three layout tokens, eight presets to start from, and a style you can pick per shortcode
- Every widget mounts in a shadow root, so no theme can break it and it cannot leak styles out
- Assets load only on pages that actually have a widget on them
- A REST API under
eventnetic/v1, and around 85 actions and filters for extending it - Translation ready, with RTL support
- A setup wizard, a checklist, and a system information panel that checks cron, folders and PHP extensions
- Uninstall removes its tables, its options and its uploads folder. Nothing is left behind.
- Seat maps: draw the room once and reuse it. Rows, tables, stands and standing areas, numbered any way you like. Seats belong to the date, so A7 sells again next week.
- PDF tickets and QR codes: a printable pass per seat, attached to the confirmation email.
- Card payments: Stripe, PayPal, or hand the checkout to WooCommerce.
- Discount codes: percentage or fixed, scoped to certain tickets, with limits and a date range.
- Taxes: percentage or fixed, scoped to a venue, a category or an event.
- Invoices: gapless numbering series, editable templates, issued when the money arrives.
- Waiting lists: offers only the places that actually came free, and the offer expires.
- Repeating dates: one class, ten Tuesdays, each with its own capacity and door list.
- Price per date: a different price, quota or sale window on the dates that need one.
- Custom booking fields: thirteen field types, conditional logic and file uploads.
- Zoom: meetings and webinars, a separate room per date.
- SMS, WhatsApp, Telegram and webhooks: the same workflow builder, more ways to reach people.
安装:
- Upload the plugin through Plugins → Add New → Upload Plugin, or install it from the WordPress plugin directory and activate it.
- A short setup asks for the business name, the currency and how you want to be paid, and offers to create the pages the booking form needs.
- Create an event under Eventnetic → Events, give it at least one ticket type,
and publish the page the setup made. If you would rather place it yourself, put
[eventnetic_booking event="12"]on any page, where 12 is the event id. - Add
[eventnetic_calendar]to a page if you want a calendar of everything that is coming, and[eventnetic_events]for a catalogue people can search.
屏幕截图:
常见问题:
What kinds of events is it for?
Cinemas and film clubs, music venues, theatres, comedy nights, conferences, workshops and classes, guided tours, museums and exhibitions, festivals, meetups, retreats, tastings, markets and fairs, charity dinners, and anything sold as timed entry. Eight of them run as live demos you can book on: a cinema, a theatre, a conference, a music venue, a museum with timed entry, a walking tour, a yoga studio and a craft workshop.
What does it work with?
WordPress 6.4 and up, PHP 8.1 and up. The block editor and Elementor are supported out of the box, and the shortcodes work in any theme or builder that can render one. Optional, and only when you configure them: Google reCAPTCHA v3, Cloudflare Turnstile, and your own SMTP server. On Pro: Stripe, PayPal, WooCommerce, Zoom and Twilio. See integrations.
Does Eventnetic need WooCommerce, a page builder or a form plugin?
No. It is standalone. Everything above happens in Eventnetic itself, with no other plugin installed. WooCommerce is supported on Pro for people who already run a shop and want the checkout to go through it, but it is a choice, not a requirement.
Can I take payment without a payment gateway?
Yes, and most people start that way. "Pay at the door" is switched on during setup and needs no account: cash, a card machine at the venue, or a bank transfer you mark as paid by hand. See payment methods.
Are there per-ticket fees?
None from us, on any plan. If you add Stripe or PayPal later, they charge their own processing fee on each transaction, the same as they would anywhere else. Nothing is taken by Eventnetic. Work out what a per-ticket fee would cost you against a flat yearly licence.
What are the limits of the free version?
There is no limit on events, tickets, bookings or customers. The free plugin holds an event on a single date and takes payment at the door; seat maps, PDF tickets, card gateways, repeating dates and the rest are on Pro. The free and Pro page lists both sides in full.
Does it work with my theme?
Yes. The booking form renders inside a shadow root, so the theme's CSS cannot reach into it and it cannot reach out. It looks the same on every theme, and you set its colours in Eventnetic rather than fighting the theme for them.
Can I check people in at the door?
Yes, in the free plugin. The door list is searchable by name, code, email or phone, and you check somebody in by typing their code or scanning it with a keyboard-wedge barcode scanner. One code is one seat and it is accepted once. Pro adds the printable PDF ticket with a QR code for the scanner to read.
Does it do assigned seating?
On Pro. You draw the room once, with rows, tables, stands and standing areas, and reuse it for every event held there. Seats belong to the date rather than the event, so the same seat can be sold again next week. See seat maps.
Can I sell a class or a season that repeats?
On Pro. A repeating event keeps one page and one set of ticket types, while each date carries its own capacity, its own bookings and its own door list. See repeating dates and courses and passes.
Can I run online events?
The free plugin handles online and hybrid events: you paste the joining link and password, and they are released to ticket holders a set number of minutes before the start. Pro connects Zoom and creates the meeting or webinar for each date itself.
Do customers need a WordPress account?
No. Guest booking is on by default. Afterwards they find their booking with the code
and the email address they used, on the page carrying [eventnetic_my_bookings].
Is it translation ready?
Yes. Both the PHP and the admin application ship .pot files and load a text domain,
and right-to-left languages are supported.
Does it send my data anywhere?
Not by itself. The plugin sends no analytics, no telemetry and no licence checks, and it does not call home. Two optional features contact a third party once you configure them; they are described under External services below.
更新日志:
1.3.1
- The bookings list names the tickets bought beside a package. A family ticket and one more child read as the family ticket alone.
- A negative amount puts its sign in front: -£32.00, not £-32.00. In the admin, on the booking form, and in messages and PDFs.
- At the desk, the discount and Paid now fields start empty, so typing 10 gives 10 rather than 010.
- Duplicate a ticket. The copy keeps its sale window, limits, deposit and the questions asked of each attendee, so the next ticket starts from the last one. The ticket list in the event editor folds up, one row per ticket.
- The booking form in the admin takes a booking the way the public form does, with ticket counts and a summary priced by the server as you go.
- Money at the desk. Record what was paid (cash, card terminal, bank transfer) when the booking is saved, and give a discount of your own, as an amount or a percentage, from Add discount.
- An offline payment method can take a deposit. Switch on Let customers pay a deposit for a bank transfer, and the confirmation page says how much to send now. New keyword for messages: {booking_deposit_due}.
- The confirmation page shows an offline method's payment instructions. A customer paying by bank transfer never saw them after booking.
- The door list has its own place in the menu and a scanner field, and asks before checking somebody in.
- Dates and times follow your site's date and time format everywhere they are shown.
- An evening that runs past midnight ends the next morning, not before it began.
- Bot protection: a Turnstile challenge that needed a click appeared nowhere, so nobody could finish booking. It is shown on screen now.
- Sorting the events list by date showed No events yet.
- After your first booking the dashboard asks, once, for a review on WordPress.org.
- With Eventnetic Pro 1.3.0: courses and passes over several dates, packages that sell tickets together at one price (a family ticket of two adults and two children), a customer panel where a signed-in customer sees their bookings without typing a code, a waiting list per date that holds the place it offers, and a View permission in each module. Pro 1.2 does not work with this version, so update both.
- Writing roles is a paid feature, and went out in the free plugin in 1.2.0 by mistake. The screen for it has moved to Eventnetic Pro on the Elite plan.
- What the free plugin does instead: a staff member given a WordPress account can reach Dashboard, Calendar, Bookings, Customers, Payments and Staff, and may correct a colleague's details but not add or remove anybody. Nothing else is open to them. Administrators are unaffected.
- Closed a hole while doing it. A WordPress user who was neither an administrator nor staff — an Editor, say — matched no rule at all and was allowed everything. They are refused now.
- Staff can sign in. Anybody given an account landed on the WooCommerce My account page instead of the admin, and then on their profile page. They arrive in Eventnetic now.
- Removing sign-in access asked "Delete this staff member?" and promised to unassign them from every event. It says what it does, and asks whether the WordPress user should go too.
- Assigning sign-in access opened with an empty Email even for staff who have one.
- The WordPress button in the header answered 404 where WordPress lives in a subdirectory.
- Permissions. Until now everybody who could open the admin saw all of it. A role says what a person may reach — bookings, events, payments, settings and the rest — and you put staff in it. Administrators are never limited, and a site that writes no roles carries on as before.
- A role can be narrowed to a person's own work: only the bookings they took, only the events they are assigned to. That holds in the lists and when a row is opened directly.
- Holding two roles can only ever take away, never add, so giving somebody a second role cannot undo the first.
- The interface follows the role. The menu, the sidebar and the row actions offer only what that person may open, instead of showing a door that refuses them.
- Staff can be given a WordPress account to sign in with, from the staff screen. If the email already belongs to a user, it says so and offers to link the two rather than failing.
- The Google Calendar button on a confirmation now carries the joining link for an online event, the same as the calendar file already did.
- The date picker is a list now. A weekly series used to spread a dozen cards across the page with the date, the time and what was left landing somewhere different on each one; in rows they line up and can be read down. Nights that have already gone are no longer shown, and a night called off still is, marked Cancelled.
- Nothing shifts while the form loads any more. The date card and the addon steps both used to grow as their answers arrived, moving the buttons out from under whoever was reaching for them.
- Booking forms in the admin: opening an event no longer shows "No location" where a venue is set, or a database id where a category is. Those names come with the event now instead of being fetched a second time.
- Opening an event to edit it no longer counts as changing it — leaving again stopped asking to discard changes nobody made.
- On a booking for a seated event, the Tickets tab stays where it is instead of moving after Attendees a second later.
- The admin menu comes up complete rather than filling in underneath the reader, which used to shuffle the items below whichever one arrived late.
- Switching tabs in a booking, event or payment dialog shows a placeholder while it fetches instead of an empty panel.
- Edit page now works when WordPress lives in a subdirectory — the link was built against the domain root and answered 404 there.
- Signed-in visitors are recognised again. The booking form was not sending WordPress's REST nonce, so the server saw a guest; on a site that requires an account, nobody could book at all.
- Turnstile works. The token was being read the wrong way, so every booking was refused with "Please confirm you are not a robot".
- Signed in? The booking form opens with your name and email already in it, instead of asking for details the site holds. Handy for members-only booking, where everybody booking has an account.
- The page settings only ever offered the first 20 pages, so a site with more could not pick the rest. They are searchable now and the list is no longer capped at a length that hid pages.
- Three strings that were never part of the plugin, left over from its tests, have been taken out of the translation file.
- Translating the plugin now translates all of it. The admin screens kept their strings in a second catalogue that Loco Translate and the other tools could not find, so a finished translation left the interface in English. There is one catalogue now, and one file to translate.
- A translation you place in
wp-content/uploads/eventnetic/languagesis no longer erased by an update. - A page with a booking form on it carries only the strings that form uses, instead of the whole catalogue. About 15KB less on every view once a translation is installed.
- Updates come from WordPress.org. The plugin no longer checks anywhere else.
- First release on the WordPress plugin directory.