Hi.Events v2.1.0

This release adds follow-up and eligibility questions with a redesigned registration questions builder, lets buyers report offline payments or send a payment link to someone else, and adds Czech.

What's new

• Redesigned registration questions builder: order and attendee questions on one page with a live checkout preview, drag-to-reorder options, ready-made templates (dietary requirements, t-shirt size and more), and attendee questions that apply to all tickets, including ones you add later. (#1466)
• Follow-up questions: ask a question only when an earlier answer calls for it. (#1466)
• Eligibility questions: mark answers that make someone ineligible, and checkout stops with your message. (#1466)
• "I've paid" reporting: on a pay-later order, the buyer can tell you they've paid, with an optional note such as a PO number. The order is marked Payment reported and you get an email. (#1460)
• Payment links: when someone else is paying, such as a finance team, the buyer can send them a link to pay, and their tickets stay held in the meantime. (#1460)
• Suspend accounts from the admin panel: their events and organizer pages go back to draft, and their members can't sign in or use API keys. (#1444)
• Czech translation, thanks to @skvost. (#1267)

Fixes

• A single-use promo code that unlocks hidden products could be shared and used by any number of buyers while the first checkout using it was still open. Hidden products now need a code with uses left, and a used-up code is reported as invalid. (#1478)
• Embedded checkout could report the same order to the host page more than once, so sites tracking hievents:order-completed counted some sales twice. (#1441)
• Archived events and custom email templates are now spam-checked, and approving a flagged event returns it to its previous status instead of publishing it. (#1463)
• The events sitemap now lists only live events that are upcoming or ended in the last 120 days. (#1446)
• Docker installs still using the example JWT_SECRET now get Docker instructions in the log, since php artisan jwt:secret doesn't take effect inside the container. (#1442)

Full Changelog: v2.0.0...v2.1.0