Events and Tickets with QR Check-in

Regjistër ndryshimesh

1.10.1

• Removed admin/views/event/pricing.php, a tombstone left from the retired
  Pricing tab that nothing has called since 1.9.0.
• Refreshed the two brand images shipped with the plugin.
• Added a donate link to the directory listing. Nothing appears inside
  WordPress: no screen in this plugin ends in an offer, and that has not
  changed.

1.10.0

• Six languages, in the download. English, French, Spanish, Portuguese,
  German and Arabic. Every screen, the booking form, the emails, the door
  station and the words printed on the ticket.
• The language is worked out from your site, by language rather than by
  locale: pt_BR, pt_PT and pt all land on Portuguese, ar_DZ, ar_MA and ar_SA all
  land on Arabic. A site in a language the plugin does not have falls back to
  French rather than serving half a translation.
• New setting: Settings → Language. Leave it on Follow the site, or name
  the language outright — for a site in one language selling to guests who read
  another. The screen says what your site is set to and what the plugin will
  speak, so there is nothing to guess at.
• The language travels with the booking. A guest who booked in Spanish is
  answered in Spanish, including a ticket re-sent months later from an admin
  screen in another language, or issued by cron in the middle of the night.
• Dates are translated too, out of the plugin’s own catalogue rather than
  WordPress’s — so a French ticket does not print “September” under a French
  heading on an English site, and a site that has never installed French still
  gets French months.
• Arabic is drawn properly on the ticket. The ticket is an image, and the
  library that draws it neither joins Arabic letters nor puts the line in
  reading order. The plugin now does both before drawing, and carries an Arabic
  typeface to draw with. A time, a price, a table number or a ticket reference
  still runs the other way inside the sentence.
• Right-to-left layout for the admin screens, the booking form, the emails
  and the door station — the plugin’s own containers only, so the rest of your
  site is untouched. A seating plan is not mirrored: table 1 stays where table 1
  actually is.
• The plugin’s catalogues are loaded after any language pack from
  translate.wordpress.org, so a translator’s work always wins over ours.

1.9.1

• Renamed, and this time for the search rather than for the branding. The
  directory ranks the words of a title, so the title is now
  Events and Tickets with QR Check-in — the words somebody actually types.
  On your own screens and in the admin menu it is Events & Tickets, two
  words that fit a sidebar. The brand leaves the title: the Author line already
  says BitForge Network, and a name is not the place to sign your work twice.
• The slug, the text domain, the shortcodes, the option keys, the database
  tables and the update path are untouched, exactly as in 1.9.0. Nothing to
  reinstall, nothing to reconfigure.

1.9.0

• Renamed on screen. The slug, the text domain, the shortcodes, the option
  keys, the database tables and the update path were all untouched: a label,
  not a new plugin. (1.9.1, the same day, renamed it again — see above.)
• New icon and new directory banners: a ticket and a QR code, which is what the
  plugin actually is. The QR in the artwork is a real one.
• The directory page shows the screens again — eight of them, from the
  assistant to the door station — and the description finally covers what was
  added between 1.2.2 and 1.8.7: the assistant, the room builder, zones as
  intervals of an inventory, price categories, live availability in the booking
  form, arrivals on the plan, re-issuing a place, and team notifications.
• The FAQ was rewritten around the questions the last two months produced.
• New: a Help screen inside the plugin. The whole guide — setup, the
  assistant, the room and its zones, payment, tickets, seating, the door, and
  what to do when something does not arrive — on the screen where somebody is
  actually stuck, linking to the screens each sentence talks about. It reads
  nothing and writes nothing, and it needs no capability beyond being able to
  open the plugin: help only an administrator can read is help the person who
  needed it could not reach.
• Nothing else changes: no database change, no stored setting touched, and no
  existing screen behaves differently.

1.8.7

The team notification field takes more than one address. A team is more than
one person. Separate them however you like — a comma, a semicolon, a space, one
per line — and everybody on the list is copied on guest emails and alerted on
every new booking. Before, only the first address was ever used.

An empty reply-to now follows WordPress. Left blank it means “whatever this
site uses” rather than “nobody”, so replies land in the site’s own
administration inbox without anybody having to think about it. The from address
behaves the same way, and both boxes show you the address they would fall back
to.

Fixed: typing an answer in the assistant left Continue greyed out. Every
keystroke repainted the panel, but only a full redraw ever drew the buttons — so
after typing the payment instructions the only way to move on was to step back
and forward again. The answer and the button are drawn together now.

