BitForgeNet Guest Tickets runs the evening from the first booking to the last\nguest through the door. It was built for clubs, bars and party promoters \u2014 the\npeople for whom an event is a door, a list, and a queue outside.<\/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
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
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
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
A booking arrives pending. You confirm the payment however you actually take it\n\u2014 bank transfer, WhatsApp, cash at the office \u2014 and the tickets go out the\nmoment you do. Nothing is issued for money you have not received.<\/p>\n\n
Everything below is in this plugin. There is nothing to unlock.<\/p>\n\n
[bitforgenet_registration]<\/code>. Asks\nfor the name of every person coming, respects capacity and the registration\nwindow, and confirms on screen.<\/li>\n- Bookings screen<\/strong> \u2014 search, filter by event and status, confirm payment,\nadd an internal note, resend an email, cancel.<\/li>\n
- Personal QR tickets<\/strong> \u2014 one per guest, rendered as a PDF, sent by email\nwith a download link alongside.<\/li>\n
- Built-in ticket design<\/strong>, generated in the colour of your choice and\npainted on demand at 300 dpi.<\/li>\n
- Door check-in station<\/strong> for any phone, opened with a per-event door code,\nwith live counters and multi-station scanning.<\/li>\n
- Printable roll-call list<\/strong> for the evenings the network fails.<\/li>\n
- CSV export with a column picker<\/strong> \u2014 bookings or guests, one event or all,\nevery field the plugin holds, and it remembers what you ticked.<\/li>\n
- Tools and data<\/strong> \u2014 a system check that tells you why a ticket or an email\ndid not arrive, a test-ticket email, a database check, and an\narchive-and-clear that copies every booking into archive tables before\nemptying the live ones, behind a one-time code sent to an address you\nnominate.<\/li>\n
- Searchable archive<\/strong> of everything that has been cleared.<\/li>\n
- Activity log<\/strong> \u2014 who did what, and when.<\/li>\n
- Delete-all-data on uninstall<\/strong>, if you tick it. Off by default.<\/li>\n<\/ul>\n\n
BitForgeNet Pro<\/h4>\n\n
Pro is a separate plugin, bought from us and installed alongside this one. It\ndoes not unlock anything here \u2014 this plugin is complete on its own. Pro adds\ncapabilities that are not in it at all:<\/p>\n\n
\n- Ticket studio<\/strong> \u2014 bring in your own artwork, generate colour variations of\nit, and move every printed field where you want it with a visual field map.<\/li>\n
- Seating and tables<\/strong> \u2014 draw the floor, assign a seat or a table to each\nguest, and print it on the ticket.<\/li>\n
- Price categories<\/strong> \u2014 VIP, table, early bird, member: several prices on one\nevent instead of one.<\/li>\n
- Discount codes<\/strong> \u2014 fixed or percentage, limited by date or by number of\nuses.<\/li>\n
- Online card payment<\/strong> \u2014 the booking pays itself and the tickets go out with\nno confirmation step. This is what the first Pro release is being built\naround.<\/li>\n<\/ul>\n\n
Pro is announced at https:\/\/bitforgenet.dev\/<\/p>\n\n
Privacy<\/h4>\n\n
The plugin stores what a booking needs \u2014 names, email address, phone number \u2014\nin your own database, on your own server. It sends nothing anywhere else. Email\ngoes out through WordPress, which means through whatever mail service your site\nalready uses. There is no external service, no account to create, and no\ntelemetry.<\/p>\n\n\n
Requirements<\/h4>\n\n\n- WordPress 5.8 or later<\/li>\n
- PHP 7.4 or later<\/li>\n
- The GD extension, for rendering the tickets<\/li>\n
- A working mail setup on the site \u2014 an SMTP plugin if your host's mail is\nunreliable<\/li>\n<\/ul>\n\n
Steps<\/h4>\n\n\n- Plugins -> Add New, search for BitForgeNet Guest Tickets<\/strong>, install and\nactivate. Or upload the ZIP under Plugins -> Add New -> Upload Plugin.<\/li>\n
- Open BitForgeNet -> Settings<\/strong> and set your currency, your From address\nand your payment instructions.<\/li>\n
- Open BitForgeNet -> Tools & data<\/strong>, run the system check, then send\nyourself a test ticket. Do this before your first real booking, not after.<\/li>\n
- Create your first event with BitForgeNet -> Events -> New event<\/strong>.<\/li>\n
- Put the booking form on a page with the shortcode\n [bitforgenet_registration].<\/li>\n
- On the night, open BitForgeNet -> Door scanner<\/strong>, note the door code, and\ngive the link and the code to whoever is on the door.<\/li>\n<\/ol>\n\n\n
\nIs there a limit on events, guests or tickets?<\/h3><\/dt>\nNo. 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
Do guests need an account?<\/h3><\/dt>\nNo. A guest fills in the form, receives their tickets by email, and shows the\nQR code at the door.<\/p><\/dd>\n
Does it need WooCommerce?<\/h3><\/dt>\nNo. 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
Can I take payment online?<\/h3><\/dt>\nNot in the free plugin. A booking arrives pending and you confirm it once you\nhave been paid \u2014 by transfer, by WhatsApp, or in cash. Card payment is what\nBitForgeNet Pro is being built around.<\/p><\/dd>\n
Does one booking give one QR code for everybody?<\/h3><\/dt>\nNo, 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
The tickets are not arriving.<\/h3><\/dt>\nThe 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>\nThe email arrives but the PDF is missing.<\/h3><\/dt>\nYour 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
Does the door scanner need internet?<\/h3><\/dt>\nIt 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
Do I need to install an app on the door phone?<\/h3><\/dt>\nNo. 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
Can two people scan at once?<\/h3><\/dt>\nYes. Every station checks the same database, so a ticket used at one door is\nalready used at the other.<\/p><\/dd>\n
The camera stays black on the door phone.<\/h3><\/dt>\nThe 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
Can I use my own ticket artwork?<\/h3><\/dt>\nThe free plugin generates its design for you, in the colour you choose.\nBringing in your own artwork and placing the printed fields yourself is what\nthe ticket studio in BitForgeNet Pro does.<\/p><\/dd>\n
Can I clear the test bookings before going live?<\/h3><\/dt>\nYes. 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>\nIs it translated?<\/h3><\/dt>\nEvery string in the plugin is translatable. Translations are welcome at\nhttps:\/\/translate.wordpress.org\/projects\/wp-plugins\/bitforgenet-guest-tickets\/<\/p><\/dd>\n
Where do I get help?<\/h3><\/dt>\nThe support forum on this page, or contact@bitforgenet.dev<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.9<\/h4>\n\n\n- The logo printed on the ticket, on the door's code screen and beside an\norganizer with no artwork of its own is the anvil alone. It had been the full\nlockup, wordmark included, which the renderer fits inside its box: a wide\nimage with words in it shrank to a smudge nobody could read<\/li>\n
- The plugin's page is rewritten. The feature list now says what this plugin\nactually does -- the organizer and venue libraries, the export column picker,\nthe system check and the archive were all shipped and none of them were\nmentioned, while three of them were wrongly described as belonging to Pro.\nThe Pro section says what Pro adds instead of hinting at it, and the FAQ\nanswers fifteen questions rather than five. No code changed for this<\/li>\n<\/ul>\n\n
1.0.8<\/h4>\n\n\n- Every template under admin\/views\/ and public\/views\/ states once, at the top of\nthe file, that the PrefixAllGlobals naming rule does not apply to it. A\ntemplate is included from a method, never at file scope, so its variables\nbelong to that method's scope rather than the global one, and PHPCS -- reading\neach file on its own -- has no way to see where the include happens. No\nvariable was renamed and nothing behaves differently<\/li>\n<\/ul>\n\n
1.0.7<\/h4>\n\n\n- The plugin is renamed. It was submitted as \"2KEvents\", and \"2K\" is a\nregistered trademark of Take-Two Interactive that we have no right to lead a\nname with. The display name, the slug, the text domain, the shortcodes and\nevery PHP prefix now read BitForgeNet \u2014 the name of the site that publishes\nit, bitforgenet.dev<\/li>\n
- Every stylesheet and script the plugin prints goes out through the enqueue\nAPI. The door station and the two screens around it are their own HTML\ndocuments, served on their own endpoint before the theme runs, so they had\ncarried their CSS and JS inside the page. They now register handles and print\nthem by name, the two runtime values arriving through wp_add_inline_style()\nand wp_add_inline_script()<\/li>\n
- The admin menu icon is assembled from the mark at runtime and has no file\nbehind it, so it registers a style handle with no source rather than printing\na style tag into the head, and moves to admin_enqueue_scripts<\/li>\n
- The code prefix is five characters. It was three, which is under the four the\ndirectory asks for<\/li>\n<\/ul>\n\n
1.0.6<\/h4>\n\n\n- Finished the tidy-up the last two releases started: every code-quality\nsuppression in the plugin is now either stated once for a whole file or\nwritten on the single line it covers, and none of them can change the\nmeaning of another one elsewhere in the same file. No behaviour changes<\/li>\n<\/ul>\n\n
1.0.5<\/h4>\n\n\n- Fixed suppression comments that did not cover what they appeared to cover.\nOne kind switched every code-quality rule back on rather than the one it had\nswitched off, quietly undoing notes written elsewhere in the same file; the\nother sat above a nine-line statement instead of around it. No behaviour\nchanges for anyone using the plugin<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Request input is now read the way it should be read: eight admin screens\napplied the integer cast to the whole expression rather than to the value,\nand the export column list is sanitised where it arrives rather than three\ncalls later<\/li>\n
- The design proof screen now checks its parameter exists before reading it<\/li>\n
- Every file that queries the plugin's own tables says so once, at the top,\nwith the reason<\/li>\n
- Dropped a call asking WordPress to load translations it already loads by\nitself, and closed a hatch that let the QR encoder run outside WordPress<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Fixed translatable strings that a translator could not have got right. The\nguest counter on an order wrote its two numbers as bare placeholders, which\na language that reorders the words has no way to move, and several strings\ncarrying a placeholder had no note saying what the placeholder holds.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- The plugin header pointed at a placeholder address. It now points at the\nplugin's own page, and the author is named.<\/li>\n
- The address authorised to reset the plugin's data shipped with a developer's\nown address already filled in. It now starts empty, and the tool refuses to\nrun until an administrator sets one.<\/li>\n
- Added the full text of the SIL Open Font License beside the bundled Poppins\nand Lora fonts, as that licence requires.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Fixed the door station refusing every scan with \"Station closed\". The page\nopened and showed the event, but each scan was posted to an address that no\nlonger said which event the station was watching, so the server treated it as\na station that had signed out. Nobody could be checked in<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"Name every guest, send each one a personal QR ticket as a PDF, and scan them in at the door from a phone. Unlimited events and tickets. No fees.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361265","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361265"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/bitforgenet"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361265"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361265"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361265"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361265"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361265"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}