Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Markdown formatting in registration descriptions
Repositories: Partners dashboard. Status: Validated locally; hosted display remains to verify.
What’s Changed
EMS editors for registration tiers, add-ons, inclusions, and variants now provide the shared Markdown formatting toolbar and preview. Their catalog cards render the same Markdown extensions used on Rego, including tables, highlights, footnotes, and diagrams. Dashboard text areas, including the design canvas examples, and previews use the shared editor and renderer as well.
Impact
Organizers can format longer descriptions while editing and review how they will appear to attendees. Existing saved descriptions remain editable as plain Markdown text.
Validation
Partners typecheck and focused registration catalog browser checks passed. The Rego attendee views already use the shared safe Markdown component for tier, add-on, inclusion, and variant descriptions; hosted end-to-end display remains to verify after release.
More control over event Google Wallet passes
Repositories: Partners dashboard and Partners API. Status: Validated locally; hosted Wallet approval and display remain to verify.
What’s Changed
The EMS Google Wallet editor now fills event dates and venue from event and registration settings, organizer contact from the partner profile, and eligible public artwork from event and partner images. Organizers can edit those details, add a doors-open time and ticket conditions, choose wording for registration and tier fields, add a wide logo, and see a layout guide while editing. Saved event details are sent through Google’s Event Ticket class schema.
Impact
Partner teams can prepare a more complete pass without re-entering information already stored in EMS. Attendee and Dealers Den passes continue to share the event class, while each ticket retains its own registration reference and barcode. The actual Wallet layout remains controlled by Google.
Validation
Partners and API typechecks passed. The API presentation-contract test covered derived values, edits, clearing optional fields, provider payload fields, and invalid input. A local browser fixture checked the editor at desktop and mobile sizes; this does not confirm hosted Google approval or a live saved pass.
Wallet button follows event configuration
Repository: Rego site. Status: Validated locally; hosted display remains to verify.
What’s Changed
The Add to Google Wallet action on attendee and Dealers Den event passes now appears only when the organizer has configured Wallet for that event and the pass is enabled. Events without Wallet configuration show only their QR pass controls.
Impact
Attendees no longer see a Wallet action or Wallet availability message for events that have not configured it. Configured events continue to show the action when it is available.
Validation
Rego typecheck and production build passed. Intercepted browser checks on standard and Dealers Den passes verified the configured action, the unconfigured hidden state, and mobile and desktop rendering; they did not request a live Wallet pass.
Included designs shown at rego review
Repository: Rego site. Status: Validated locally; hosted display remains to verify.
What’s Changed
The assigned-design summary now appears on the final rego review screen after the payment screen. It no longer takes up space while attendees choose a tier. Design assignment and any item-specific questions still happen before submission.
Impact
Attendees can check their assigned designs alongside their answers and payment details before submitting. The list also appears at review for regos that do not collect payment.
Validation
Rego typecheck and production build passed. An intercepted mobile and desktop paid-rego browser fixture verified the list is absent from tier and payment, appears at review, and does not submit or allocate an item early.
Fursona choices in registration questions
Repository: Rego site. Status: Validated locally; hosted display remains to verify.
What’s Changed
Fursona questions attached to a registration tier, inclusion, add-on, or event now show the attendee’s saved fursonas. Attendees can create a fursona from the question and use it immediately as that answer.
Impact
Attendees can complete item-specific fursona questions without leaving registration. A fursona created for one question is selected for that question.
Validation
Rego typecheck and production build passed. A mobile and desktop browser fixture verified the saved options, inline creation, and question selection with intercepted sample API data; it did not create a rego.
Prefill choices remain editable
Repository: Rego site. Status: Validated locally; hosted display remains to verify.
What’s Changed
The event page and prefill form now explain that attendees can edit and resave a prefill later. When registration opens, they can choose a different available tier and add-ons before submitting their rego.
Impact
Attendees can save early choices without treating the prefill as a fixed order. Prices and availability are checked again during registration.
Validation
Rego typecheck and production build passed. Mobile and desktop browser checks showed the updated event card and prefill form; the checks used intercepted sample event data and did not create a rego.
Gift receiver eligibility matches existing regos
Repositories: Rego site and Partners API. Status: Validated locally; hosted release remains to verify.
What’s Changed
The gift form now explains when a receiver already has a rego or an unredeemed gift and keeps the giver on the receiver step. The API checks for any existing rego for the event both during receiver lookup and before creating a gift.
Impact
Attendees cannot be shown as gift eligible when the event already has a rego for their account. Gift givers can choose another receiver without entering payment details first.
Validation
Rego typecheck, production build, and desktop and mobile browser fixtures passed. Partners API typecheck passed. Hosted behavior remains to verify after release.
Faster inclusion review in EMS
Repository: Partners dashboard. Status: Validated locally; hosted display remains to verify.
What’s Changed
Each registration inclusion card now has an Active in Rego switch and an expandable preview of every variant. The preview shows names, available images, descriptions, variant status, and question counts. Turning off an inclusion keeps its tier choices saved; operators save the registration configuration to publish the change.
Impact
Event operators can review variants and pause an inclusion without opening its edit dialog.
Validation
The desktop and mobile browser fixture passed, including switching an inclusion off and on without losing tier selections. Partners typecheck and production build passed.
Consistent random draw labels in registration tiers
Repository: Rego site. Status: Validated locally; hosted display to verify after release.
What’s Changed
Grouped inclusion headings now say “Random draw” wherever designs are randomly selected. Sets with both fixed designs and a draw name both parts, while bundles name their random draw explicitly. Inclusion details use the same term.
Impact
Attendees can identify which designs are guaranteed and which come from a random draw across every tier.
Validation
Desktop and mobile tier comparison fixtures passed for sets, mixed sets, bundles, and ordinary draws. Rego typecheck and production build passed.
Clearer changes between registration tiers
Repository: Rego site. Status: Validated locally; hosted display to verify after release.
What’s Changed
Tier comparisons now describe when a random draw becomes a list of fixed designs, or fixed designs become a random draw. They also explain when variants change from being bundled with the base inclusion to replacing it, and when the base inclusion returns alongside its variants. Each change appears with its inclusion.
Impact
Attendees can tell whether a higher tier guarantees particular designs and whether it still includes the base item.
Validation
Desktop and mobile browser fixtures covered both directions of each switch, including unchanged random pools. Rego typecheck and production build passed.