The floor plan says who is actually in the room. A seat that is sold and a
seat whose guest has walked through the door are two different facts, and only
one of them changes all evening. A guest who has scanned their ticket turns
green, carries a tick, and breathes gently; a table whose whole party
has arrived wears a green ring. There is an Already in filter, a key under
the plan explaining every colour, and the same story in the simple list for
anyone who never opens the drawing. The movement stops for anyone whose system
asks for less motion — the colour and the tick still say everything.

Moving a guest who already has a ticket is no longer an ordinary save. It
is a reissue, and it does three things at once: the tickets they are holding are
voided — the door refuses those QR codes from that moment — new tickets are
drawn with the new places, and a second email goes out. If they have already
shown somebody the first one, that is the copy that stops working. So the screen
now says all of that in plain words, and the buttons stay dead until you type
edit place into the box beside them. Not a checkbox, which the hand ticks
before the eye reads; not a browser dialog, which is dismissed by reflex. The
same sentence is checked again on the server, because a rule that only lives in
a browser is not a rule.

1.8.6

The booking form now knows what is left while somebody is filling it in.
Three things have to agree, and until now only the first was ever asked: the
number the page was drawn with, the guest rows above this one, and whoever
else is booking at the same moment somewhere else. Choose VIP for five guests in
a room that has five, and the sixth row greys VIP out as you reach it — instead
of letting you type eight names and refusing the lot at the end.

It asks again at the moments a decision is being made: a menu opening, a
choice changing, the quantity changing, the tab coming back to the front — and
on a slow tick in between, never while the tab is hidden. One function answers,
for the page and for the live refresh alike, so the two can never disagree. It
is cached for five seconds and thrown away the instant a booking is written, so
the next person to open a menu sees the seat go.

The quantity stepper stops at what exists, and a line above the guest rows
says how many places are still for sale, counting down as they go.

A category that sells out under you is said out loud, on the row it affects,
and the booking cannot be sent until you have picked another. Your choice is
never changed behind your back — first come, first served, and being told so.

Fixed — and this was the hole underneath all of it: a booking held no place in
its category until somebody had been sat down. The seat count could only see
guests who already had a place written against them, and where the organizer
seats people by hand nobody has one until they do it — hours or days after the
guest paid. A VIP zone of forty still reported forty places left after forty
people had bought it. Every booking now holds its places from the moment it is
written, whether or not anybody has decided where those people are sitting.

None of this is the guarantee, and it does not pretend to be. The booking
itself is still taken under a lock on the event, counted again, and refused with
a plain sentence if the last place went a second ago. The live form exists so
that you are told before you have typed eight names rather than after.

1.8.5

Fixed: your event was not selling the price categories you gave the room.
Every event is handed a “Standard admission” ticket category the moment it is
created, and the room only spoke up when nothing else had — so you could name
three price categories in the assistant, see all three on every screen in the
admin, and have the booking page sell one. The room now decides what an event
sells whenever it describes it, because it is the thing that actually holds
the people. A room category you left at zero borrows the price of the ticket
category of the same name, so nothing silently drops to the base price.

The ticket-categories list stops competing. With a room in place it folds
away on Prices & places under Offers that are not places — early bird,
member, child: a price about when or who rather than where. That is the
job it is actually for.

Fixed: the WordPress footer printed across two tabs. One stray closing tag
at the foot of two templates closed WordPress’s own content wrapper early,
which dropped “Merci de faire de WordPress votre outil de création de contenu”
into the middle of the Ticket and Payment tabs. The test bench now counts
opening and closing tags in every template, because nobody reads a closing tag
at the foot of a 120-line file and a machine counts them in a millisecond.

The floor plan builder can select more than one thing. Drag a rectangle over
the floor and it picks up every part it touches; shift-click adds one;
Ctrl+A takes the lot. Then move them together, line them
up — left, centre, right, even gaps — duplicate them or remove them in one go.
Before this, the only rectangle gesture in the builder struck seats out: the
obvious way to grab a row of tables quietly crossed out every chair inside it.
A rectangle now means whatever the tool means, and striking seats out lives
with the strike-out tool where it belongs.

The stage is picked up like anything else. It needed its own tool before,
which is not something anybody guesses.

