Furries PH Docs
Dashboard

Updates

Platform Updates

Public-facing release notes for meaningful changes across Furries PH operational systems.

First created Last updated

Showing release notes 491-500 of 1461
2026-09-2610:39

Dashboard activity and analytics appear sooner

Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

The dashboard now displays event activity and workspace links as soon as those sections are ready, even when report activity is still loading. Finance, inventory, and registration analytics show their page headings during the first read. Refreshes keep previously loaded analytics visible, and registration analytics retries failed reads automatically.

Impact

Partner teams can start navigating and reading available information without waiting for every dashboard request. Slow or failed analytics refreshes no longer replace the current view with a full-page loading state. Saved-state checks after uncertain changes continue automatically without requiring a manual recheck.

Validation

Local browser fixtures covered a held report request, analytics first reads, same-event refreshes, and failed-read recovery. Typecheck and production build passed locally. Authenticated production route and save timings remain to verify.

2026-09-2610:39

Profile and forecast pages keep working during checks

Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

Profile settings and event forecasting show their page content immediately while saved data loads. After an uncertain profile or forecast control change, the dashboard checks the latest saved state automatically. Person Profiles also keeps its list visible during refresh and after saves.

Impact

Partner teams can keep reading current content and retain an active profile draft during slow or failed reads. Repeat changes wait for a saved-state check; uncertain writes are not sent again automatically. If profile values differ, the latest saved values are shown for review.

Validation

Local browser fixtures covered delayed and failed reads, automatic rechecks, retained content, and write locks. Typecheck and production build passed. Authenticated hosted route timings remain to verify.

2026-09-2610:39

Event options appear as their checks finish

Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

On an event page, shop, feedback, Dealers Den, volunteer, activity, and attendee checks now update their own options as each response arrives. A slow optional service no longer holds back unrelated event options. Account changes still clear attendee-specific results.

Impact

Visitors can use available event options sooner while other event sections continue loading in place.

Validation

Rego typecheck, production build, and route-contract checks passed. A mobile browser fixture held the shop response while confirming that Dealers Den appeared, then passed the existing event, waitlist, volunteer, and activity checks. Authenticated production timing remains to verify.

2026-09-2610:39

Rego home loads the selected page first

Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

The public event list now waits for a visitor to hover, focus, or touch an event card before downloading the event-detail route. The shared shell loads MFA and waitlist dialog code when those dialogs are needed, while profile and security checks continue as before.

Impact

The home page can show its event list without competing with event-detail and dialog downloads. Choosing an event still begins the next route download immediately on interaction.

Validation

Rego typecheck, production build, and route-contract checks passed. Mobile and desktop production-preview fixtures observed 39 assets for idle home and 76 after event-card intent. Profile, MFA, waitlist, account-switch, and session-boundary browser fixtures passed. Authenticated production timing remains to verify.

2026-09-2610:39

More dashboard saves recheck automatically

Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

Refund reviews, settlements, registration roster updates, HR settings, volunteer application reviews, and email campaign changes now start checking saved state automatically when the result needs confirmation. The email composer opens as soon as recipient data arrives while campaign history loads separately.

Impact

Partner and event teams can keep their current lists and drafts visible while the dashboard checks the latest records. Repeat changes remain paused until saved state is confirmed; email campaigns are not sent or cancelled again during a status recheck.

Validation

Local typecheck, production build, and focused browser fixtures for these workflows passed, including failed reads and automatic recovery. Authenticated hosted speed and real provider delivery remain to verify.

2026-09-2610:39

Dashboard checks saved changes automatically

Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

The dashboard starts checking saved state automatically after an uncertain change in registration, affiliate tracking, SMS, volunteer positions, staffing, accounting, payments, and point of sale. Editors and draft values stay on screen during refresh. SMS delivery data starts loading alongside Android readiness, and event linked work starts alongside event details.

Impact

Partner and event teams no longer need to press a recheck button after a save with an unclear result. Repeat actions stay paused until current records are read. Financial changes and uncertain SMS sends still ask an operator to review the refreshed outcome before continuing.

Validation

Local typecheck, production build, and focused browser fixtures for the affected workspaces passed. The fixtures exercised delayed and failed reads, retained drafts, and automatic retry without replaying a write. Authenticated hosted speed and real provider delivery were not measured in this release.

2026-09-2610:39

Event pages load lighter community icons

Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

Event and registration pages now use only the Discord and Telegram icon shapes they need. The full brand icon stylesheet and font are no longer part of their first load.

Impact

Attendees download less styling and font data when opening an event or starting a rego. Community role and chat details still appear in the same place.

Validation

Rego typecheck, production build, and route-contract checks passed. The desktop and mobile community-benefits browser fixture confirmed both icons and account-link controls. The built event HTML no longer links the brand stylesheet, and the build emits no brand font. Authenticated production timing remains to verify.

2026-09-2610:39

Notification inbox stays usable while loading

Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

The notification inbox now shows its heading and controls immediately. Existing messages remain visible while the attendee switches filters or loads another page. Read actions can finish during pagination, and the inbox reconciles with the server after a bulk read.

Impact

Attendees can continue reading updates and marking them read without a page reload or a blank inbox. A slow or failed list request keeps the already loaded messages on screen with an inline retry.

Validation

Rego typecheck, production build, and route-contract checks passed. Mobile and desktop browser fixtures held pagination and filter responses, marked messages read during the wait, and verified no navigation or loss of read status. Authenticated production timing remains to verify.

2026-09-2610:39

Registration and volunteer editors stay ready

Repository: Partners. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

Event Management registration settings and volunteer applications and positions now keep their current forms, lists, filters, and expanded cards visible while refreshing. Registration edits made during a delayed read or after a save remain available. A save with an uncertain result asks for a read-only recheck before another attempt, and unchanged registration prefixes skip an extra availability check. Registration catalog cards also fit narrow screens.

Impact

Event operators can continue reviewing and editing during routine updates without a page reload. Failed refreshes offer an inline retry while keeping the last loaded work visible.

Validation

Focused browser fixtures exercised delayed and failed reads, newer edits during a save, recheck without duplicate writes, and desktop/mobile layouts. Partners typecheck and production build passed. Authenticated production timing remains to verify.

2026-09-2610:39

Faster signed-in checks and waitlist prompts

Repository: Rego. Status: Released through the linked GitHub branch; authenticated production timing remains to verify.

What’s Changed

Rego now checks attendee profile readiness and site-access MFA policy at the same time. The read-only MFA status request no longer queues unrelated page reads behind a cookie-changing auth action. A session nearing expiry still refreshes before protected reads, and a pending waitlist offer still waits for both current checks.

Impact

Signed-in pages can continue loading while the security policy is checked. Attendees with a waitlist offer should see its time-sensitive prompt sooner. Profile setup, required authenticator approval, and account switching remain enforced.

Validation

Rego typecheck, production build, and route-contract checks passed. Mobile and desktop browser fixtures verified overlapping reads, offer gating, one refresh for an expiring session, and incomplete-profile redirect. Session-boundary and account-switch/MFA fixtures passed. Authenticated production timing remains to verify.

All docs