Safer email verification, buy-first paid signup, and easier ticket setup

New accounts confirm their email first

Creating a password account now includes confirming the email address before the rest of Hubbaly relies on it.
This catches a mistyped address straight away, instead of leaving someone unable to sign back in or recover their account later.
Established accounts are not treated as new signups, and email links can never take over an account that already has a password, passkey, multi-factor authentication, single sign-on, or platform access.

A new buyer on a paid public event can create their account, finish payment, and verify their email straight after, while the completed purchase stays safely held.
The approved journey survives refreshes in the same browser for up to 60 minutes, but cannot be reused by another session or another person.
One verification then opens the ticket, full-screen QR code, and joined hub without asking for a username or password again.
Free tickets, waitlists, invitations, and private events still verify first; only the eligible paid journey gets the shortcut.

Account verification emails now send through the same reliable route as the event and ticket emails.
The resend button shows a short countdown before another email can be requested, because delivery can take a few minutes and each replacement supersedes the earlier link; the newest email is always the one that works, and the waiting screen now notices by itself once you have verified.
If the address was typed wrong after a purchase, the buyer can correct it from the purchase screen and verify the right one without losing the ticket.

Ticket setup now uses clearer, denser choice cards, a slimmer progress view, and a one-row action bar that leaves more room for the form on phones.
Buyer limits, returns, event capacity, sales batches, and incomplete answers are explained where organisers need them.
Review links return to the exact step that needs attention, and the flow no longer opens Review with an incomplete ticket or reopens an old saved version.
Closing a ticket with unsaved changes asks first, while a saved draft remains ready to resume later.

Organisers can move ticket types up and down from Event Admin, and that order is used everywhere buyers choose tickets.
On events with several dates, passes appear first, dates stay chronological, and tickets can be arranged inside the relevant pass or date.
Automatic system tickets remain separate, so organiser choices do not disturb the platform’s internal ticket records.
The saved order survives reloads and stays consistent across public event pages, member views, and checkout.

Checkout refreshes ticket availability and buyer limits before reserving anything, while keeping the price and sales batch the buyer actually accepted.
Used-up hub share links now stop cleanly instead of creating an extra join request.

Creating a hub on a phone keeps the Name field and action buttons visible above the keyboard.
Feedback forms enforce the stated answer lengths, and participant requests reach the people who really attended without duplicate or guest-placeholder messages.
Event communication reports now reconcile in-app, push, and email results more accurately.
Ticket setup, checkout, and email verification have broader automated coverage across desktop, mobile, and real database journeys.