More of the builder: arrow keys nudge a selection by 10 cm, or a metre with
Shift. Ctrl+D duplicates,
Delete removes. The panel now opens on what you have selected
instead of on the template gallery, so clicking a table no longer scrolls its
own settings out of sight. A part has a Level field, and the room has a
name field in the builder.

The name of the room is asked at the top of the assistant, where you already
know it, instead of sitting in a box at the bottom of a tab.

Fixed: the Category column of a guest list showed a dash for every guest who
booked a part of the room, because it looked in one module’s own table instead
of asking the question properly.

1.8.4

The assistant describes a room the way you would describe it out loud. You
say how many rows of tables and how many tables to a row — that lays the hall
out once and numbers every table — and then each zone claims a stretch of it:
“the VIP zone runs from table 1 to table 5.” A zone no longer invents places
of its own, which is what makes the rest possible: the same table can never end
up in two zones, and a table you left out of every zone is named on screen
rather than quietly dropped off the sale.

A price category is no longer the same thing as a zone. A category has its
own name and its own price, and several zones can share one — Premium is
Premium whether it is the left balcony or the right. The booking page sells the
categories; the ticket prints the zone, because the zone is what somebody
actually reads at the door.

The payment question is now the whole story. As well as how people pay and
when the ticket goes out, the assistant asks what to tell a guest paying off the
site, how many places one booking may take, and whether you need a name for
every place or one name for the booking. All four are written into the event.

Prices & places shows the room instead of asking for it again. The four
buttons — no places, one gauge, zones, a plan — and the “What one person is
given” radio group are gone. Both asked what the assistant had just asked, and
the two screens could contradict each other: answer “tables” in the assistant,
tick “a chair” here, and the plugin starts selling chairs at a table nobody
booked. The tab now draws the room that exists, says in a sentence what a
ticket will print, and gives you the two ways back — run the assistant again, or
open the builder on what it built.

The capacity is counted, not typed. With a room in place, the capacity box
is replaced by the room’s own total. Two boxes for one number always ends the
same way: one of them is believed at the door.

Fixed: a balcony forgot it was a balcony. A block’s level and its control
were saved to the database and never read back, so both were lost the first time
the room was loaded again.

Fixed: a hall of tables came back sold chair by chair. The floor plan
builder never sent the room’s grain back when you saved, so a room built around
whole tables was rewritten as a room of single seats.

1.8.3

Fixed: finishing the assistant broke the site. It wrote its entry to the
activity log with the wrong number of arguments, which PHP answers with a fatal
error — so the last click of the assistant produced a white screen. The test
bench now reads every logging call in the plugin and checks it passes what the
log actually asks for.

The assistant walks you through it now. It showed every question at once and
left you to work out where the end was. It asks one question at a time, with
Back and Continue at the bottom and a row of steps along the top showing
where you are, what is behind you, and what is still to come. Continue stays
greyed out, with a reason, until the question in front of you has an answer — a
button that disappears just leaves you looking for it.

1.8.2

Fixed: finishing the assistant said “Security check failed”. Its form was
signed with the name of a different action, which is the same as not signing it
at all — so the one button that mattered died at the last step. Every form is now
checked against the action it posts, by the test bench, so this cannot come back
quietly.

1.8.1

The creation wizard stops asking what the assistant asks. It had a “Tickets”
step wanting a price and a capacity, and then the assistant wanted the same two
numbers again — with the zones and the room that give them meaning. One number
asked on two screens is how two screens end up disagreeing about it. Creating an
event is now three steps, and the last button says what happens next: Set up
places and prices.

1.8.0

An assistant that sets up an event by asking about it. Prices, zones,
capacity and the moment a ticket goes out are one decision described on four
screens, and nobody arriving for the first time can know that. So the assistant
has the conversation instead — starting from a picture of the kind of room you
are filling, not a word for it — and writes the answers into the tabs.

• It opens by itself after you create an event, and there is a button for it on
  Prices & places whenever you want to run it again.
• Every answer decides the next question, and the panel beside it shows the
  consequence: the room being drawn, the prices a guest will see, and what the
  ticket will actually print.
• It tells you what each answer settles and why — “the ticket carries the table,
  so the chair number is not asked: at a round table it tells nobody anything.”
• It owns nothing. It adds no setting of its own; everything it decides is
  still there, field by field, on the tab that always owned it.
• It will not quietly rebuild a room for an event that already has bookings —
  a place is printed on a ticket the moment it is given out.

1.7.0

