Documentation /Changelog
Changelog
Two plugins, released together and numbered together. Entries are tagged [Free] or [Pro] where a change belongs to one of them; an untagged entry is in both. The free plugin updates from the WordPress plugin directory, Pro from your licence.
v1.6.0 - 9 Nov 2026
Both plugins. Pro 1.6.0 needs the free plugin 1.6.0; the free plugin still runs an older Pro. Pro adds two tables for event fields.
Added
- [Free] Every event gets a page of its own kind. The page Eventnetic makes for a new event is an event post rather than a WordPress page: it has the editor, an excerpt, a featured image (the event's cover) and tags, and a theme or page builder can give every event one template and list events on their own. Settings → General settings → Public pages → Event pages sets the address and the name. Events made before keep the pages they have. See Event pages and custom fields.
- [Free] A Public page tab on the event form, just above Settings: create a new page, use a page you already have, or no page for now. A new page is published, not a draft.
- [Free] A page that shows an event's booking form links itself to that event, through the shortcode, the block or a page builder widget, when the event has no published page yet.
- [Pro] Event fields. Fields every event carries, such as a speaker, a level or a featured flag, made in Settings → General settings → Event fields and filled in on the Public page tab. Page builders read them as custom fields, workflows as
{event_cf_<key>}. On every paid plan.
Fixed
- [Free] Twenty Twenty-Five's menu opens in Firefox with Eventnetic active, as does every block that uses the WordPress Interactivity API. The plugin no longer prints an import map of its own on the front end.
- [Free] Statuses in workflow messages are words in your site's language.
{booking_status},{payment_status}and{event_status}say "Approved" or "Not paid" and can be translated. Conditions and webhooks keep the codes. - [Free] The date triggers for your own team say so: "Event starts — for your team" beside "Event starts — for each booking", and a message action on one says it has no customer to write to.
- [Free] When an event is deleted, the page Eventnetic made for it goes to the trash.
v1.5.0 - 4 Nov 2026
The free plugin only; Pro stays at 1.4.3. Nothing in the database changes.
Added
- [Free] Choose when a date shows how many places it has left. Settings → General settings → Bookings → Spots left: on every date, only when few are left (from a number you pick, 5 by default, as before), or never. The booking form and every view of the calendar follow it.
- [Free]
[eventnetic_calendar event="4"]shows only the dates of the events named. Separate several with commas; it combines withcategory.
Fixed
- [Free] Booking works behind caches that also keep the REST API, such as LiteSpeed Cache. Every visitor used to be given the same token, and once it expired nobody could book: "This request could not be verified".
- [Free] The last places on a date can be booked from the site. Holding them used to stop the payment step with "The total could not be confirmed".
- [Free] Busy recurring events save again. An event whose dates together had sold more than its capacity refused every save, even with no date full. The capacity, and a ticket's own limit, are now checked against each date still ahead.
- [Free] The calendar counts places the way the booking form does. A rejected booking no longer holds places, checkout holds count, and an event whose tickets carry their own limits sells out on the calendar too. A rejected booking also stops holding places in the events list and on the dashboard.
- [Free] Close cancelling in Settings → General settings → Bookings hides as soon as cancelling is switched off.
v1.4.4 - 19 Oct 2026
The free plugin only; Pro stays at 1.4.3. Nothing in the database changes.
Fixed
- [Free] Widgets start on page-builder pages. The booking form, the events list and the other widgets start on pages whose layout a page builder keeps outside the post content, such as Bricks, and inside synced patterns. Before, the form stayed empty there.
- [Free] Widgets in popups wear the site's style. A widget that arrives after the page has loaded, in a popup or a tab, now takes its colours from Booking form → Appearance instead of the defaults.
v1.4.3 - 19 Oct 2026
Update the free plugin first, then Pro: Pro 1.4.3 needs the free plugin 1.4.3. Nothing in the database changes.
Fixed
- [Free] A booking paid for online is confirmed by its payment. It used to be confirmed, and announced to the customer, the moment the form was sent, before the card page had even opened. Now it stays pending, and Booking is created workflows wait, until the payment goes through.
- [Free] Abandoned checkouts let their places go, even without cron. When the time in Settings → Bookings → Hold tickets during checkout runs out, the next visitor to open a booking form releases the places, so a site whose WordPress cron never runs no longer keeps them forever. A booking that was never confirmed is let go quietly, without a cancellation email.
- [Free] A late payment is still recorded. If it arrives after the checkout time ran out and the places are still free, the booking goes ahead as if it had been paid on time. If they were taken in the meantime, the booking waits as pending for somebody to decide.
- [Free] A paid deposit is no longer taken back when the checkout time runs out.
- [Pro] Stripe and PayPal stop taking money for bookings that were let go. A Stripe checkout page now stops taking payment after 31 minutes instead of 24 hours, and PayPal no longer captures a payment for a booking that was already released.
Added
- [Free] Workflow trigger: Booking is paid after its time ran out. It fires when a late payment could not simply go ahead, so you can tell the customer and yourself, and decide whether to approve or refund.
v1.4.2 - 18 Oct 2026
The free plugin only; Pro stays at 1.4.1. Nothing in the database changes.
Fixed
- [Free] The booking form wears its style. Background, Corner rounding and the new Inner spacing in Booking form → Appearance now apply to the form itself, the way the style editor's preview shows it, so the form can sit on a coloured page as a panel of its own. Before, it stayed white with square corners whatever the style said. The form keeps 10px of space inside its edges by default.
v1.4.1 - 12 Oct 2026
Nothing in the database changes.
Added
- [Free] Open the booking form on a date or a package.
[eventnetic_booking event="12" date="345"]opens it on that date, andpackage="77"opens it with that package for the dates already chosen, so a page that lists its own dates or course runs can give each row its own Book button. The form element takes the same asdata-eventnetic-dateanddata-eventnetic-package, and a link as?evntc_occurrence=and?evntc_package=. - [Free] How an event is held, in the API. The events list and a single event return
eventMode(venue,onlineorhybrid), and the list takesmode[]to keep only some of them.
Changed
- [Pro] Tickets for some roles only belong to the Pro and Elite plans. On Starter the setting is no longer offered, and the roles a ticket already has keep applying, so a members' rate does not open to everybody.
v1.4.0 - 5 Oct 2026
Update the free plugin first, then Pro: Pro 1.4 needs the free plugin 1.4. Order lines and custom answers now point at their attendee by id, so back up your database first.
Added
- [Pro] Extras per attendee. An extra can be sold once per booking, as before, or for each attendee: a meal, a T-shirt size, an audio guide. Each person picks their own on the booking form, the least and most apply to each of them, and the line says who it is for: on the summary, the invoice, the door list, both CSV exports, the customer's pass and the
{attendee_extras}keyword. - [Pro] Tickets for some roles only. A ticket or package can be sold only to visitors signed in with one of the WordPress roles you choose: a members' rate beside the public one. Everybody else sees it greyed out with who it is for, or, switched to hidden, does not see it at all. The server refuses it too, and the "from" price on event cards leaves it out.
- [Pro] Dates that repeat every year, beside daily, weekly and monthly. A date on 29 February falls only in leap years.
- [Free] Payment methods per event. Switch on Custom payment methods in an event's settings and pick from every method you have set up, including one switched off for the rest of the site: bank transfer for one event, card for another.
- [Free] Workflows ask about payment. A Payment status filter (not paid, partly paid, paid, refunded) on Booking is created, Booking status changes and the reminders sent for each booking, so "five days after booking, if not paid, remind them" is one workflow.
- [Free] Take one attendee off a booking. On the admin booking form, each attendee can be removed on their own, with their answers, extras, check-in and seat. The others keep theirs.
- [Free] The public events list and a single event include the venue's name, for themes and page builders that show it.
Fixed
- [Free] A delayed workflow checks its filters again when it comes due. Somebody who paid on day three no longer gets the day-five reminder, and a reminder for a booking cancelled since is not sent.
- With Turnstile or reCAPTCHA switched on, holding tickets or seats asked for a token that was never sent, so nobody could book.
- [Free] Check-ins survive an edit. Saving a booking from the admin replaced its attendees, so anybody already checked in at the door was checked out again.
- [Free] A ticket bought twice in one booking no longer loses attendees when the booking is saved.
- [Free] A booking form opened in a popup, or added after the page loaded, treated signed-in visitors as guests and refused their bookings.
- [Pro] Custom answers given at the desk are kept. Saving wiped the answers of attendees whose panel had not been opened.
- [Pro] A package and a loose ticket of the same kind (a family ticket and one more child) no longer share an attendee on the booking form, where their answers collided and Continue could hang.
- [Pro] An extra bought for several nights no longer multiplies its quantity when the booking is edited.
- [Pro] An extra ordered outside its least or most is refused with a message instead of dropped without one.
- [Pro] A cancelled or rejected booking gives back the extras stock it held.
v1.3.1 - 29 Sep 2026
Fixed
- [Free] The bookings list names the tickets bought beside a package. A family ticket and one more child read as the family ticket alone.
- [Free] 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.
- [Free] At the desk, the discount and Paid now fields start empty, so typing 10 gives 10 rather than 010.
Pro 1.3.1 has no changes of its own. It keeps the two plugins on one number.
v1.3.0 - 28 Sep 2026
Update both plugins together. Pro 1.2 does not work with the free plugin 1.3, and Pro 1.3 waits for the free plugin to reach 1.3 before it starts. This release moves each booking's dates into a table of their own, so back up your database first.
Added
- [Pro] Courses and passes. A booking can cover more than one date. A ticket can be for every date of the run, for dates you name, or for any number of dates the buyer picks, and an event can let one booking take several of its dates, each charged. Seats, the door list, reminders and the customer's own page all read the dates a booking covers.
- [Pro] Packages. Sell tickets together at one price: a family ticket of two adults and two children. A package holds no seats of its own. The tickets inside it do, so a room is counted once however a seat was sold, and a package shows as sold out when one of its tickets is.
- [Pro] Packages for the evenings. The whole course, the dates you name, or any two of the run, offered above the dates. An event sold only as packages asks for a package instead of a date, and a ticket only a package sells asks nothing the package decides.
- [Pro] A date can have its own name and room: lesson three, in the other hall. It shows wherever the date does.
- [Pro] Seat maps over several dates (Elite). A booking for several evenings keeps the same chair on each of them, and the map shows only the seats that are free on every evening chosen.
- [Free] Duplicate a ticket. Tickets on one event usually differ in a line or two, so a ticket can copy itself. The copy lands under the original with its sale window, limits, deposit, the questions asked of each attendee and the PDF template, and opens for its new name. What belongs to the original alone stays with it: prices on particular dates and its seat category.
- [Free] The admin booking form takes a booking the way the public form does. Ticket counts with plus and minus, packages and the dates of a series (Pro), and a summary priced by the server as you go, the same total the order will hold. Changing the event says it is asking and never shows the last event's tickets meanwhile.
- [Free] Money at the desk. Record what was paid, and how (cash, card terminal, bank transfer), when the booking is saved. Give a discount of your own, as an amount or a percentage, from Add discount. [Pro] A discount code is offered from the same menu.
- [Free] A deposit by bank transfer. An offline method can take a deposit: switch on Let customers pay a deposit. The confirmation page says how much to send now, and messages can say it too with
{booking_deposit_due}. - [Pro] A customer panel (Pro and Elite plans). A customer who is signed in opens My bookings and sees their bookings listed, with no code or email to type. A course shows its evenings and which are behind them. Under Settings, General, Customer panel every customer can be given a WordPress account when they book, and the customers list gives one to anybody by hand. Bookings made as a guest are left out on purpose: an email address proves nothing about who is signed in.
- [Pro] A waiting list per date (Pro and Elite plans). Somebody can wait for the one evening that is full, or for a package, and the place they are offered is held for them until they take it or the offer runs out. Their link opens the event with that date ticked.
- [Free] The door list has a place of its own in the menu and a scanner field. It scans first and asks only when it has to, and asks before checking somebody in. [Pro] On a course a ticket is let in once each evening.
- [Pro] Permissions (Elite) show View in each module, and the box in a module's header selects everything in it. Granting Add, Edit or Delete grants View with it.
- [Free] After your first booking the dashboard asks, once, for a review on WordPress.org.
Changed
- [Free] Dates and times follow your site's date and time format everywhere they are shown.
- [Free] The ticket list in the event editor folds up. Each ticket is a row that opens when you need it, and says what it is while it is shut.
- [Free] The events list says what each event has taken and how many places have gone. The slots column shows one evening, not a series added up.
- [Free] The booking dialog reads a booking date by date, and the bookings list says what each booking holds.
- [Pro] The discount code sits inside the price summary, compact.
- [Pro] A date's own details (name, room, start time, seats and prices) are edited in the Recurring tab, one row per date.
Fixed
- [Free] Bot protection: a Turnstile challenge that needed a click appeared nowhere, so nobody could finish booking. It is shown on screen now.
- [Free] The confirmation page shows an offline method's payment instructions. A customer paying by bank transfer never saw them after booking.
- [Free] Sorting the events list by date showed No events yet.
- [Free] An evening that runs past midnight ends the next morning, not before it began.
- [Free] An event's capacity covers every ticket, those with limits of their own included.
- [Pro] Editing a package booking at the desk kept its package and its price instead of pricing it at nothing.
- [Free] Delete in a row's menu no longer opens the event's details as well, and an upcoming event on the dashboard opens its details rather than its editor.
- [Pro] Saving a role with any permission in it ended in a critical error.
- [Pro] The waiting list on a series counted every date's bookings against one date's seats, so a place that came free was never offered.
v1.2.1 - 21 Sep 2026
Changed
- Permissions is an Elite feature. It went out in the free plugin in 1.2.0 by mistake. The screen for writing roles has moved to Pro on the Elite plan.
- [Free] A staff member with a WordPress account reaches a fixed set instead: Dashboard, Calendar, Bookings, Customers, Payments and Staff. They may correct a colleague's details but not add or remove anybody. Administrators are unaffected, on any plan.
Fixed
- [Free] 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.
- [Free] Staff could not reach the admin. Anybody given an account landed on the WooCommerce My account page, and then on their profile. They arrive in Eventnetic now.
- [Free] 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.
- [Free] Assigning sign-in access opened with an empty Email even for staff who have one.
- [Free] The WordPress button in the header answered 404 where WordPress lives in a subdirectory.
v1.2.0 - 21 Sep 2026
Added
- [Free] Permissions. Everybody who could open the admin used to see all of it. Now a role says what a person may reach — bookings, events, payments, settings and the rest — and you put staff in it. A role can be narrowed further to that person's own work: only the bookings they took, only the events they are assigned to, in the lists and when a row is opened directly. Holding two roles can only take away, never add, so a second role cannot undo the first. The interface follows the role, offering only the doors that will open. Administrators are never limited, and a site that writes no roles carries on exactly as before.
- [Free] A WordPress account for a staff member, made from the staff screen. If the email already belongs to a user, it says so and offers to link the two rather than failing.
Fixed
- [Free] The Add to Google Calendar button on a confirmation now carries the joining link for an online event. The calendar file already did; the button sent people to the address instead.
v1.1.0 - 21 Sep 2026
Added
- [Pro] Extras. Sell what goes with the ticket — a glass of champagne on arrival, a parking space, a programme. Each one has a price, a picture and its own stock, and is offered on the events or categories you choose; leave both empty and it is on sale everywhere. Two limits, either or both: a number per date, which comes back each night, and a number in total, which runs out for good. What is left is worked out from the bookings that sold it, so a cancellation hands its stock back without anyone remembering to. The visitor picks them in a step of their own, the desk picks them on the booking form, and they appear on the order, the invoice, the email and the booking's own tab.
Changed
- [Free] The date picker is a list. 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 read down. Dates that have already gone are no longer offered; one called off still is, marked Cancelled.
- Seat maps are an Elite feature.
Fixed
- [Free] Signed-in visitors were treated as guests. The booking form was not sending WordPress's REST nonce, so the server never saw the login — and on a site that requires an account, nobody could book at all.
- [Free] Turnstile refused every booking. The token was read from the wrong place, so an empty answer reached the server and it asked the customer to confirm they were not a robot.
- [Free] Edit page gave a 404 where WordPress lives in a subdirectory. The link was built against the domain root instead of being asked for.
- [Free] An event's Location read "No location" while the form loaded, and its categories and staff read as database ids. Those names arrive with the event now.
- [Free] Opening an event no longer counts as editing it — leaving again asked to discard changes nobody had made.
- [Free] On a seated event the Tickets tab stayed where it was instead of moving after Attendees a second later.
- [Free] The admin menu comes up whole rather than filling in underneath the reader and shifting what was under the cursor.
- [Free] A booking, event or payment dialog shows a placeholder while a tab fetches, instead of an empty panel.
- [Free] Neither the date card nor an addon's step moves the buttons any more while it loads.
- [Pro] Saving a booking for a seated event was refused with "One of your seats is no longer available" — including a save that changed nothing. A confirmed booking's own chairs were being counted against it.
v1.0.2 - 19 Sep 2026
Added
- [Free] A signed-in visitor's booking form opens with their name and email already in it, taken from their WordPress account. The phone number comes from an earlier booking if they have made one. Anything they type themselves is left alone. Useful where booking is for members only and everybody booking already has an account.
Fixed
- [Free] The page settings offered only the first 20 pages, so a site with more of them could not pick the rest. The fields search now, and the list is no longer capped at a length that hid pages.
- [Free] Three strings that are not part of the plugin, left behind by its tests, were in the file translators work from. They have been taken out.
v1.0.1 - 18 Sep 2026
Fixed
- [Free] 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.
- [Pro] Pro can be translated at all. Its strings were loaded, filtered and sent to the browser, then read by nothing, because the lookup only consulted an add-on's catalogue when explicitly asked and no part of Pro asked. Pro has never appeared in any language until now.
- A translation placed in
wp-content/uploads/eventnetic/languagesis no longer erased by an update.
Improved
- A page carrying a booking form now loads only the strings that form uses, instead of the whole catalogue. Around 15KB less on every view once a translation is installed.
- [Free] Updates come from WordPress.org. The plugin no longer checks anywhere else.
v1.0.0 - 16 Sep 2026
Added
- [Free] First release on the WordPress plugin directory.
- [Free] Events with single, multi-day and full-day dates, capacity, ticket types, deposits and per-attendee details.
- [Free] A booking form, an event catalogue and a calendar with month, week, day and list views, each available as a shortcode, a block and an Elementor widget.
- [Free] Bookings, a searchable door list, check-in by code or barcode scanner, CSV exports and customer records.
- [Free] A workflow builder with 15 triggers and your own emails.
- [Free] Payment at the door: cash, a card machine or a bank transfer.
- [Pro] Seat maps, PDF tickets with QR codes, and Stripe, PayPal and WooCommerce payments.
- [Pro] Discount codes, taxes, invoices, waiting lists, repeating dates and a price per date.
- [Pro] Custom booking fields, Zoom meetings and webinars, and SMS, WhatsApp, Telegram and webhook notifications.