A page of their own for every booking, guest cancellation, refunds, invoices\nand credit notes, your own email texts, and questions for your guests. New\ncolumns and two new tables: back up first. Guest cancellation and invoices\nstay off until you turn them on.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3697091,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3697091,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500-ar.png":{"filename":"banner-1544x500-ar.png","revision":3704268,"resolution":"1544x500","location":"assets","locale":"ar","width":1544,"height":500},"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3704268,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250-ar.png":{"filename":"banner-772x250-ar.png","revision":3704268,"resolution":"772x250","location":"assets","locale":"ar","width":772,"height":250},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3704268,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.8","1.0.9","1.10.0","1.10.1","1.11.0","1.12.18","1.13.12","1.14.4","1.15.7","1.2.0","1.2.1","1.2.2","1.8.7","1.9.0","1.9.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3694201,"resolution":"1","location":"assets","locale":"","width":1520,"height":639},"screenshot-10.png":{"filename":"screenshot-10.png","revision":3719801,"resolution":"10","location":"assets","locale":"","width":1568,"height":677},"screenshot-11.png":{"filename":"screenshot-11.png","revision":3719801,"resolution":"11","location":"assets","locale":"","width":1280,"height":900},"screenshot-12.png":{"filename":"screenshot-12.png","revision":3719801,"resolution":"12","location":"assets","locale":"","width":1280,"height":960},"screenshot-13.png":{"filename":"screenshot-13.png","revision":3719801,"resolution":"13","location":"assets","locale":"","width":1568,"height":676},"screenshot-14.png":{"filename":"screenshot-14.png","revision":3727725,"resolution":"14","location":"assets","locale":"","width":1350,"height":1063},"screenshot-15.png":{"filename":"screenshot-15.png","revision":3727725,"resolution":"15","location":"assets","locale":"","width":1600,"height":1375},"screenshot-16.png":{"filename":"screenshot-16.png","revision":3727725,"resolution":"16","location":"assets","locale":"","width":1600,"height":1250},"screenshot-17.png":{"filename":"screenshot-17.png","revision":3727725,"resolution":"17","location":"assets","locale":"","width":1600,"height":1250},"screenshot-18.png":{"filename":"screenshot-18.png","revision":3727725,"resolution":"18","location":"assets","locale":"","width":1600,"height":1250},"screenshot-19.png":{"filename":"screenshot-19.png","revision":3727725,"resolution":"19","location":"assets","locale":"","width":1800,"height":1140},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3694201,"resolution":"2","location":"assets","locale":"","width":1520,"height":639},"screenshot-20.png":{"filename":"screenshot-20.png","revision":3727725,"resolution":"20","location":"assets","locale":"","width":1753,"height":669},"screenshot-21.png":{"filename":"screenshot-21.png","revision":3727725,"resolution":"21","location":"assets","locale":"","width":1153,"height":513},"screenshot-22.png":{"filename":"screenshot-22.png","revision":3739907,"resolution":"22","location":"assets","locale":"","width":1624,"height":1256},"screenshot-23.png":{"filename":"screenshot-23.png","revision":3739907,"resolution":"23","location":"assets","locale":"","width":1697,"height":532},"screenshot-24.png":{"filename":"screenshot-24.png","revision":3739907,"resolution":"24","location":"assets","locale":"","width":1500,"height":634},"screenshot-25.png":{"filename":"screenshot-25.png","revision":3739907,"resolution":"25","location":"assets","locale":"","width":1656,"height":994},"screenshot-26.png":{"filename":"screenshot-26.png","revision":3739907,"resolution":"26","location":"assets","locale":"","width":1697,"height":717},"screenshot-27.png":{"filename":"screenshot-27.png","revision":3739907,"resolution":"27","location":"assets","locale":"","width":1400,"height":1530},"screenshot-28.png":{"filename":"screenshot-28.png","revision":3739907,"resolution":"28","location":"assets","locale":"","width":1697,"height":1768},"screenshot-29.png":{"filename":"screenshot-29.png","revision":3760450,"resolution":"29","location":"assets","locale":"","width":1536,"height":3566},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3694201,"resolution":"3","location":"assets","locale":"","width":1520,"height":639},"screenshot-30.png":{"filename":"screenshot-30.png","revision":3760450,"resolution":"30","location":"assets","locale":"","width":1440,"height":516},"screenshot-31.png":{"filename":"screenshot-31.png","revision":3760450,"resolution":"31","location":"assets","locale":"","width":1920,"height":1010},"screenshot-32.png":{"filename":"screenshot-32.png","revision":3760450,"resolution":"32","location":"assets","locale":"","width":1924,"height":1854},"screenshot-33.png":{"filename":"screenshot-33.png","revision":3760450,"resolution":"33","location":"assets","locale":"","width":1242,"height":962},"screenshot-34.png":{"filename":"screenshot-34.png","revision":3760450,"resolution":"34","location":"assets","locale":"","width":1924,"height":2646},"screenshot-35.png":{"filename":"screenshot-35.png","revision":3760450,"resolution":"35","location":"assets","locale":"","width":1924,"height":2594},"screenshot-36.png":{"filename":"screenshot-36.png","revision":3760450,"resolution":"36","location":"assets","locale":"","width":1044,"height":2856},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3694201,"resolution":"4","location":"assets","locale":"","width":1520,"height":639},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3694201,"resolution":"5","location":"assets","locale":"","width":1520,"height":479},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3694201,"resolution":"6","location":"assets","locale":"","width":1520,"height":639},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3694201,"resolution":"7","location":"assets","locale":"","width":1520,"height":639},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3694201,"resolution":"8","location":"assets","locale":"","width":1552,"height":660},"screenshot-9.png":{"filename":"screenshot-9.png","revision":3694201,"resolution":"9","location":"assets","locale":"","width":1552,"height":651}},"screenshots":{"1":"The event assistant. Fifteen kinds of night, drawn rather than listed \u2014 pick the one that looks like your room, and every answer from there decides the next question. The panel on the right builds the room as you go, and shows the prices the booking page will show and the line the ticket will print. It refuses to rebuild a room that already has bookings.","2":"The room builder. Describe the room in numbers \u2014 rows, tables to a row, chairs to a table, levels \u2014 or draw it: drag a stage in, rectangle-select a whole row, shift-click, align, space evenly, nudge with the arrow keys. The plan you draw is the plan the guest picks from and the one you watch on the night.","3":"Prices & places, on one panel. What a ticket will say, how places are given out, the levels, and each part of the room with the price category it is sold as and the first places it hands out. The capacity is counted from the room, not typed beside it.","4":"The booking page. One shortcode on any page. It asks for the name of every person coming \u2014 five names for a booking of five \u2014 and it knows what is left while the form is being filled in, counting the lines above and the other people booking at the same moment.","5":"The floor, on the night. Every part of the room on one screen, filling in real time, with three facts kept apart: sold, seated, and arrived. The pale bar is what has been sold; the solid one inside it is who has walked in.","6":"The door check-in station. A web page on any phone, opened with a per-event door code \u2014 no app to install. Camera, photo or keypad, a live count of who is inside, and one screen per scan: let in, already inside, or not for tonight.","7":"Every ticket issued. One per guest, with its own serial and its own QR code, the place it carries, and whether that guest has walked through the door \u2014 with the minute and the entrance they came in by.","8":"The control room. Every event, what has sold, what is still waiting on a payment, who has arrived \u2014 and the shortcode for the event you are looking at, ready to paste.","9":"Help, inside the plugin. The whole guide on the screen where you are stuck: a first event in ten minutes, then the assistant, the room, payment, tickets, the night, and what to do when something does not arrive. Every step links to the screen it talks about.","10":"Dates that repeat. One event, every Friday: each date keeps its own bookings, capacity and door. Change one date, this one and the following, or all of them \u2014 a date somebody has booked is never moved with the others.","11":"The guest chooses the date. A series shows its dates on the booking page, and the one chosen travels to the emails, the ticket and the calendar file.","12":"The door works one date at a time. A ticket for another Friday is refused as \"Not tonight\", and the screen says which date it is for.","13":"Online and hybrid events. Every guest gets a personal join link that goes through your site and is checked when clicked, so the meeting link can change at any time. You choose who gets it, and when the room opens.","14":"The agenda, month view. Every date of every event in its day, each with its own state; switch to compact, large or list, go to a date, keep only some events or one category.","15":"The agenda as a grid of cards. The picture on top, the price, the state, the category, a button to book \u2014 and add to my calendar, and share.","16":"The page of an event. Your theme's look or the Classic one: the path from the list of events, the picture, the date and the place, the categories, the booking form below. Each date of a series has its own page.","17":"A category's page. Its picture, its words and only its events \u2014 the agenda filtered for it, with the categories under it.","18":"A venue's page. The address, the map, the website, a few words, and the events to come there.","19":"Your own agenda. Every state, drafts included, what the site shows and what it hides, how full each night is. Drag a night to another day; change several at once.","20":"Cards and colours. Rows or a grid, the size of the pictures, the corners and the colour of each state, with a sample that changes as you choose.","21":"Categories. A tree of families, each with a colour, a picture and its own page; ticked on each event.","22":"A full date keeps its guests. Under \"sold out\", the waiting list: a name, an email, how many places. A freed place is held for the first in line.","23":"The waiting list of each date: who waits, in which order, whose place is held until when. Offer a place by hand, take somebody off, export.","24":"Sale dates and a minimum. An early bird whose sale has ended stays on the page, greyed, with the reason; a group category says its minimum.","25":"On each category: on sale from, until, and the minimum per booking \u2014 and the event's own waiting list, beside it.","26":"Reminders, per event: the site's, its own, or none; and the link where guests can review the event the morning after.","27":"A reminder the day before, in the guest's language: the night, the venue and the way there.","28":"Messages to participants. Choose who, write once, see it as they will, send yourself a test, then send in batches. Nothing tracks who opens it.","29":"The guest's own page, opened by the signed link in every email: where the booking stands, each guest and their ticket \u2014 one who left with a refund \u2014 the invoice and its credit note, and what happened when.","30":"A guest cancels, if you allow it: a question first, with what it means. Their places go back on sale; a payment is not refunded on its own.","31":"A booking and its money, in one word: paid, awaiting payment, cancelled but paid, refunded \u2014 and how much was given back.","32":"Refunds, on a booking's screen: by card through Stripe or recorded when made elsewhere, for the guests who leave or an amount alone. Below, the invoice and its credit note.","33":"An invoice, when you turn them on: your name and legal details, the categories sold, VAT included at your rate, and the answers marked for the invoice.","34":"The words of an email, in each language: the subject, the title and the first paragraph, previewed as a guest will receive it. The plugin writes the rest.","35":"Questions for your guests: a menu for everyone, a child's age only in the Child category, a company asked once per booking for the invoice.","36":"The booking page asks them: the second guest, in the Child category, gets their own question; the questions asked once come before confirming."}},"plugin_section":[],"plugin_tags":[4745,1486,1373,603,4771],"plugin_category":[40,58],"plugin_contributors":[278878],"plugin_business_model":[],"class_list":["post-361265","plugin","type-plugin","status-publish","hentry","plugin_tags-event-calendar","plugin_tags-events","plugin_tags-qr-code","plugin_tags-registration","plugin_tags-tickets","plugin_category-calendar-and-events","plugin_category-user-management","plugin_contributors-bitforgenet","plugin_committers-bitforgenet"],"banners":{"banner":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/banner-772x250.png?rev=3704268","banner_2x":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/banner-1544x500.png?rev=3704268","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/icon-128x128.png?rev=3697091","icon_2x":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/icon-256x256.png?rev=3697091","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-1.png?rev=3694201","caption":"The event assistant. Fifteen kinds of night, drawn rather than listed \u2014 pick the one that looks like your room, and every answer from there decides the next question. The panel on the right builds the room as you go, and shows the prices the booking page will show and the line the ticket will print. It refuses to rebuild a room that already has bookings."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-2.png?rev=3694201","caption":"The room builder. Describe the room in numbers \u2014 rows, tables to a row, chairs to a table, levels \u2014 or draw it: drag a stage in, rectangle-select a whole row, shift-click, align, space evenly, nudge with the arrow keys. The plan you draw is the plan the guest picks from and the one you watch on the night."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-3.png?rev=3694201","caption":"Prices & places, on one panel. What a ticket will say, how places are given out, the levels, and each part of the room with the price category it is sold as and the first places it hands out. The capacity is counted from the room, not typed beside it."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-4.png?rev=3694201","caption":"The booking page. One shortcode on any page. It asks for the name of every person coming \u2014 five names for a booking of five \u2014 and it knows what is left while the form is being filled in, counting the lines above and the other people booking at the same moment."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-5.png?rev=3694201","caption":"The floor, on the night. Every part of the room on one screen, filling in real time, with three facts kept apart: sold, seated, and arrived. The pale bar is what has been sold; the solid one inside it is who has walked in."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-6.png?rev=3694201","caption":"The door check-in station. A web page on any phone, opened with a per-event door code \u2014 no app to install. Camera, photo or keypad, a live count of who is inside, and one screen per scan: let in, already inside, or not for tonight."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-7.png?rev=3694201","caption":"Every ticket issued. One per guest, with its own serial and its own QR code, the place it carries, and whether that guest has walked through the door \u2014 with the minute and the entrance they came in by."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-8.png?rev=3694201","caption":"The control room. Every event, what has sold, what is still waiting on a payment, who has arrived \u2014 and the shortcode for the event you are looking at, ready to paste."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-9.png?rev=3694201","caption":"Help, inside the plugin. The whole guide on the screen where you are stuck: a first event in ten minutes, then the assistant, the room, payment, tickets, the night, and what to do when something does not arrive. Every step links to the screen it talks about."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-10.png?rev=3719801","caption":"Dates that repeat. One event, every Friday: each date keeps its own bookings, capacity and door. Change one date, this one and the following, or all of them \u2014 a date somebody has booked is never moved with the others."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-11.png?rev=3719801","caption":"The guest chooses the date. A series shows its dates on the booking page, and the one chosen travels to the emails, the ticket and the calendar file."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-12.png?rev=3719801","caption":"The door works one date at a time. A ticket for another Friday is refused as \"Not tonight\", and the screen says which date it is for."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-13.png?rev=3719801","caption":"Online and hybrid events. Every guest gets a personal join link that goes through your site and is checked when clicked, so the meeting link can change at any time. You choose who gets it, and when the room opens."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-14.png?rev=3727725","caption":"The agenda, month view. Every date of every event in its day, each with its own state; switch to compact, large or list, go to a date, keep only some events or one category."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-15.png?rev=3727725","caption":"The agenda as a grid of cards. The picture on top, the price, the state, the category, a button to book \u2014 and add to my calendar, and share."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-16.png?rev=3727725","caption":"The page of an event. Your theme's look or the Classic one: the path from the list of events, the picture, the date and the place, the categories, the booking form below. Each date of a series has its own page."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-17.png?rev=3727725","caption":"A category's page. Its picture, its words and only its events \u2014 the agenda filtered for it, with the categories under it."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-18.png?rev=3727725","caption":"A venue's page. The address, the map, the website, a few words, and the events to come there."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-19.png?rev=3727725","caption":"Your own agenda. Every state, drafts included, what the site shows and what it hides, how full each night is. Drag a night to another day; change several at once."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-20.png?rev=3727725","caption":"Cards and colours. Rows or a grid, the size of the pictures, the corners and the colour of each state, with a sample that changes as you choose."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-21.png?rev=3727725","caption":"Categories. A tree of families, each with a colour, a picture and its own page; ticked on each event."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-22.png?rev=3739907","caption":"A full date keeps its guests. Under \"sold out\", the waiting list: a name, an email, how many places. A freed place is held for the first in line."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-23.png?rev=3739907","caption":"The waiting list of each date: who waits, in which order, whose place is held until when. Offer a place by hand, take somebody off, export."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-24.png?rev=3739907","caption":"Sale dates and a minimum. An early bird whose sale has ended stays on the page, greyed, with the reason; a group category says its minimum."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-25.png?rev=3739907","caption":"On each category: on sale from, until, and the minimum per booking \u2014 and the event's own waiting list, beside it."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-26.png?rev=3739907","caption":"Reminders, per event: the site's, its own, or none; and the link where guests can review the event the morning after."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-27.png?rev=3739907","caption":"A reminder the day before, in the guest's language: the night, the venue and the way there."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-28.png?rev=3739907","caption":"Messages to participants. Choose who, write once, see it as they will, send yourself a test, then send in batches. Nothing tracks who opens it."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-29.png?rev=3760450","caption":"The guest's own page, opened by the signed link in every email: where the booking stands, each guest and their ticket \u2014 one who left with a refund \u2014 the invoice and its credit note, and what happened when."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-30.png?rev=3760450","caption":"A guest cancels, if you allow it: a question first, with what it means. Their places go back on sale; a payment is not refunded on its own."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-31.png?rev=3760450","caption":"A booking and its money, in one word: paid, awaiting payment, cancelled but paid, refunded \u2014 and how much was given back."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-32.png?rev=3760450","caption":"Refunds, on a booking's screen: by card through Stripe or recorded when made elsewhere, for the guests who leave or an amount alone. Below, the invoice and its credit note."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-33.png?rev=3760450","caption":"An invoice, when you turn them on: your name and legal details, the categories sold, VAT included at your rate, and the answers marked for the invoice."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-34.png?rev=3760450","caption":"The words of an email, in each language: the subject, the title and the first paragraph, previewed as a guest will receive it. The plugin writes the rest."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-35.png?rev=3760450","caption":"Questions for your guests: a menu for everyone, a child's age only in the Child category, a company asked once per booking for the invoice."},{"src":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/screenshot-36.png?rev=3760450","caption":"The booking page asks them: the second guest, in the Child category, gets their own question; the questions asked once come before confirming."}],"raw_content":"\n
Events & Tickets<\/strong> runs the evening from the first booking to the last guest\nthrough the door. It was built for clubs, bars and party promoters \u2014 the people\nfor whom an event is a door, a list, and a queue outside \u2014 and it has since been\nused for seated dinners, concerts, conferences and weddings, because they are\nthe same problem wearing different clothes.<\/p>\n\n Nothing is capped and nothing is metered. There is no per-ticket fee, no\nexternal service to sign up for, no account to create, and no telemetry. Your\nguest list lives in your own database, on your own server.<\/p>\n\n English, French, Spanish, Portuguese, German, Italian and Arabic<\/strong> \u2014 not a\npromise that somebody will translate it one day, but seven finished catalogues in\nthe download.\nInstall it and it is already in your language.<\/p>\n\n It works the language out for itself.<\/strong> Whatever WordPress is set to, the\nplugin follows \u2014 and it follows by language rather than by locale, so Everything is translated, not just the buttons.<\/strong> The booking form the guest\nfills in, the emails they receive, the words printed on the ticket itself, the\ndoor station held at the entrance, and the admin screens you work in. Dates too \u2014\nthe month and the weekday come out of the plugin's own catalogue rather than\nWordPress's, so a French ticket does not print September<\/em> under a French\nheading on an English site.<\/p>\n\n Arabic really is Arabic.<\/strong> The screens, the emails and the booking form read\nright to left. And the ticket \u2014 which is a drawn image, not a web page \u2014 is drawn\nwith an Arabic typeface that travels with the plugin, with the letters joined the\nway Arabic joins them and the line put in reading order. A time, a price, a table\nnumber or a ticket reference still runs the other way inside the sentence, as it\nshould. Most plugins that claim Arabic print a row of disconnected letters\nbackwards on the one thing the guest actually holds.<\/p>\n\n The language travels with the booking.<\/strong> A guest who booked in Spanish gets\ntheir ticket in Spanish \u2014 including a ticket re-sent months later, from a screen\nyou are reading in French. And your own words stay yours: event titles, venue\nnames, payment instructions and the success message are your text, and the plugin\nwill not rewrite them.<\/p>\n\n An agenda your guests can use.<\/strong> One shortcode, one block in the editor or\none Elementor widget, and your events are on a calendar: Compact<\/em> (a dot a\nnight), Month<\/em> (the time and the title in each day), Large<\/em> (the picture of\neach night) and List<\/em>, in rows or as a grid of cards. It shows dates, not\nevents \u2014 every date of a series in its day, each with its own state: open, few\nplaces left, sold out, closed, cancelled. Guests go to a date, keep only the\nevents they care about or one category, add a night to their calendar and\nshare it. The month they open comes with the page; the next one is asked for\nwhen they turn to it. Without JavaScript, it is a list of links search engines\ncan follow.<\/p>\n\n Shaped from one screen.<\/strong> The view it opens on, the views on offer, the\nnumber of nights a day, the pictures and their size, rows or a grid, the\ncorners, the colour of each state, your theme's style or its own \u2014 with a\nsample beside the settings that changes as you choose, before you save.<\/p>\n\n A page for every event, and for every date.<\/strong> One page lists every event to\ncome, and under its address each event has its own: Categories, venues and organizers, each with a page.<\/strong> Sort events into\nfamilies \u2014 Jazz under Concerts \u2014 each with a colour, a picture and a few words.\nGuests filter the agenda by category, and every category, every venue and every\norganizer has its own page with its own events to come. A venue's page shows\nthe address, the map and the website; an organizer's, the logo and the links \u2014\nnever their email address or phone.<\/p>\n\n Your own agenda, to run the season.<\/strong> Under Events, a calendar for whoever\nruns the events: every state, drafts included, what the site shows and what it\nhides, how full each night is. Year, month, week or list; filters and a search.\nDrag a night onto another day to move it; change the state of one event or of\nseveral at once; start a new event from the day it falls on. A night somebody\nhas booked never moves from there.<\/p>\n\n Found by search engines.<\/strong> Every event page describes its date, its place, its\nline-up and its prices in the structured data search engines read; a date of a\nseries says which series it belongs to, and the page of a series lists every\ndate on sale. Category, venue and organizer pages describe themselves too, and\nevery page carries the breadcrumb from the list of events.<\/p>\n\n A full date keeps the people it would have turned away.<\/strong> Under \"sold out\",\nthe page offers to join the waiting list. When a place comes free \u2014 a\ncancellation, a refund, a payment that ran out, a capacity you raised \u2014 it is\nheld for the first person in line, who gets a link to book it. Nobody else can\nbuy it in the meantime; if they do not book in time, it goes to the next\nperson. Not \"first to click wins\": first in line, for real. How long a place\nis held is yours to set, and shortens on its own close to the date.<\/p>\n\n Each category sells when you say.<\/strong> An early bird that closes on the 1st, a\ndoor price that opens on the day, a table sold by four: sale dates and a\nminimum per booking on each category. A category outside its dates stays on\nthe page, greyed, with the reason, rather than vanishing; the server refuses\nit whatever the browser sends.<\/p>\n\n Reminders that bring people in.<\/strong> The day before and two hours before by\ndefault \u2014 a week before and the morning after if you want them \u2014 in the\nlanguage each guest booked in, with the doors, the address, the online link\nand a fresh link to every ticket. Each one goes once and only once. The\nmorning after thanks them, offers the next date and, if you give one, the link\nwhere they can review your event.<\/p>\n\n Write to everybody who booked.<\/strong> One date or all, one category or all,\nconfirmed, waiting for payment, came in or did not: preview it, send yourself a\ntest, then send. One email per address, in batches your host accepts, with a\nrecord of every one. Nothing tracks who opens it.<\/p>\n\n Every booking has a page of its own.<\/strong> Each email about a booking ends with\na link to the guest's own page \u2014 no account, no password: where the booking\nstands, every guest and their ticket to download, the venue, the way into the\nonline room, the invoice, and what happened when. A guest who has lost their\nemails types the address they booked with and receives the links there; the\npage never says whether an address has booked.<\/p>\n\n Guests can cancel, if you let them.<\/strong> Off unless you turn it on, for the site\nor one event, until 48 hours before the date or the deadline you choose. The\nguest cancels the whole booking from their page, after a question: its tickets\nstop opening the door, its places go back on sale and the waiting list is\nserved. The money stays where it is: refunds are yours to make, in one click.<\/p>\n\n A booking and its money are two facts.<\/strong> A booking is pending, confirmed,\ncancelled or expired; its money is due, paid or refunded. A paid booking you\ncancel keeps its money until you decide \u2014 Cancelled \u2014 paid<\/em> \u2014 and a payment\nthat arrives late never reopens a booking somebody cancelled.<\/p>\n\n Refunds that give the money back.<\/strong> From the booking's screen: by card,\nthrough Stripe, back to the card that paid \u2014 or recorded, when you gave it back\nby transfer or in cash. All of it or part: the guests you tick leave the\nbooking, their tickets stop working and their places go back on sale, and the\nguest is told what was refunded, how, and who is no longer coming. A refund\nhere is money returned, not a word changed on the booking.<\/p>\n\n Invoices and credit notes, when you turn them on.<\/strong> Two series without a gap,\nissued as the money moves: an invoice when a payment is confirmed, a credit\nnote when money goes back. Your name, your legal details, VAT none or included\nin the price, in your site's language; an A4 PDF attached to the email and kept\non the guest's page; every document as a spreadsheet for your accountant. The\nplugin follows your settings, not a tax law: what your invoices must say is\nyours to check.<\/p>\n\n Your words in the emails.<\/strong> The subject, the title and the first paragraph of\neach of the nineteen emails a guest can receive, in each language, with\n {first_name}, Questions for your guests.<\/strong> A menu, a size, a company to invoice: each\nquestion is asked of every guest or once per booking, in the ticket categories\nit concerns \u2014 a child's age only of the Child category. The answers go to the\nbooking, the export and the team's email, and to the ticket or the invoice when\nyou choose. The server checks them against the category it records, and a\nbooking's answers are erased in one click.<\/p>\n\n Creating an event asks three things first: how guests attend \u2014 at a venue,\nonline, or both \u2014 what it is called and when, and whether it repeats. Then an\nassistant takes over, and it is the shortest way to describe a night that\nexists. It starts with a drawing rather than a form:\nfifteen kinds of event, from a standing club night to a banquet, a theatre, a\npodium in I or in T, a stadium, a classroom. You point at the one that looks\nlike your room.<\/p>\n\n From there every answer decides the next question, and nothing is asked twice.\nAre seats numbered? Then how is the room laid out \u2014 tables in rows, rows of\nchairs, or no order at all? How many rows, how many tables to a row, how many\nchairs to a table? Are there levels \u2014 a balcony, a terrace, a gallery? Which\nparts are sold at which price? Do guests buy a ticket, or simply reply? How\nare you paid, and what should somebody who\npays by transfer be told? Does the ticket leave immediately, or once you have\nassigned the places yourself? Who chooses the place \u2014 the guest, or you?<\/p>\n\n The panel on the right draws the room while you answer, and shows the prices as\nthe booking page will show them and the line the ticket will print. When you\nfinish, the event is ready to sell: places, zones, prices, payment, delivery.<\/p>\n\n The assistant owns nothing.<\/strong> It adds no setting of its own and keeps no\ncolumn of its own \u2014 it fills in the panels that already held each answer, and\nevery one of them stays editable field by field afterwards. An assistant that\nknows something the editor does not is a second source of truth, and this\nplugin has already paid that bill. For the same reason it refuses to rebuild\nthe room of an event that already has bookings: it will not renumber a table\nsomebody has already been sold.<\/p>\n\n Say the room once \u2014 six rows of eight tables, ten chairs a table, plus a\nbalcony \u2014 and the plugin numbers every place in it. A zone then claims a slice\nof that inventory: tables 1 to 5<\/em>, rows A to C<\/em>, the whole balcony<\/em>. It\ninvents nothing, so nothing can be sold twice and nothing is quietly lost:\nwhatever no zone claims is named on screen as unclaimed rather than forgotten.<\/p>\n\n A price category is not a zone. A category has a name and a price, and several\nzones can share it \u2014 Premium is Premium on the left balcony and on the right.\nThe booking page sells the categories; the ticket prints the zone<\/strong>, because\nthe zone is what somebody reads at the door.<\/p>\n\n Each zone also says what it controls: access only \u2014 a standing area where\nnobody has a seat \u2014 or exactly where each person sits. One event can hold all\nthree at once: a standing floor, a seated balcony, and a numbered block.<\/p>\n\n And if you want to draw the room instead of describing it, the builder is\nthere: drag tables and rows onto a plan, rectangle-select or shift-click,\nalign, space evenly, nudge with the arrow keys, place a stage, a bar, a door.\nThe plan you draw is the plan the guest picks from, and the plan you watch on\nthe night.<\/p>\n\n = One event, many dates \u2026<\/p>\n\n\n Yes. Same plugin, same folder, same settings, same data, same updates \u2014 only\nthe name shown in the directory has changed. It was BitForgeNet Guest Tickets\nand Door Check-in<\/em>, then Events and Tickets with QR Check-in<\/em>, and it is now\nEvents Calendar, Tickets & Registration with QR Check-in<\/strong>, because it now has\nthe calendar. On your own screens it is still Events & Tickets<\/strong>. Nothing to\nreinstall and nothing to reconfigure. It is still published by BitForge\nNetwork, which is what the Author line says, and this is the last renaming.<\/p><\/dd>\n Create the events page under Settings \u2192 Event pages<\/em> \u2014 it shows the agenda \u2014\nor put Yes, under the events page: It speaks seven languages, and it brought them with it<\/h4>\n\n
pt_BR<\/code>,\n pt_PT and pt<\/code> all land on Portuguese and ar_DZ<\/code>, ar_MA<\/code> and ar_SA<\/code> all land\non Arabic. A site in a language it does not have falls back to French rather than\nserving a screen that is half one language and half another. If you would rather\nsay it outright, there is one setting: Settings \u2192 Language<\/em>.<\/p>\n\nA calendar of your events, and a page for every one<\/h4>\n\n
\/events\/opening-night\/<\/code>,\nand \/events\/opening-night\/2026-10-09\/<\/code> for one date of a series. The address\nspeaks your site's language \u2014 \/evenements\/<\/code>, \/eventos\/<\/code>, \/veranstaltungen\/<\/code> \u2014\nand the page wears your theme or the Classic<\/em> look: the picture, the date and\nthe place at the top, the details beside, the booking form below. An event can\nalso live on a page of its own, built with your editor or with Elementor; the\nplugin finds it, and every link then leads there. Links already shared keep\nworking, with a permanent redirect.<\/p>\n\nWhen it is full, when it sells, and what guests are told<\/h4>\n\n
After the booking: a page of their own, the money, the paperwork<\/h4>\n\n
{event}<\/code> and the other words filled in for each guest. Below\nyour words the plugin still writes the evening, the tickets and the links, so\nnothing a guest needs can go missing. Preview it as a guest will see it, send\nyourself a test, and go back to the shipped text in one click.<\/p>\n\nWho it is for<\/h4>\n\n
\n
Set an event up by answering questions<\/h4>\n\n
The room is an inventory, and a zone is an interval of it<\/h4>\n\n
Requirements<\/h4>\n\n
\n
Steps<\/h4>\n\n
\n
\n
The name keeps changing. Is it the same plugin?<\/h3><\/dt>\n
How do I show a calendar of my events?<\/h3><\/dt>\n
[bitforgenet_agenda]<\/code> on any page, the Events agenda<\/em> block in the\neditor, or the Events agenda<\/em> widget in Elementor. Events \u2192 Agenda settings<\/em>\ndecides how it looks, with a sample beside, and writes a shortcode for one\ncategory, one venue, one organizer, this week, this month or this year.<\/p><\/dd>\nDoes every event get a page of its own?<\/h3><\/dt>\n
\/events\/opening-night\/<\/code>, and one more for each\ndate of a series. The address needs pretty permalinks; on a site with plain\nones, links go through the booking page and everything else works. Prefer to\nbuild the page yourself? Paste the event's shortcode on any page or post \u2014 an\nElementor page included \u2014 and every link leads there instead.<\/p><\/dd>\n