One tab for money, capacity and places. The price and the capacity lived on
one screen and the room on another, so you could set a capacity of 500 and then
describe a room holding 380 — and nothing said so until somebody was turned away
at the door. They are one decision, so they are now one tab: Prices & places.
A place there is whatever your event hands out: a seat, a table, a row, or a
whole area.

• Pricing & capacity is gone. The price, the currency and the capacity moved
  to Prices & places, along with the price categories and the zones.
• When & where is now Information & details, and holds what a guest is told
  before booking — including this event serves food or drinks and the sponsor
  strip.
• Old links to the removed tab land on Prices & places instead of dropping you
  back at the start.

Fixed: the back button brought a finished booking form back to life. After
booking, pressing Back showed the form still filled in, with the submit button
still greyed out and the countdown frozen — a page that looked broken. A booking
could never have been made twice (the server has refused that since 1.3.0), but
the page now reloads itself, with an empty form, a live clock and a working
button.

1.6.1

Fixed: named zones were all sold at the price of the event. Give three zones
three prices and the booking page offered three zones — at one price. Worse, the
booking was charged that price too, so a zone priced higher than the event was
sold short and one priced lower was overcharged. The room hands the booking form
a zone carrying its own price; the form then asked a separate question — what
does this cost? — that nothing was answering for a zone. It answers now.

Fixed: deleting a zone moved the bookings of the one below it. Zone
references were rebuilt from their position on every save, so removing the first
zone renamed the second into it, and a booking already sold pointed at a zone its
guest never bought. Each zone now carries its own reference.

Fixed: a zone of 25 places sold 40. A capacity that did not divide evenly
into rows was rounded up to fill the last row, silently. The surplus places are
now held back, and a zone holds the number you typed.

1.6.0

Four capabilities that used to be withheld are now in the plugin.

• The ticket studio. Bring in your own artwork, generate colour variations
  of it, and place every printed field yourself on a visual field map, on the
  Designs screen.
• The floor plan editor. Draw the room: the stage, curved rows, round
  tables, standing areas and aisles, with numbering that runs whichever way
  your venue counts — and a guest who picks their own seat on the plan.
• Price categories. VIP, table, early bird, member: several prices on one
  event instead of one.
• Discount codes. Fixed or percentage, limited by date or by number of
  uses.

Nothing was removed and nothing changed shape: existing events, designs, rooms
and settings are read exactly as before. If you never open these screens, the
plugin behaves as it did.

1.2.1

Two security fixes, both reported responsibly by Alik, who tested 1.0.9 in
an isolated environment and sent a clear, accurate write-up of each. Both were
real. Thank you.

Bookings for one event now happen one at a time. Counting the free seats
and taking one were two separate steps, and between two steps another request
fits: two people clicking at the same instant could both be told there was one
seat left, and both take it. The capacity check was never wrong — it was just
on the wrong side of a gap. That gap is now closed with a lock held for the
length of a booking, per event, so a busy night with four events does not queue
into one line. Every capacity rule is now inside it: the event’s own capacity,
each price category, and each area of the room. (CWE-362.)

Forwarding headers are no longer believed by default. The plugin recognises
a visitor by their address in order to count how often they book. It used to
read CF-Connecting-IP, X-Real-IP or X-Forwarded-For if they were present —
but those are written by whoever is making the request, so anybody could invent
one and get a fresh allowance. Only the address the connection actually came
from is used now. If your site really is behind Cloudflare or a reverse proxy,
say so under Settings → Anti-abuse, and the panel shows you what your server is
actually sending so the choice is not a guess. Naming your proxies in
wp-config.php as BFNET_TRUSTED_PROXIES narrows it further. Where a list of
forwarded addresses is read, the plugin now takes the entry the nearest proxy
wrote rather than the one at the front, which is the one a visitor can invent.
(CWE-799.)

Also: a second booking limit counted per email address, so getting around
the per-connection one is no longer enough on its own.

1.2.0

Everything below arrived since 1.0.9. It was built and tested over several
internal builds; this is the first of them anyone is offered, because a version
that was superseded the same week is not a version worth installing.

Rooms and places. An event can now describe where people sit. Three levels,
and nobody is made to climb them: a plain capacity, named zones with a capacity
and a price each, or — with Pro — a drawn floor plan. Seats are worked out
from a rule rather than stored, so a four thousand seat auditorium is twenty
rows in your database and not four thousand. The numbering runs whichever way
your venue counts: left to right, right to left, odd and even out from the
centre, alternating by row. It can skip row I and O, skip 13, start anywhere,
and carry a prefix.

