Ladna
Current version 0.166.0

What's new in Ladna

0.166.0

One private-lesson pass for several disciplines

  • Individual-lesson passes can now cover several selected class formats, so clients can use one package across disciplines while the public price list keeps one offer per package.
  • Choose the covered formats in Class passes & prices. Existing selections, trainer and room restrictions stay in place; newly created formats are included only when an owner selects them.
Pending release commit.
0.165.1

SMS auto top-up recovery

  • SMS auto top-up now resumes when a new month begins in the studio’s time zone after reaching its monthly limit. Page and email notices explain the limit and how to continue sooner, while failed card payments remain paused for owner review.
Release commit.
0.165.0

Festival payment recovery

  • Festival participants can now check a waiting Monopay payment with the bank, reopen a valid checkout, and retry after an unpaid invoice expires or fails. Automatic checks also recover missed confirmations without creating duplicate payments.
  • Eligible withdrawn, unpaid application drafts can be restored to continue registration. Payments made on time can complete their step when bank confirmation arrives after the deadline, while current registration and review requirements still apply.
Pending release commit.
0.164.0

Promotion codes for tickets and class passes

  • Studio owners and authorized Event and Festival teams can now create fixed or percentage promotion codes for selected Event tickets, Festival admission types, and class-pass plans, with active dates and total or per-customer limits.
  • Public checkout recalculates eligible prices before payment, supports fully discounted ticket and class-pass issuance, and preserves the original subtotal, discount, final amount, and promotion snapshot in customer and finance history.
  • Event and Festival Monobank checkout now opens directly on iPhone instead of relying on an embedded payment frame that iOS may block.
Pending release commit.
0.163.1

Reliable Monobank payment completion

  • Monobank processing and failed callbacks now use the original invoice amount and respect the providerʼs update time, so Event tickets and other payments no longer reject valid status updates or move backward when callbacks arrive out of order.
  • Trial class-pass eligibility is now secured before opening the payment page and honored when the confirmed payment returns. A guarded audited exception can recover an already charged legacy trial purchase without creating studio cash or hiding the responsible actor and reason.
Pending release commit.
0.163.0

Custom Festival step-completion messages

  • Festival teams can now set separate Ukrainian and English Email, SMS, and Telegram text for every registration step, including Summary. Empty fields continue using Ladnaʼs localized defaults, while %name% and %category% insert the application performers and category.
  • A message is created after every new step approval, including automatic and paid Payment steps and final confirmation. Existing cabinet links, Telegram buttons, email presentation, and Ladna footer remain in place.
Pending release commit.
0.162.0

Fresh Festival confirmations and a livelier Battle audience screen

  • Festival staff now receive the latest readiness checks whenever they open Fully confirm, so reviews and payments completed on the same page no longer leave a stale blocker dialog.
  • The Windows Ladna Battle Meter audience screen now adds an animated 3–2–1 countdown, applause-responsive waves, clearer live and accepted readings, and the Ladna mascot cheering for each performer.
Pending release commit.
0.161.0

Independent Festival field-review notifications

  • Festival teams can now configure accepted, rejected, and waived registration-field notifications independently for Email, SMS, participant Telegram, and owner Telegram. Routine accepted-field messages can be disabled while correction alerts stay active.
  • Communication settings now keep all four channel controls aligned in responsive columns, including on wide screens.
Pending release commit.
0.160.0

Festival Battle audience meter

  • Festival teams can now connect the Windows Ladna Battle Meter with a securely scoped studio API token, select a ready match and microphone, compare two applause captures against one ambient baseline, and present the live vote on a separate audience screen without recording or uploading audio.
  • The meter submits safely retryable audience scores and waits for Ladnaʼs official 50/50 jury-and-audience result, including manager-resolved ties. Festival administration and judge interfaces now use the general Battles name for every competition style.
Pending release commit.
0.159.0

Faster Festival applicant review

  • Authorized Festival registration staff can now see the applicantʼs name, phone, email, Telegram, and Instagram together in one full-width contact block with direct links.
  • Category requirements now open from a compact action beside Change category, keeping the application review page shorter while preserving the complete guidance.
Pending release commit.
0.158.0

AI music duplicate review for Festivals

  • Festival teams can now check the Media report for likely duplicate music selections with one AI-assisted action. The review compares the marked text from every eligible application and recognizes likely matches despite spelling mistakes, formatting, language, or transliteration differences.
  • Each result links back to the relevant applications and fields for human review. The check is advisory and never changes application data.
