Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Event previews open with less code
Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
An event’s published overview can appear before its markdown renderer and item detail dialogs finish loading. Current event information still replaces that overview, including registration tiers and inclusions. If optional detail code fails to load, readable event text remains and item details offer a reload action.
Impact
Direct event links request less JavaScript before showing useful event information. Attendees can continue opening inclusion details when current data arrives. No action is needed.
Validation
Rego typecheck, route contract, production build, and mobile and desktop browser fixtures passed. The local event route preloaded about 84 KB less raw JavaScript. Published preview, live tiers, item dialogs, module-failure recovery, gift entry, variation labels, private-field exclusion, and API-error retry were checked. The linked Pages build succeeded; the hosted event route and asset responded correctly without preloading the optional detail modules. Hosted signed-in timing remains to verify.
Dashboard work lists appear sooner
Repository: Partners. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
EMS registration, coupon, and affiliate lists now appear as soon as their authorized reads finish. Event Planning shows its catalog and change history independently of slower settings. Finance Outflows shares capability and account reads across rows, reducing repeat requests in large lists. A confirmed report enforcement action updates its on-screen result immediately; if the response is interrupted, the dashboard checks the exact saved state automatically before permitting another action.
Impact
Event, planning, finance, and safety operators should see their current work sooner and keep the page open while a save is checked. No action is needed.
Validation
Focused local browser fixtures covered early lists, held refreshes, scope changes, shared Finance reads, and confirmed or uncertain enforcement saves. Partners typecheck and production build passed, and the linked Pages build succeeded. Hosted signed-in timing and real-account saves remain to verify.
Gift entry and affiliate payout saves do less work
Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.
What’s Changed
Opening a rego gift link now loads the full gift form after attendee authentication. Anonymous visitors avoid downloading the protected form, while the current event still decides whether gifting is available. A confirmed Affiliate payout save updates the form from the API response without reloading the entire rewards list; an interrupted response still triggers a read to check the result. Gift history also loads identity and promised-inclusion details concurrently after fetching the attendee’s owned gifts.
Impact
Gift links request less code on direct entry, Affiliate payout saves keep the form in place, and gift history needs less serial server work. No action is needed.
Validation
Rego typecheck, route contract, production build, and mobile and desktop gift and Affiliate browser fixtures passed. Gift entry preloaded about 219 KB less raw JavaScript (30.3%) in the local build. Confirmed payout saves made one initial list read and one write with one browser document; lost-response reconciliation and account isolation passed. API typecheck, promised-inclusion parity, and a synthetic overlap fixture passed. Both linked builds succeeded; hosted Rego gift and Affiliate routes and their entry assets responded correctly. Hosted authenticated timing and real-account saves remain to verify.
Registration forms appear sooner and dealer edits stay open
Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
Once the required registration details arrive, the already downloaded form now appears sooner. A failed form download offers an explicit retry. Saving an existing pending Dealers Den application keeps the edit form open with an inline confirmation. First submissions and requested resubmissions still show their completion screen.
Impact
Attendees see the registration choices sooner after event details finish loading. Dealers can continue editing a saved application without reopening it. No action is needed.
Validation
Rego typecheck and production build passed. In a local registration fixture, the first tier appeared 44–88 ms after the required read, compared with 337–355 ms before this change. Five registration scenarios covered anonymous, signed-in, teaser, and failed-download recovery. Three Dealers Den browser scenarios covered ordinary edits, first submission, and requested resubmission, including a second save using the returned revision. The linked Pages build succeeded, and hosted registration and Dealers Den routes and the registration asset responded correctly. Hosted signed-in timing and real-account saves remain to verify.
Dashboard access and review lists start sooner
Repository: Partners. Status: Linked release succeeded; signed-in cold-start and save timing remain to verify.
What’s Changed
For a signed-in visit, the dashboard now starts its access check while page code loads. EMS upgrade requests and Finance custody sessions appear before slower event or account details finish. Dealers Den settings and packages appear independently, and loaded packages remain visible during refresh. Confirmed custody changes update their row promptly; uncertain outcomes trigger automatic read-only checks while another command stays locked.
Impact
Event and finance operators should reach their request lists and saved work sooner. Decisions and cash actions still wait for current authorized data. No action is needed.
Validation
Local browser fixtures covered delayed reads, scope changes, no duplicate access request, confirmed custody receipts, and uncertain writes. Partners typecheck and production build passed, and the linked Pages build succeeded. Hosted cold-start timing and live save journeys remain to verify.
Registration and profile setup load less code upfront
Repository: Rego. Status: Linked release succeeded; hosted signed-in timing remains to verify.
What’s Changed
Registration pages now load the attendee form after the current event allows registration. Visitors who need to sign in or who see an event teaser avoid downloading that form. Profile Setup loads security and legal controls as attendees approach those steps, while keeping the existing save and acceptance checks.
Impact
The first view of registration and Profile Setup requests less JavaScript. Attendees can continue through the same forms without a document reload. No action is needed.
Validation
Rego typecheck and production build passed. The local registration route preloaded about 315 KB less raw JavaScript (37.8%), and Profile Setup about 47 KB less. Mobile and desktop browser fixtures passed, including anonymous and teaser access, the required registration reads, profile save, and one browser document. The linked Pages build succeeded. Hosted signed-in timing and real-account saves remain to verify.
Profile saves stay put and legal pages load less
Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.
What’s Changed
Saving Profile Setup during a direct edit keeps the form and its confirmation on screen. An explicit continuation after sign-in still takes the attendee to the requested page. Legal, Terms, and Privacy pages now load third-party license data only when the attendee opens Third-Party Notices. The API reuses event inclusion links already loaded for public event details, avoiding an extra lookup for linked tiers.
Impact
Attendees can review a saved profile without being moved to another page. Common legal pages request less JavaScript, and public event details require fewer API data reads. No action is needed.
Validation
Rego typecheck, synthetic build, route contract, and mobile and desktop browser fixtures passed. Common legal pages preloaded about 89 KB less raw JavaScript in the local build. Profile saves used one write and one browser document. API inclusion parity, fallback, and existing overview checks plus typecheck passed. Both linked builds succeeded; hosted legal and Profile Setup routes returned 200. Hosted signed-in timing and real-account saves remain to verify.
Older event registrations load when requested
Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.
What’s Changed
Transactions now requests the newest 40 event registrations first. Attendees can load older event registrations on the same page. Check-in badges, filters, and records already on screen remain available while an older page loads or retries. Other registration workflows keep their existing full-list API.
Impact
Attendees with many event registrations should reach their recent history sooner and can still browse older records. No action is needed.
Validation
API typecheck and a 1,205-record local ownership and paging fixture passed. Rego typecheck, synthetic build, route contract, and mobile and desktop browser fixtures passed, including older-page retry, filters, account isolation, and no document reload. Both linked builds succeeded; the hosted Transactions route and new JavaScript assets returned 200. Hosted signed-in timing and real-account saves remain to verify.
Saved dashboard changes appear sooner
Repository: Partners. Status: Linked release succeeded; signed-in save timing remains to verify.
What’s Changed
New Finance Integration profiles and Event Planning notification settings appear from confirmed save results without a full page or list refresh. If a save response is interrupted, the dashboard checks the saved state automatically and pauses repeat writes. Notification preferences now include the current version, preventing a conflict on a later save. An open dashboard can recover once when a new release replaces a page file; it pauses automatic recovery if an unsaved form is detected.
Impact
Finance and event planning operators should see confirmed changes sooner and keep their working context during checks. No action is needed.
Validation
Focused Finance, Planning, and updated-page recovery browser fixtures, typecheck, and production build passed. The linked Pages build succeeded; signed-in save timing remains to verify.
Large transaction histories open with less work
Repositories: Rego and Partners API. Status: Linked releases succeeded; hosted signed-in timing remains to verify.
What’s Changed
Transactions now shows the newest 40 matching records first. Show more reveals the next records on the same page without repeating the list request. Staffing and vollie pages can reuse a recent same-account roster read during navigation, while Refresh and saves still request current data. The API skips unused attendee profile checks for public events without an age restriction; age-restricted events retain their check.
Impact
Attendees with long histories should reach recent transactions sooner, and staffing navigation should avoid a repeat roster request. No action is needed.
Validation
Rego typecheck, synthetic build, route contract, and mobile and desktop fixtures passed, including a 600-record history and account isolation. The API overview and age-gate fixture and typecheck passed. Both linked builds succeeded, and the hosted Transactions route and its asset returned 200. Hosted signed-in timing and real-account saves remain to verify.