Card payment with Stripe. Set your own secret key and a guest can pay on
Stripe’s own page. No card number reaches your site. A payment is confirmed by
reading it back from Stripe and by a signed message Stripe sends your site —
never by the browser that came back. Your places are held for the length of the
payment session and released on their own if nobody finishes, so the same seat
cannot be sold twice. Card payment is optional, per event: an evening paid at
the door works exactly as it did before.

When the ticket goes out, per event. Acknowledge the booking now and send
the ticket once you have decided where somebody sits, or — when the event has
a room — send it straight away with the place printed on it.

The booking page no longer depends on a page. If a direct link to an event
has nowhere to open, the plugin renders the booking form itself inside your
theme. It also creates the booking page for you, once, rather than leaving a
link that opens nothing.

Fixed

• A booking link opened an empty page on sites that had never added the
  shortcode themselves.
• Guest rows two and after on the manual booking screen were greyed out instead
  of hidden, because the plugin’s own stylesheet beat the browser’s rule.
• The Reserve button was clipped by themes with their own line height.
• Sold-out categories were still offered for booking; a category is now closed
  by the room as well as by its own capacity, and the last place is re-counted
  at the moment the booking is written rather than only when the page was
  drawn.
• Reverting a booking to awaiting payment cleared the check-ins but kept them
  in the history, named.

Also added

• Add a guest by hand, for the bookings that arrive by phone.
• A live floor view of the evening — what is taken, what has arrived, and what
  is full — with the room drawn as the organizer drew it.
• The confirmation screen says which address the email went to, and to look in
  the spam folder.
• Keyboard in the plan editor: undo, redo, delete, escape, shift to select
  several, and a number beside every slider.

1.0.9

• The logo printed on the ticket, on the door’s code screen and beside an
  organizer with no artwork of its own is the anvil alone. It had been the full
  lockup, wordmark included, which the renderer fits inside its box: a wide
  image with words in it shrank to a smudge nobody could read
• The plugin’s page is rewritten. The feature list now says what this plugin
  actually does — the organizer and venue libraries, the export column picker,
  the system check and the archive were all shipped and none of them were
  mentioned, while three of them were wrongly described as belonging to Pro.
  The Pro section says what Pro adds instead of hinting at it, and the FAQ
  answers fifteen questions rather than five. No code changed for this

1.0.8

• Every template under admin/views/ and public/views/ states once, at the top of
  the file, that the PrefixAllGlobals naming rule does not apply to it. A
  template is included from a method, never at file scope, so its variables
  belong to that method’s scope rather than the global one, and PHPCS — reading
  each file on its own — has no way to see where the include happens. No
  variable was renamed and nothing behaves differently

1.0.7

• The plugin is renamed. It was submitted as “2KEvents”, and “2K” is a
  registered trademark of Take-Two Interactive that we have no right to lead a
  name with. The display name, the slug, the text domain, the shortcodes and
  every PHP prefix now read BitForgeNet — the name of the site that publishes
  it, bitforgenet.dev
• Every stylesheet and script the plugin prints goes out through the enqueue
  API. The door station and the two screens around it are their own HTML
  documents, served on their own endpoint before the theme runs, so they had
  carried their CSS and JS inside the page. They now register handles and print
  them by name, the two runtime values arriving through wp_add_inline_style()
  and wp_add_inline_script()
• The admin menu icon is assembled from the mark at runtime and has no file
  behind it, so it registers a style handle with no source rather than printing
  a style tag into the head, and moves to admin_enqueue_scripts
• The code prefix is five characters. It was three, which is under the four the
  directory asks for

1.0.6

• Finished the tidy-up the last two releases started: every code-quality
  suppression in the plugin is now either stated once for a whole file or
  written on the single line it covers, and none of them can change the
  meaning of another one elsewhere in the same file. No behaviour changes

1.0.5

• Fixed suppression comments that did not cover what they appeared to cover.
  One kind switched every code-quality rule back on rather than the one it had
  switched off, quietly undoing notes written elsewhere in the same file; the
  other sat above a nine-line statement instead of around it. No behaviour
  changes for anyone using the plugin

1.0.4

• Request input is now read the way it should be read: eight admin screens
  applied the integer cast to the whole expression rather than to the …