Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Faster Rego browsing and in-place updates
Repository: Rego. Status: Git-linked production deployment and hosted assets verified; authenticated save timing remains to verify.
What’s Changed
The events page now displays its published event list while live details refresh. Event pages show core details before optional fee information arrives. Common navigation paths preload route code, and internal links in registration, account, and affiliate flows stay within the app. Friends, security, affiliate payout, transaction actions, Dealers Den withdrawals, and staff and vollie shift tracking keep their current content visible while saved changes refresh.
Impact
Attendees can start browsing sooner and continue using the page after a save without a full browser reload or a blank loading screen. Current availability, checkout totals, permissions, and saved records remain API controlled.
Validation
Rego typecheck and build passed. Desktop/mobile browser fixtures confirmed immediate event cards during a delayed live read, Friends mutation retries, account security flows, attendee shell behavior, and staffing and vollie content remaining visible through delayed post-save reads. Cloudflare’s production deployments list Rego commits 50f1c360, 1ceb3dc8, and 7f489a74; the custom domain serves the updated event list and roster bundles. The Docs production deployment and hosted Updates page display this entry. Provider backed saves and real attendee timing remain to verify.
Faster Partner Dashboard navigation and quieter saves
Repository: Partners. Status: Git-linked dashboard deployed; authenticated behavior remains to verify.
What’s Changed
The dashboard now loads protected workspaces when opened instead of downloading every workspace at startup, and starts fetching a workspace’s code when an operator pauses over or focuses its link. Moving between dashboard pages keeps the active session, while sign-in and partner-scope changes still refresh access. Event Management keeps existing content visible while refreshing event lists, configuration, registrations, waitlists, check-in queues, coupons, staff rosters, activity submissions, POS sales, and transfer and upgrade reviews. Finance, Event Planning, Asset Management, Reports, Pawsports, organization settings, reminder readiness, and Surveys keep loaded records visible during refreshes and show refresh errors in place.
Impact
Partner teams should reach workspaces sooner and keep their place while saving or refreshing event configuration, finance records, planning work, asset operations, reports, and surveys. A confirmed POS sale leaves its receipt and counter visible while stock and the attendee list refresh for the next sale. A failed refresh leaves the last successful content visible with an error message and a way to retry. Controls that require current data pause until the refresh finishes.
Validation
Partners typecheck and build passed. Local browser fixtures checked route preloading, session navigation, EMS review and roster refresh, POS post-sale stock and attendee reads, planning files and decisions, asset registers and operations, reports and enforcement, Pawsports, organization settings, surveys, and Finance refresh/error recovery. The Finance operations fixture checked 30 route/viewport states, including a failed refresh that kept loaded records visible. Three fresh browser sessions measured public sign-in first content between 132 and 412 ms from one workstation. Cloudflare Pages completed the preceding Partners and Docs deployments. The registration roster fixture requires a local authenticated session that was unavailable in this run; authenticated hosted load and save times remain to verify.
Suggested friends in the gift receiver search card
Repository: Rego. Status: Validated locally; hosted display remains to verify.
What’s Changed
The gift receiver field, eligibility feedback, suggested friends, and optional Friends search now share one card. Suggested friends appear below the receiver username field instead of in a separate Friends card.
Impact
Attendees can check any receiver and choose a suggested friend in the same part of the gift form. Friends remains optional.
Validation
Rego typecheck and the desktop/mobile gift receiver browser fixture passed. The fixture checks suggestion placement, friend selection, receiver eligibility feedback, and search behavior.
More reliable Social meetup and sponsorship status
Repository: Social. Status: Validated locally; optional capabilities remain off.
What’s Changed
If a private meetup invitation or decision returns an uncertain result, Social now asks for a fresh request list before another attempt. A failed refresh cannot leave an old request list looking current. Separately, a hidden custom sponsorship no longer claims to have rendered: the app declares it only after the card is actually visible in the foreground.
Impact
These changes protect future opt-in meetups from duplicate actions and keep custom sponsorship measurement honest when a privacy tool hides a card. They do not enable location sharing, ads, or provider scripts.
Validation
Social typecheck, 623 tests, a ten-check synthetic meetup browser flow, and an isolated Chromium/uBlock Origin Lite test passed. The latter kept ten organic posts visible and recorded no declaration for a cosmetically hidden synthetic card. Production meetup, provider and wider privacy-tool checks remain outstanding.
Gift receiver feedback beside the username field
Repository: Rego. Status: Validated locally; hosted display remains to verify.
What’s Changed
When a proposed gift receiver cannot receive a rego, the reason now appears below the receiver username field in a card matching the successful receiver confirmation’s spacing and layout. Editing the username clears the old warning so a new receiver can be checked.
Impact
Attendees see receiver eligibility feedback beside the field they need to change, on desktop and mobile.
Validation
Rego typecheck and the desktop/mobile gift receiver browser fixture passed. The fixture checks that the warning stays inside the receiver card and aligns with the successful confirmation.
Safer Social destination, sponsorship, and Event mapping recovery
Repositories: Social and Admin. Status: Validated locally; optional capabilities remain off.
What’s Changed
Closing a manually chosen meeting point now cancels even a start request whose response has not arrived. If cancellation cannot be confirmed, Social keeps a visible warning and retry instead of allowing another share. Optional sponsorship receipt handling stays usable when browser privacy controls block tab coordination. In Admin, an uncertain CMS Event mapping response now requires a fresh inventory and exact-record review before another attempt.
Impact
These safeguards protect future opt-in workflows. They do not enable public location sharing, ads, provider scripts, or automatically map any CMS Event. Staff still need to confirm a real CMS-to-operational Event pair in native systems before making a mapping.
Validation
Social typecheck, 623 tests, production build, and a 16-check synthetic desktop/mobile destination-sharing browser flow passed. Admin typecheck, 27 tests, build, and a synthetic uncertain-mapping browser view passed. Live recipient sharing, ad delivery, and staff mapping remain unverified.
Clearer tier changes for sticker designs
Repositories: Rego and Partners. Status: Validated locally; hosted display remains to verify.
What’s Changed
When a higher tier changes an inclusion from a random draw to guaranteed designs, its comparison note now states the previous draw count and the new guaranteed-design count. The draw change takes precedence over a separate bundle/alternative flag change, so the note describes the visible offering instead of claiming a base item was previously replaced. Partners also labels these selection groups “Guaranteed variants” in the catalog editor and its per-attendee preview.
Impact
Attendees comparing tiers can see exactly how many designs are assigned at each tier.
Validation
Rego and Partners typechecks passed. Their desktop/mobile browser fixtures verified the renamed selection mode and tier comparison copy, including a random-to-guaranteed change with a simultaneous behavior flag change.
Clearer cancellation of Social meeting points
Repository: Social. Status: Validated locally; recipient sharing remains off.
What’s Changed
If a temporary manually chosen destination is accepted after its panel closes, the app now sends an immediate stop. If the stop cannot be confirmed, the closed panel keeps a visible warning and retry action. The reviewed audience may still see the destination until its 15-minute expiry.
Impact
This improves the future opt-in meeting-point flow without requesting device location or activating the public feature. Members still need a separate recipient review and consent step when the feature is eventually approved.
Validation
A capability-gated browser exercise passed 15 checks, including cancellation retry, and captured the closed and unconfirmed-cancellation states at desktop and mobile widths. Managed authorization and release checks remain outstanding.
Safer nearby-session expiry in Social
Repository: Social. Status: Validated locally; not activated.
What’s Changed
The future native nearby-finding flow now accounts for time spent starting device ranging when it sets its session timeout. A clock that appears to move backward stops the start instead of extending the session.
Impact
There is no change to the current Social experience: location sharing and native precision finding remain off. This safeguard applies if a supported native finding flow is approved and released later.
Validation
Social typecheck, 620 tests, and the static Pages build passed. Real-device pairing, permissions, policy, and release verification remain outstanding.
Full add-on descriptions on Rego
Repository: Rego. Status: Validated locally; hosted display remains to verify.
What’s Changed
Event add-on and separately sold merchandise cards now include a details action when the organiser provides a description. The dialog shows the complete description with the shared markdown-ext renderer, including formatting, tables, and other supported extensions.
Impact
Attendees can read the full description even when the card preview is shortened. Tier, inclusion, and variant detail views continue to use the same safe renderer.
Validation
Rego typecheck, markdown-ext browser verification, and desktop and mobile tier comparison fixtures passed.