Pending release commit.
0.157.1

Compact Festival category changes

  • Festival staff can now change an application category from a compact action in the category summary. The category selector and required reason open in a focused confirmation dialog instead of occupying the full application page.
Pending release commit.
0.157.0

Clearer Festival application review and communication

  • Festival application lists now show every registration step and status. Application history has its own filterable page, grouping lifecycle, reviews, fields, payments, program and results, and other activity.
  • Application decisions now use action-specific confirmations, require correction details where needed, and show every blocker before final confirmation instead of failing only after the action.
  • Festival Communication now opens Notification scenarios by default and repeats the same three buttons across separate History, Announcements, and Scenarios pages. Email can be enabled or disabled independently for every scenario, and each scenario explains what triggers it.
Pending release commit.
0.156.0

Festival participant entrance passes and friend tickets

  • Approved Festival performers and their selected confirmed helpers now receive separate entrance passes. Door teams can scan and search them with dedicated participant and helper counters without consuming guest ticket inventory; lost eligibility disables the pass, while completed Festivals remain untouched.
  • The participant cabinet now keeps entrance passes and tickets bought for friends in separate tabs. Participants can email or print their passes and use a prefilled public checkout to buy ordinary admission tickets for friends while preserving the established private ticket-delivery flow.
Pending release commit.
0.155.0

Direct Festival Telegram access

  • The Velvet Night landing now links its active Series Telegram bot beside the main application and ticket actions and again in the Festival footer. Empty live-timeline space no longer leaves a large gap before the authored Festival information.
  • Participant cabinets now use clear button-styled navigation and place every active Festival Series Telegram bot beside Help for quicker access.
Pending release commit.
0.154.0

Festival information and independent Telegram delivery

  • An exact Festival in the Series Mini App now presents every active public organizer-authored information block as a compact disclosure, alongside the published timeline, schedule, results, and documents. The unused Notifications tab is gone, and external Festival, application, and ticket actions use the neutral Go to page label.
  • Festival communication settings now place participant Telegram beside Email and SMS for every scenario. Telegram is enabled by default and is delivered independently rather than replacing or falling back to SMS; the separate studio-owner Telegram alert remains available.
Pending release commit.
0.153.2

Compact Festival Telegram experience

  • Authorized Festival subscribers now move directly from the compact Series hero to the Mini App navigation without the redundant Series summary or large authorization card. The Calendar is a compact edition list; opening one Festival replaces the poster with an Evolution-style operational view using a small cover, date, venue, expandable published information, and a clear back action. Edition actions now mirror the participant cabinet with New application, confirmation for an additional application, and the existing application count in one aligned full-width stack. After phone authorization, the bot explicitly removes Telegram’s contact-sharing keyboard before presenting the Festival button.
Pending release commit.
0.153.1

Festival-branded Telegram Mini App

  • Each Festival Series Telegram Mini App now uses that Series brand colour and the nearest live or upcoming published edition’s configured desktop and mobile cover images as its main hero visual. If no future cover is available, it falls back to the newest published Festival cover and then to the existing gradient.
Pending release commit.
0.153.0

Festival Series Telegram companion

  • Studio owners can connect one independent Telegram bot to each Festival Series. Its Mini App presents the Series calendar, previous and upcoming editions, published schedules and results, live timelines, applications, team statistics, tickets, streaming access, and organizer contacts.
  • A private Telegram contact securely authorizes one human for the Series and can link separate participant and ticket-buyer profiles without merging their roles. Registration, profile changes, payments, ticket checkout, and private order access remain in Ladna through short-lived single-use handoffs.
  • Subscribed participants and ticket buyers can receive Festival lifecycle messages in Telegram alongside existing email and SMS delivery. Required messages remain active while optional reminders, schedule changes, and announcements follow the participant’s notification preferences.
Pending release commit.
0.152.0

Exact missing-pass booking report

  • The dashboard missing-pass indicator now opens one account-wide report with every exact booking, optional location filtering, assigned trainers, and a direct link to the class in the schedule or history.
  • Only booked or attended entries without a pass reservation, direct payment, or active waiver require attention. An explicitly recorded no-show is no longer treated as a payment problem or attached to a later pass, while existing payments, refunds, and used pass sessions remain unchanged.
  • The owner help now explains how to review and correct these bookings and how no-shows without a pass are handled.
Pending release commit.