Housekeeping. A retired file that no longer had any caller is gone, the two\nbrand images are refreshed, and the directory listing gains a donate link.\nNothing in the plugin behaves differently; a site on 1.10.0 loses nothing by\nwaiting.<\/p>","1.10.0":"
The plugin now speaks six languages \u2014 English, French, Spanish, Portuguese,\nGerman and Arabic \u2014 and brings them with it rather than waiting for a language\npack. It follows your site's language by itself, falls back to French for a\nlanguage it does not have, and can be set outright under Settings \u2192 Language.\nThe booking form, the emails, the door station, the admin screens, the dates and\nthe printed ticket are all covered, and Arabic is drawn properly on the ticket\nitself. Nothing to reconfigure.<\/p>","1.9.1":"
The plugin is now Events and Tickets with QR Check-in<\/strong> in the directory, and\nEvents & Tickets<\/strong> on your own screens. Same plugin, same folder, same\nsettings, same data \u2014 only the name has changed, and nothing needs\nreinstalling or reconfiguring.<\/p>","1.9.0":" Adds a Help<\/strong> screen inside the plugin, and brings the directory page up to\ndate: the screens are shown at last, the description covers everything added\nsince 1.2.1, and the FAQ has been rewritten. (1.9.1 renamed the plugin again the\nsame day \u2014 see above.)<\/p>","1.8.3":" Fixes a white screen when finishing the assistant, and gives it proper Back and\nContinue buttons \u2014 one question at a time instead of everything at once. Update\nbefore using it: in 1.8.2 the last click still failed.<\/p>","1.8.2":" Fixes "Security check failed" when finishing the assistant. Update before using\nit \u2014 in 1.8.0 and 1.8.1 the last button could not save.<\/p>","1.8.1":" Creating an event no longer asks for a price and a capacity on its own step \u2014\nthe assistant asks for them, together with the room they belong to. Three steps\ninstead of four, and the assistant opens straight after.<\/p>","1.8.0":" New: an assistant that sets up an event by asking what kind of night it is. It\nfills in the places, the zones, the prices and when the ticket goes out, and\neverything it sets stays editable exactly where it always was.<\/p>","1.7.0":" One tab now holds the price, the capacity and the room: Prices & places<\/strong>.\n"Pricing & capacity" is gone, and the menu moved to Information & details<\/strong>.\nNothing was lost and no setting needs re-entering. Also fixes a booking form that\ncame back filled in, with a dead button, after the browser's back button.<\/p>","1.6.1":" Fixes zone prices. If your event is priced by named zones, every zone was shown\nand charged at the price of the event instead of its own. Worth updating before\nyour next sale.<\/p>","1.6.0":" Everything the private build does, this plugin now does: the ticket studio, the\nfloor plan editor, price categories and discount codes. Nothing is held back and\nnothing is capped. Existing settings and data are untouched.<\/p>","1.5.0":" Zone prices reach the booking page.<\/strong> An event with named zones \u2014 A at 40, B\nat 60, C at 80 \u2014 showed every guest the same price, because the booking form\nhad never been told the zones existed. It is told now: each guest picks a zone,\npays its price, and sees how many places it has left. A zone with no price of\nits own costs what the event costs.<\/p>\n\n This is the same link the plugin already used to tie a ticket category to a\npart of the room, followed in the other direction: the room is what tiers an\nevent that nothing else tiers, and it always could.<\/p>","1.4.0":" Seating is in this plugin now.<\/strong> The floor that shows the evening filling, the\nscreen that seats a booking, the button that places a party for you \u2014 all of it.\nOnly the drawing<\/em> of a floor plan stays out: the canvas, the curved rows, the\nround tables, the guest picking their own seat on a map. Managing places and\ndrawing a room are two different things, and only the second one was ever worth\nholding back.<\/p>\n\n Fixed: an event set to "you decide where they sit" decided for you.<\/strong> 1.3.3\nplaced bookings automatically where no seating screen existed, which was a fix\nfor one problem and a worse bug in its own right: the ticket went out before you\nhad looked. Now only "ticket straight away" places on its own \u2014 and the screen\nyou were being sent to actually exists.<\/p>\n\n A zone says what it controls, not whether its seats are numbered.<\/strong> The\nquestion an organizer really answers about a part of a room is do I care where\nthese people sit, or only that they are in?<\/em><\/p>\n\n One event can mix all of them, which is the point: a standing area, free seating\nbehind it, and a numbered block for invited guests.<\/p>\n\n A zone with no price of its own costs what the event costs<\/strong>, and the field\nnow shows that price rather than sitting empty. And a room that adds up to\nmore places than the event says it holds now says so<\/strong> \u2014 one of the two numbers\nis wrong, and the door will believe the room.<\/p>","1.3.4":" Fixed: "Confirm payment and send the tickets" was greyed out for good.<\/strong> 1.3.3\nadded a rule that holds a ticket until every guest has a place, and hung it on\nthe wrong button. Confirming a payment records something that has already\nhappened at a desk; it cannot be refused because a seat is undecided. The button\nis never disabled now \u2014 it says Confirm the payment<\/em> when the tickets will have\nto wait, and the reason is printed under it.<\/p>\n\n And the rule no longer has a door with no key.<\/strong> This plugin has no screen for\nplacing guests by hand, so being told "give everyone a place first" was being\ntold to do something it never offered. Where there is no way to place by hand,\nthe plugin now places the booking itself as the payment lands. If it cannot \u2014 no\nfree place left in the category somebody paid for \u2014 it says exactly that, and\nthe fix is in your own hands: add places to the room and the tickets go out on\ntheir own.<\/p>\n\n A paid booking whose tickets never went out now has a button that finishes\nit.<\/strong> Send them now<\/em>, on the booking, once nothing is holding them.<\/p>","1.3.3":" Fixed: a card payment sent tickets with no place on them.<\/strong> The rule that\nholds a ticket until every guest has a place lived in a module this plugin does\nnot include, so an event with a room issued tickets the moment the money landed\n\u2014 with the place blank. The rule now lives with the room itself, which means it\napplies here. The guest is told their payment arrived, and the ticket follows\nwhen you have decided where they sit.<\/p>\n\n "Ticket straight away" now actually places the booking.<\/strong> It was a promise\nwith nothing behind it. The plugin now gives every guest a place as the payment\nlands \u2014 in a category their ticket pays for, keeping the party together where\nthe seats allow \u2014 and only then sends the ticket. If somebody cannot be seated\nin the category they paid for, nobody is moved and the booking waits for you:\nhalf a placed booking is worse than none.<\/p>\n\n Fixed: "This form stays open for ." with nothing in the gap.<\/strong> The sentence\nwaited for a script to fill it in, and read as broken whenever anything stopped\nthat script. The server writes it out in full now, and the script only turns it\ninto a live clock when it can.<\/p>\n\n Fixed: WordPress's own footer line printed across the last panel<\/strong> of an event\nscreen, under the sticky save bar. Room is made for it.<\/p>","1.3.2":" A ticket category is tied to a part of the room.<\/strong> The plugin still works it\nout from the names on its own \u2014 "Standard admission" finds "Standard" \u2014 but the\nguess is only made when exactly one part of the room fits, and the Pricing\nscreen now has a column to say it outright when the names are too far apart.<\/p>\n\n And a part of the room that a category sells is closed to every other\ncategory.<\/strong> This is the half that was missing. Matching alone answers "where may\nthis guest sit?", and when the two screens were named differently it has to\nanswer "anywhere" \u2014 which hands a standard ticket the VIP row. Claiming answers\nthe other question, "who is this row for?", and that one can always be answered.\nA guest whose ticket matches nothing may now sit anywhere nobody else has\nclaimed: never in the VIP row, and never nowhere.<\/p>\n\n Capacity and price follow the same link.<\/strong> A category of tickets takes its\nremaining places from the part of the room it sells, and a part of the room\npriced at zero takes the price of the category that sells it.<\/p>","1.3.1":" Fixed: the plan let you choose a place the dropdown refused.<\/strong> The rule that\nkeeps a standard ticket out of a VIP row was applied to the list of places and\nnot to the plan beside it, so the same booking could be refused a row in one\nplace and given it in the other. It is now one rule, asked by the list, the\nplan, automatic placement and the server alike \u2014 and the "place anyone\nanywhere" box lifts all four together. A rule enforced in one of two places is\nnot a rule.<\/p>\n\n Fixed: a room category priced at zero was sold for nothing.<\/strong> The screen said\nzero meant "the price of the event", and it did not. A price is now settled in\none order wherever it is needed: what you typed on the room category, or else\nthe ticket category of the same name, or else the price of the event.<\/p>\n\n A category on a ticket that the room does not have no longer locks a guest\nout.<\/strong> "Standard admission" and "Standard" are the same thing to an organizer\nand two different strings to a computer. Where the names do not meet, the\nplugin now says so by allowing rather than by forbidding: a guest with nowhere\nto sit stops an evening, and that is the worse failure.<\/p>","1.3.0":" A place is a coordinate, not a name.<\/strong> Where somebody sits is now written the\nway a room is actually read: the level, then the part of the room, then the row\nor table, then the seat along the row. Each piece appears only when it says\nsomething \u2014 a room with one level never mentions it, and a group names itself\nonly when another group uses the same row letters. So a row is "C", not\n"Straight rows-C", and two blocks that both have a row C become "SR\/C" and\n"BAL\/C". Shorter on the ticket, shorter in the door list, and it fits the\ncolumn it is stored in.<\/p>\n\n Levels.<\/strong> A room can be built on more than one \u2014 stalls and balcony, ground\nfloor and gallery, garden and terrace. Name the level on each zone and it\nbecomes the first thing a ticket says. Leave it empty, as most rooms will, and\nit is never mentioned.<\/p>\n\n A chair at a table is found by its table.<\/strong> Where somebody sits around a round\ntable is nobody's business and is no longer printed; which table it is, is. A\nchair in a row is found by both numbers, "Row C, seat 12", because that is how\nsomebody finds it.<\/p>\n\n Fixed: a standard ticket could be seated in a VIP place.<\/strong> A guest is now\noffered only the places the category on their ticket pays for, and automatic\nplacement fills each guest's own category \u2014 a party of five with one VIP among\nthem is seated in two parts of the room rather than one. The desk can still\noverrule it for a swap, a favour or a wheelchair, but on purpose: there is a\nbox to tick, and the check runs again on the way in.<\/p>\n\n Fixed: pressing back could book you twice.<\/strong> A booking form may now be sent\nonce, within a window you set (fifteen minutes by default), and the page shows\nthe time left. Going back and submitting again shows the guest the booking they\nalready have instead of making a second one \u2014 which also means a guest who has\njust paid cannot go back and reserve the same places again for free.<\/p>\n\n Fixed: the paid confirmation did not say who bought what.<\/strong> A party of five\nwith one VIP among them was told the total and nothing else. The email now\nlists each guest and their category.<\/p>\n\n The printed door list<\/strong> keeps a clear gutter between the place and the ticket\nnumber, and prints the readable coordinate rather than the key.<\/p>","1.2.2":" Fixed: the Stripe key would not save.<\/strong> Pasting a secret key changed nothing\nand the card option stayed greyed out, because the Payments screen was not\nallowed to write the settings it was showing. It is now, and a module can\ndeclare settings of its own on somebody else's screen rather than having them\nsilently dropped.<\/p>\n\n New: what one person is given.<\/strong> A room now says whether a booking gets a\nwhole table, row or area, or a single chair. It is one question, asked once, on\nthe Room tab -- and everything follows from it: what can be chosen, what goes on\nthe ticket, and what every screen calls a place. A wedding gives out tables; a\ncinema, a theatre or a seminar gives out chairs; standing areas have no chairs\nand stay areas either way. Rooms that already exist are unchanged and keep\nhanding out whole tables and rows.<\/p>\n\n A place is no longer always called a Table.<\/strong> It is called a Seat, a Table, a\nRow or an Area, depending on what it is -- on screen, in the export, on the\nticket and on the printed door list. A room that mixes them says Place. When\nthis plugin was written a place was always a table; it has not been for a while,\nand a cinema seat labelled Table is the plugin admitting it has not understood\nthe evening.<\/p>\n\n Choosing a chair on the plan.<\/strong> Where a room is sold seat by seat, clicking a\nchair on the plan picks that chair. It used to pick the whole row the chair\nstood in.<\/p>\n\n The plan keeps up while you seat a party.<\/strong> Placing four guests one after\nanother, the second used to be offered the place the first had just been given.\nThe plan and the lists now account for the choices already made on the screen,\nwithout a reload.<\/p>\n\n The printed door list shrinks before it cuts.<\/strong> A place, a ticket number, a\nbooking reference or a category too long for its column is set a little smaller\nso it fits whole, and only loses its tail if it still will not fit at the\nsmallest readable size. "Balcony-A12" clipped to "Balco..." tells an usher\nnothing. The place column is wider and the guest column a little narrower.<\/p>","1.2.1":" Two security fixes, both found and reported by Alik. Forwarding headers such as\nX-Forwarded-For are no longer believed by default, so a visitor can no longer\nhand themselves a fresh rate limit by inventing an address; and bookings for\none event now happen one at a time, so two people clicking at the same instant\ncannot both take the last seat. If your site is behind Cloudflare or a reverse\nproxy, tell the plugin so under Settings \u2192 Anti-abuse.<\/p>","1.2.0":" Rooms and places, card payment with Stripe, and the booking page no longer\ndepends on you having made one. Existing events are untouched and keep working\nexactly as before: a room is something you add when you want one, and card\npayment does nothing until you enter a Stripe key of your own.<\/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":3697091,"resolution":"1544x500","location":"assets","locale":"ar","width":1544,"height":500},"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3697091,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250-ar.png":{"filename":"banner-772x250-ar.png","revision":3697091,"resolution":"772x250","location":"assets","locale":"ar","width":772,"height":250},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3697091,"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.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-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."}},"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=3697091","banner_2x":"https:\/\/ps.w.org\/bitforgenet-guest-tickets\/assets\/banner-1544x500.png?rev=3697091","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."}],"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 and Arabic<\/strong> \u2014 not a promise that\nsomebody will translate it one day, but six finished catalogues in the 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 opens an assistant, and the assistant is the shortest way to\ndescribe a night that exists. 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? How are 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 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 There is no paid edition of this plugin. The assistant, the room builder, the\nticket studio, the price categories, the discount codes and card payment are\nall here, in the plugin you just installed. Nothing is capped, nothing is\nmetered, and no screen ends in an offer.<\/p>\n\n If you find something, write to the address on\nhttps:\/\/bitforgenet.dev\/ and it will be looked at, fixed and credited here by\nname unless you would rather not be. Please test against your own installation\nrather than somebody else's.<\/p>\n\n Thank you to Alik<\/strong> for the two issues fixed in 1.2.1.<\/p>\n\n The plugin stores what a booking needs \u2014 names, email address, phone number \u2014\nin your own database, on your own server. Email goes out through WordPress,\nwhich means through whatever mail service your site already uses. There is no\naccount to create with us and no telemetry: nothing is ever sent to BitForge\nNetwork.<\/p>\n\n The plugin uses one external service, and only if you set it up yourself.<\/p>\n\n Stripe<\/strong> \u2014 used only when you enter a Stripe secret key under Settings \u2192\nPayments and turn card payment on for an event. Until then no connection to\nStripe is ever made.<\/p>\n\n When a guest chooses to pay by card, the plugin asks Stripe to open a payment\npage and …<\/p>\n\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 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\n
It speaks six 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
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
[bitforgenet_registration]<\/code>. Asks\nfor the name of every person coming, shows what is still available as the\nform is filled in, respects capacity and the registration window, and\nconfirms on screen. If no page carries the shortcode, the plugin shows the\nform itself rather than leaving a dead link.<\/li>\nedit place<\/code>, the old\nticket stops working at the door and a second email goes out.<\/li>\nNothing is held back<\/h4>\n\n
Reporting a security issue<\/h4>\n\n
Privacy<\/h4>\n\n
External services<\/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
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
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