A large update: dates that repeat, online events, invitations, a programme,\ncalendars, and a door that works one date at a time. The database is updated\non the spot; back it up first, as for any update. Open door stations ask for\ntheir code once more.<\/p>"},"ratings":[],"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.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-2.png":{"filename":"screenshot-2.png","revision":3694201,"resolution":"2","location":"assets","locale":"","width":1520,"height":639},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3694201,"resolution":"3","location":"assets","locale":"","width":1520,"height":639},"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."}},"plugin_section":[],"plugin_tags":[1486,99,1373,4772,4771],"plugin_category":[40,58],"plugin_contributors":[278878],"plugin_business_model":[],"class_list":["post-361265","plugin","type-plugin","status-publish","hentry","plugin_tags-events","plugin_tags-multilingual","plugin_tags-qr-code","plugin_tags-ticketing","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."}],"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 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 A weekly club night, a play that runs for a month, a course every Tuesday: one\nevent with several dates, not one event per date. Set the rule once \u2014 every\nday, week, month or year, on the weekdays you tick, until a date or for a\nnumber of dates \u2014 and each date gets its own bookings, its own capacity, its\nown door and its own online room. The guest picks a date on the booking page,\nand everything they receive carries that date: the emails, the ticket, the\ncalendar file.<\/p>\n\n Changing dates works the way every calendar has taught everybody: this date,\nthis one and the following, or all of them. A date somebody has booked is never\nmoved with the others \u2014 it is named, so you change it knowing who holds a\nticket for it. A booked date is cancelled rather than deleted, and its tickets\nare refused at the door with the reason. A date that needs another room or\nother prices can be detached into an event of its own, taking a copy of the\nroom and the ticket categories with it.<\/p>\n\n At the door, a ticket for another date is refused as not tonight<\/em>, with the\ndate it is for.<\/p>\n\n How guests attend is the first question of every event. Online, nobody is\nseated and nothing waits for a place: the capacity is the size of your online\nroom. Hybrid, the room people walk into and the online room share one capacity.<\/p>\n\n Guests never receive the meeting link itself. Each gets a personal link through\nyour site, checked the moment it is clicked \u2014 so the link can be added late or\nchanged at any time and still reach everyone, a cancelled booking stops opening\nit, and you decide who gets in: anyone who booked, only paid guests, or only\nonce the room opens. Each date of a series can have a link of its own.<\/p>\n\n Any ticket category can be a reply instead of a sale: free, confirmed the\nmoment the guest answers, with a ticket and its QR code or simply with their\nname on the list. When every category of an event is a reply, the booking page\nbecomes an invitation \u2014 count me in<\/em> or I can't make it<\/em>, and no total. A\nguest who cannot come says so, you are told, and the place stays free. One\nevening can mix both: a free reply for the family beside a paid dinner.<\/p>\n\n Describe the people who appear once \u2014 a photo, a few lines, their links \u2014 and\nput them on as many events as you like. Each event has a line-up, shown on the\nbooking page and printed on the ticket, and a programme of sessions: who, what,\nwhen and where, day 2 at 00:30 included. On a series, a session can belong to\none date only.<\/p>\n\n The thank-you page and the first email offer the date to Apple Calendar and\nOutlook (a .ics file), Google Calendar and Outlook.com \u2014 with the right time\nzone and, online, the way in. And every event page tells search engines what it\nis, in the structured data they read: the dates, the venue or the online room,\nthe line-up, the organizer and the prices.<\/p>\n\n The top of every email is your event: the organizer's logo, the title of the\nevent and who is presenting it, in colours worked out to stay readable on your\nbrand colour. The plugin's name appears nowhere in what your guests receive. If\nyou would like to credit it, one box in Settings \u2192 Email<\/em> adds a small line at\nthe bottom \u2014 off unless you switch it on.<\/p>\n\n A booking for five asks for five names, and each one gets their own ticket with\nits own QR code. One code cannot let five people in, and the door knows who is\nstanding in front of it.<\/p>\n\n The booking form also knows what is left while it is being filled in<\/strong> \u2014\ncounted against what the page was rendered with, what the lines above it have\nalready taken, and what somebody else is taking in another browser at the same\nmoment. An option with nothing left is greyed out rather than removed, so\nnobody's choice is ever changed behind their back. The real guarantee is not in\nthe browser, where it could never be: the event is locked, the places are\nrecounted and the booking is refused at the moment of writing.<\/p>\n\n Each one is drawn at 100 x 250 mm, 300 dpi, with the QR engraved into the\nartwork, and delivered as a PDF by email. Mail servers strip attachments more\noften than they admit, so every message also carries a download link for each\nguest.<\/p>\n\n The ticket studio takes your own artwork if you have some \u2014 upload it, generate\ncolour variations, and move every printed field where you want it on a visual\nfield map \u2014 and generates a design for you in the colour of your choice if you\nwould rather not think about it.<\/p>\n\n Open the check-in station on any phone \u2014 no app to install. Point it at a\nticket and it answers in one screen: valid, already used, or not for tonight.\nCounters update live, several phones can scan the same event at once, and when\nthe venue's wifi gives up \u2014 it will \u2014 there is a printable roll-call list with\nevery guest and every ticket number on it.<\/p>\n\n The plan says who is actually in the room. A place that has been sold and a\nplace whose guest has walked through the door are two different facts, and only\none of them moves all evening: a guest who has scanned turns green, carries a\ntick and pulses, and a table whose whole party has arrived wears a green ring.<\/p>\n\n Two ways, and neither is the lesser one.<\/p>\n\n Take the money yourself: a booking arrives pending, you confirm it however you\nactually get paid \u2014 bank transfer, WhatsApp, cash at the office \u2014 and the\ntickets go out the moment you do. Nothing is ever issued for money you have not\nreceived. What the guest is told about paying is your own text, written per\nevent, because offline that text is<\/em> the payment.<\/p>\n\n Or let the card do it: add your own Stripe key and the guest pays on Stripe's\npage, comes back confirmed, and gets their tickets without you touching\nanything. Their places are held while they pay and released on their own if\nthey walk away, so the same seat is never sold twice. The money goes straight\nfrom the guest to your own Stripe account \u2014 this plugin is never in between,\nand takes nothing.<\/p>\n\n Everything below is in this plugin. There is nothing to unlock.<\/p>\n\n Yes. Same plugin, same folder, same settings, same data, same updates \u2014 only\nthe name shown on screen has changed. It was BitForgeNet Guest Tickets and\nDoor Check-in<\/em>, briefly Tickets & Events<\/em>, and it is now Events and Tickets\nwith QR Check-in<\/strong> in the directory and Events & Tickets<\/strong> on your own\nscreens. Nothing to reinstall and nothing to reconfigure. It is still published\nby BitForge Network, which is what the Author line says.<\/p><\/dd>\n No. Nothing in this plugin is capped or metered, and there is no per-ticket\nfee. What your server can hold is the limit.<\/p><\/dd>\n Not today. Everything this plugin can do is in the plugin you installed \u2014 the\nassistant, the room builder, the ticket studio, the price categories, the\ndiscount codes and card payment included. No screen ends in an offer.<\/p><\/dd>\n No. A guest fills in the form, receives their tickets by email, and shows the\nQR code at the door.<\/p><\/dd>\n Yes. Under Information & details<\/em>, set it to repeat every day, week, month or\nyear, on the weekdays you choose, until a date or for a number of dates. It\nstays one event: each date has its own bookings, capacity and door, and the\nguest chooses the date when booking. The Recurring dates<\/em> tab lets you change\none date, the following ones or all of them.<\/p><\/dd>\n Yes. Choose Online<\/em> or Both<\/em> as the first answer when you create the event,\nand put your meeting link in Information & details<\/em>. Every guest receives a\npersonal link through your site rather than the meeting link itself, so you can\nchange the link at any time, and a cancelled booking stops opening it.<\/p><\/dd>\n Yes. Set a ticket category to RSVP: the place is free and confirmed the moment\nthe guest replies, with a QR ticket or simply their name on the list. When every\ncategory is an RSVP, the booking page becomes an invitation with count me in<\/em>\nand I can't make it<\/em>.<\/p><\/dd>\n No. The top of every email shows your event and its organizer. There is an\noptional credit line in Settings \u2192 Email<\/em>, off by default.<\/p><\/dd>\n No. It has its own booking form and its own bookings screen, and it works on a\nsite with no shop on it.<\/p><\/dd>\n No. It opens when you create an event because that is the fastest way through,\nand you can leave it at any point: every answer it writes is a field you can\nopen and change afterwards. It owns no setting of its own.<\/p><\/dd>\n Two ways, and they end in the same place. Describe it in numbers \u2014 rows, tables\nto a row, chairs to a table, levels \u2014 or draw it in the builder: drop tables,\nrows, a stage and a bar on a plan, select several at once, align them, space\nthem evenly, nudge them with the arrow keys. Either way the plugin numbers\nevery place and hands them out.<\/p><\/dd>\n Yes. Each zone says for itself whether it controls access only or where each\nperson sits, so a standing floor, a seated balcony and a numbered block can all\nbelong to the same night.<\/p><\/dd>\n A zone is a piece of the room \u2014 tables 1 to 5<\/em>, the balcony<\/em>. A category is a\nname and a price, and several zones can share one: Premium is Premium on the\nleft balcony and on the right. The booking page sells the categories; the\nticket prints the zone, because that is what somebody reads at the door.<\/p><\/dd>\n You can add to it and change prices. You cannot rebuild it: the assistant\nrefuses to renumber a room that already has bookings, because a table number\nsomebody has already been sold has to keep meaning the same table.<\/p><\/dd>\n One of them gets it and the other is told, before anything is charged. The form\nshows what is left while it is being filled in \u2014 including what somebody else\nis taking in another browser \u2014 but the guarantee is not in the browser: the\nevent is locked, the places are recounted and the booking is refused at the\nmoment it is written.<\/p><\/dd>\n Yes, and the plugin treats it as what it is: a re-issue, not an edit. The\nscreen states the three consequences, the buttons stay dead until you type\n edit place, and then the old ticket stops working at the door and a second\nemail goes out with the new one.<\/p><\/dd>\n Yes, with Stripe. Put your own Stripe secret key in Settings \u2192 Payments and\nturn card payment on for the events you want it on. The guest pays on a page\nhosted by Stripe, no card number touches your site, and the money goes straight\nto your own Stripe account: this plugin is never in between and takes nothing\nper ticket, ever.<\/p>\n\n Until you enter a key, nothing changes and no connection to Stripe is made. A\nbooking arrives pending and you confirm it once you have been paid \u2014 by\ntransfer, by WhatsApp, or in cash \u2014 exactly as before.<\/p><\/dd>\n No. It is a choice per event, and you can also let a guest reserve now and pay\nlater: they get both buttons. If you would rather nothing be reserved until it\nis paid for, there is a single setting for that. What a guest who pays offline\nis told is your own text, written per event \u2014 offline, that text is the\npayment.<\/p><\/dd>\n No, and that is the point. A booking for five produces five tickets with five\ndifferent codes, each carrying the name of the person it belongs to.<\/p><\/dd>\n Yes. The notification address takes a list, and every address on it is really\ncopied in.<\/p><\/dd>\n The plugin sends through WordPress, so anything that fixes email for the rest\nof your site fixes it here. Run Tools & data -> System check<\/strong> first: it says\nwhether the failure is in the rendering or in the sending. If your host's mail\nis unreliable, install an SMTP plugin and connect a real mailbox \u2014 it will be\npicked up automatically.<\/p><\/dd>\n Your mail server is stripping the attachment. Lower the attachment ceiling in\nSettings; every email already carries a download link per guest, so the guest\nstill gets their ticket.<\/p><\/dd>\n It needs to reach your own website, the same as any other page. For the\nevenings when the venue's wifi is not to be trusted, print the roll-call list\nfirst: it carries every guest and every ticket number, and it works on paper.<\/p><\/dd>\n No. The station is a web page. Open the link in the phone's browser, enter the\ndoor code, and allow the camera.<\/p><\/dd>\n Yes. Every station checks the same database, so a ticket used at one door is\nalready used at the other.<\/p><\/dd>\n The page must be served over HTTPS \u2014 browsers refuse the camera otherwise. If\nthe site is already on HTTPS, a security plugin or your CDN is probably sending\na blanket camera policy; the scanner screen re-states its own, so clearing the\nCDN cache usually settles it.<\/p><\/dd>\n Yes. The plugin will generate a design for you in the colour you choose if you\nwould rather not think about it, and the ticket studio on the Ticket designs<\/strong>\nscreen takes your own artwork instead: upload it, generate colour variations of\nit, and move every printed field where you want it on a visual field map.<\/p><\/dd>\n Yes. Tools & data -> Archive and clear<\/strong> copies every booking, guest, ticket\nand scan into archive tables and then empties the live ones. Events, venues,\norganizers and designs are untouched. It asks for a one-time code sent to an\naddress you set, so it cannot be run by accident.<\/p><\/dd>\n Seven, finished and in the download: English, French, Spanish, Portuguese,\nGerman, Italian and Arabic. Nothing to install and nothing to wait for.<\/p><\/dd>\n It reads the language WordPress is set to, and it reads it by language rather\nthan by locale \u2014 pt_BR, pt_PT and pt all get Portuguese; ar_DZ, ar_MA and ar_SA\nall get Arabic. A site in an eighth language falls back to French rather than\nshowing you half a translation. You can also say it outright under Settings \u2192\nLanguage<\/strong>, which is the answer when your site is in one language and your guests\nread another.<\/p><\/dd>\n No. It moves this plugin and nothing else. WordPress, your theme and every other\nplugin keep the language they had.<\/p><\/dd>\n The ticket itself. A ticket is a drawn image rather than a web page, so it is the\npiece that usually gets left behind \u2014 here the words on it, the date written out\nin full, and the line that says which table or seat all come out in the guest's\nlanguage.<\/p><\/dd>\n Yes, and that is a real question rather than a polite one. Arabic letters change\nshape depending on what is beside them, and the line reads right to left; the\nimage library that draws tickets does neither by itself, which is why Arabic on a\nticket usually comes out as a row of disconnected letters in the wrong order. The\nplugin joins the letters and orders the line before anything is drawn, and carries\nan Arabic typeface to draw them with. Numbers inside the sentence \u2014 a time, a\nprice, a table number, a ticket reference \u2014 still run the other way, as they\nshould. The screens, the booking form, the emails and the door station are laid\nout right to left too.<\/p><\/dd>\n Theirs. The language a guest booked in is kept with their booking, so their\nticket and their emails go out in it \u2014 including a ticket re-sent months later\nfrom a screen you are reading in French.<\/p><\/dd>\n No, and they should not be. Your event titles, venue names, payment instructions\nand success message are your words; the plugin translates its own and leaves\nyours alone. A venue selling to guests in two languages writes those lines in\nboth.<\/p><\/dd>\n Yes. The catalogues are ordinary .po files in the plugin's There is a Help<\/strong> screen in the plugin itself \u2014 the whole guide, one click from\nwherever you are stuck. The same text is at\nhttps:\/\/bitforgenet.dev\/plugins\/bitforgenet-guest-tickets\/help\/ \u2014 it walks\nthrough a first event, the room, the door and the night itself. Beyond that,\nthe support forum on this page, or contact@bitforgenet.dev<\/p><\/dd>\n\n<\/dl>\n\n\n The biggest release since the first: events that repeat, online events,\ninvitations, people and a programme, calendars \u2014 and a door that knows which\nnight it is.<\/p>\n\nIt 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\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
One event, many dates<\/h4>\n\n
Online, at the venue, or both<\/h4>\n\n
Invitations as well as tickets<\/h4>\n\n
Speakers, performers and the programme<\/h4>\n\n
In the calendar, and in search engines<\/h4>\n\n
Your emails carry your name<\/h4>\n\n
Every guest is a person, not a number<\/h4>\n\n
Tickets that look like tickets<\/h4>\n\n
The door works<\/h4>\n\n
Payment on your terms<\/h4>\n\n
What the free plugin does<\/h4>\n\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
Is there a limit on events, guests or tickets?<\/h3><\/dt>\n
Is there a paid version?<\/h3><\/dt>\n
Do guests need an account?<\/h3><\/dt>\n
Can an event repeat?<\/h3><\/dt>\n
Can I run an online or hybrid event?<\/h3><\/dt>\n
Can guests just reply, without paying?<\/h3><\/dt>\n
Does the plugin's name appear in my guests' emails?<\/h3><\/dt>\n
Does it need WooCommerce?<\/h3><\/dt>\n
Do I have to use the assistant?<\/h3><\/dt>\n
How do I describe a room that is not a grid?<\/h3><\/dt>\n
Can one event have standing room and numbered seats?<\/h3><\/dt>\n
What is the difference between a zone and a price category?<\/h3><\/dt>\n
Can I change the room after people have booked?<\/h3><\/dt>\n
Two people booked the last table at the same moment. What happens?<\/h3><\/dt>\n
Can I move somebody who already has their ticket?<\/h3><\/dt>\n
Can I take payment online?<\/h3><\/dt>\n
Do I have to make guests pay by card?<\/h3><\/dt>\n
Does one booking give one QR code for everybody?<\/h3><\/dt>\n
Can more than one of us be told when a booking arrives?<\/h3><\/dt>\n
The tickets are not arriving.<\/h3><\/dt>\n
The email arrives but the PDF is missing.<\/h3><\/dt>\n
Does the door scanner need internet?<\/h3><\/dt>\n
Do I need to install an app on the door phone?<\/h3><\/dt>\n
Can two people scan at once?<\/h3><\/dt>\n
The camera stays black on the door phone.<\/h3><\/dt>\n
Can I use my own ticket artwork?<\/h3><\/dt>\n
Can I clear the test bookings before going live?<\/h3><\/dt>\n
What languages does it come in?<\/h3><\/dt>\n
How does it know which one to use?<\/h3><\/dt>\n
Does it change the language of my site?<\/h3><\/dt>\n
Is the ticket itself translated, or only the screens?<\/h3><\/dt>\n
Does Arabic work properly, including on the ticket?<\/h3><\/dt>\n
A guest booked in one language and I work in another. Which one do they get?<\/h3><\/dt>\n
Are my own event titles translated?<\/h3><\/dt>\n
Can I correct or add a translation?<\/h3><\/dt>\n
languages<\/code> folder,\nand the template is there beside them. Better still, put the correction on\nhttps:\/\/translate.wordpress.org\/projects\/wp-plugins\/bitforgenet-guest-tickets\/ \u2014\na language pack from there is loaded ahead of the plugin's own files, so your\nwording wins and everybody gets it.<\/p><\/dd>\nWhere do I get help?<\/h3><\/dt>\n
1.12.18<\/h4>\n\n
\n
LICENSE.txt<\/code>.<\/li>\n<\/ul>\n\n1.11.0<\/h4>\n\n
\n
1.10.1<\/h4>\n\n
\n
admin\/views\/event\/pricing.php<\/code>, a tombstone left from the retired\nPricing tab that nothing has called since 1.9.0.<\/li>\n1.10.0<\/h4>\n\n
\n
1.9.1<\/h4>\n\n
\n