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 651-660 of 1462
2026-09-1515:53

Separate remembered sign-ins for Partners and Admin

Repositories: partners.furries.ph, admin.furries.ph, and partners-api · Status: Local implementation; not deployed.

Partners and Admin now restore their own valid browser session before showing a sign-in form. Their remembered session metadata and API cookies are separate, so signing into one site no longer replaces the account used by the other. RegoSite’s existing separate session remains unchanged.

Impact: Operators who use different accounts for Partner work and Furries PH administration can keep both sessions open in the same browser. No data, roles, or access rules changed.

Validation: Focused session-isolation contracts, Admin tests, type checks, and production builds are being run locally. Deployment and live browser verification remain separate.

2026-09-1515:53

Clearer Partners dashboard reading and controls

Repository: partners.furries.ph · Status: Local implementation; not deployed.

What’s Changed

Local validation is complete: all 115 operational route entries have component or redirect evidence, with desktop/mobile workflow checks, 99 shared navigation/readability checks, a clean typecheck and production build. Tests use synthetic data; no production deployment is claimed.

  • Dashboard section navigation stays in the sidebar and mobile drawer across EMS, EPS and the other systems. Decorative colored side borders have been removed; readable labels, calmer cards, consistent controls and responsive dialogs now extend across the operational dashboard. Guide pages are unchanged.

  • EMS setup and Dealers Den, Finance reconciliation/settings, Reports, account settings, social publishing and Linked Operations have clearer long-content layouts and save recovery. Filters offer useful empty-state recovery, and long organization names stay within the sidebar footer. Local browser checks cover phone and desktop layouts; operators will see these changes after a future deployment.

  • EMS affiliate, coupon, settlement, social-verification and waitlist screens wrap long records more reliably. Waitlists offer a filter reset; settlement payment choices have calmer selected states. Dashboard checkboxes and radio controls stay visible beside long labels. Local responsive and workflow tests preserve saving and review behavior.

  • EMS shop, stock, pickup and point-of-sale screens wrap long items and provide clearer filters and save recovery. Assets overview, loaned registers, finance and settings now use calmer selected states, readable details and consistent retries. Local desktop/phone checks include every Assets settings section and preserve existing workflows.

  • EMS check-in, inclusion claims, offline snapshot tools and registration records have clearer labels and narrow-screen layouts. Long records and recovery dialogs wrap correctly, and missing-event navigation uses a single accessible link. Existing offline and attendance behavior passed local regression checks.

  • Finance overview event rows now open the chosen event in the detailed portfolio. Event selection is clearer and uses a neutral border; phone and desktop navigation and load recovery were checked locally.

  • EMS communications explains email and SMS options in attendee-focused language. Recipient filters have visible labels and reset actions, with calmer cards and better long-name wrapping. Local checks preserve campaign behavior and failed-action drafts.

  • EMS accounting and analytics use calmer borders, clearer labels and responsive forecast charts. Activity, department, roster and volunteer screens wrap long content and provide clearer filter and retry actions; narrow activity and position editors no longer clip controls. Local browser checks cover populated, empty and failed-load states at phone and desktop widths.

  • EPS workspace empty filters offer a direct return to open plans, and current plans use a neutral selected surface. Table preview actions open fictional record details and keep selection counts readable. These changes are verified locally on phone and desktop layouts.

  • Notifications is easier to find from the sidebar and dashboard. Alert summaries count configured destinations more accurately and keep partner results separate during switching. Pawsport registry and issuance screens, EPS risks, approvals and files have clearer mobile layouts and recovery feedback.

  • EMS event lists group search and display controls, make dates and registration counts easier to scan, and offer a clear-filters action when a search has no matches.

  • EMS event creation has clearer field hints, linked validation messages, keyboard focus on the first invalid entry and confirmation after creation. Long partner names wrap on phones; failed creation keeps entered values for retry.

  • EMS refund, transfer and submission queues have labelled filters and clearer mobile records. EPS department and event-configuration actions wrap on phones; Settings keeps edits visible during failed saves and explains audit-download failures.

  • EPS plan selection uses clearer selected states and more readable actions. Workspace sections stay in the EMS-style sidebar and mobile side drawer.

  • Dashboard sections, selected sidebar items, embedded editors and quoted content use soft surfaces without decorative blue side borders.

  • Surveys, Linked Operations, Logistics Hub workflows, Asset master-data settings and EMS forecast section menus now use the sidebar and mobile side drawer. Pawsports uses its existing sidebar without a duplicate page menu.

  • Operational workspaces share larger supporting text, calmer surfaces, consistent form and table spacing, and visible keyboard focus. Guide pages retain their existing presentation.

  • EMS detail fields adapt to the space available; EPS plan summaries wrap long names. Assets saved-view fields remain usable on phones, and Finance event rows keep their totals readable on narrow screens.

  • EPS calendar arrows now advance one month at a time. Busy days open all scheduled work; phones start with a readable agenda ordered by time. Calendar and board panels use consistent soft backgrounds.

  • Reports overview gives report names and summaries more space, wraps metadata clearly, and explains empty lists and failed refreshes. Survey sidebar switching and draft preservation are verified on desktop and phones using synthetic records.

  • Mobile navigation keeps keyboard focus inside the drawer, closes with Escape or after choosing a destination, and returns focus to the menu button. Embedded form editors now use readable controls and neutral section borders.

  • Dashboard and Settings cards describe their destinations more clearly. EPS Requirements and Meetings wrap better on small screens; failed RSVP saves keep the draft and show the error inside the dialog.

  • Finance payables, receivables, expenses, budgets and close workspaces use clearer filters and totals, readable queue cards, and a mobile path between records and their details. Dismissing action or creation dialogs returns keyboard focus to the control that opened them.

  • Finance Transactions and Outflows now show separate currency totals and clearer mobile record details. Manual-entry option loading, rejected entries, evidence downloads and bulk review failures offer visible recovery without losing entered details.

  • Approved submissions, gifts and upgrade queues have clearer search recovery and mobile details. Report directories and reminders wrap full subjects, with clearer filter reset and keyboard actions.

  • My Work shows every returned assignment instead of stopping after 12, with clearer filter reset and save errors. EPS notification preferences offer Retry after failed loading. EMS payment, notification and Google Wallet settings use clearer labels and responsive controls; validation appears inside payment editors.

Impact

Partner teams can scan event records and read operational forms more comfortably across desktop and narrow screens. Existing data, permissions, and Admin destinations are unchanged.

Upgrade Notes

No migration or operator configuration is needed. The updated production build passed. The expanded readability suite passes 99 checks, with focused EMS, EPS, Assets, Finance, Reports, Surveys, Dashboard and Settings checks. Full typecheck now passes. TASK341 tracks the remaining route review and build evidence. Screenshots use synthetic records; production workflows and deployment are not certified by this visual pass.

2026-09-1415:53

Synchronized EPS boards

Repositories: partners.furries.ph, partners-api · Status: Deployed.

What’s Changed

  • My Work and Requirements now use the same delivery summary and column rules.
  • Planning saves refresh both open views across tabs. Returning to a board refreshes it, and visible boards check for teammates’ changes every 15 seconds.
  • Requirement progress includes authorized linked work assigned to other contributors; one person’s completion cannot prematurely finish the requirement.

Impact

Department leads, administrators, and members see consistent progress within their existing access scope. Requirement approval remains a separate step.

Upgrade Notes

No schema migration is needed. The API and dashboard release together; two-tab browser fixtures verify updates in both directions.

2026-09-1415:53

EPS My Work and Requirements boards

Repository: partners.furries.ph · Status: Deployed.

What’s Changed

  • My Work and Requirements now offer Not started, In progress, and Done boards with a List view toggle.
  • Assigned members can update their delivery work in My Work. Department leads and administrators can update linked delivery tasks in Requirements.
  • Existing assignment boundaries, version checks, and requirement submission/approval steps remain enforced.

Impact

Teams can track progress directly from cards. A requirement with completed delivery still needs its normal submission and approval.

Upgrade Notes

No schema changes. Browser fixtures cover status updates, permissions, conflicts, and mobile layout.

2026-09-1415:53

Expanded problem-report diagnostics across websites

Repositories: Partners API and website reporter adapters. Status: API and all ten website adapter deployments verified live.

What’s Changed

  • Reports capture console objects, traces, groups and timers; successful and failed fetch/XHR requests; readable header names; redacted JSON previews; resource timing and policy violations.
  • Added reporter loaders for Support, Docs, Moderation, Signals, Join, Admin and Status. Partners and Social load the reporter independently of application startup.
  • Snapshots retain up to 200 events / 40,000 characters, show omitted-event counts, and remain editable before public-sharing consent.

Impact

Support teams receive more useful request and response context. Sensitive values are filtered; browser-internal Firefox logs, hidden headers and historical messages remain unavailable. Public reporting remains an explicit user action.

Upgrade Notes

Reload the page to use the expanded reporter. Cloudflare deployments succeeded for the API and all ten changed website builds; the live pages contain their correct reporter loaders. Identity and submission preflight checks pass for all twelve site labels. Live browser previews on the main site, Support and Docs show the expanded diagnostics, and Turnstile hostname coverage is verified. Signals required correcting its hosted build output directory to build/client. Local parser, intake and browser regressions passed. No public test issue was submitted, and authenticated CMS reporting was not exercised.

2026-09-1415:53

Password recovery email validation repair

Repositories: partners-api, partners.furries.ph, and partners.furries.ph-v2 — API fix deployed and live recovery verified.

What’s changed: Recovery emails now preserve their purpose through API verification, allowing valid email OTP sessions to reach password replacement while ordinary sign-in sessions remain rejected. Password replacement no longer depends on a missing client-library session. Partners V2 reset requests target Partners, and recovery validation remains accessible without platform MFA. Agent instructions now allow commands needed for authorized diagnostics, fixes, and validation without repeated permission requests.

Impact: Addresses valid reset links being rejected as invalid and the subsequent password-saving failure. Existing frontend recovery forms are reused.

Upgrade notes: Request a fresh reset email; old links cannot supply the new recovery proof. Credential, signed email-hook, and route integration tests, full API typecheck, and Worker dry build pass. The fix was released through the Git-connected Cloudflare build from API commit 4c249036.

Live validation: A disposable account’s real recovery token opened the production Partners password form, saved a replacement password, and signed in successfully with that password. Reusing the link was rejected, and the fixture was removed. This used a generated test link without sending an email; inbox delivery itself was not retested.

2026-09-1415:53

Waitlist turn email reminders

Repositories: partners-api and partners.furries.ph — scheduled delivery is active in production.

What’s changed: When a waitlisted attendee receives a registration turn, the platform sends an email with the event and tier. It follows up 3 hours and 1 hour before the offer ends, then confirms when an unclaimed turn has been released to the next attendee.

Impact: The Worker now expires and promotes waitlist offers on its minute schedule. Messages are stored in a durable queue, checked against the current offer state and Rego-email preference before sending, deduplicated, and retried after temporary delivery failures.

Upgrade notes: No organizer action is required beyond existing waitlist and offer-window configuration.

2026-09-1415:53

Event Rego and prefill availability email reminders

Repositories: partners-api and partners.furries.ph — scheduled delivery is active in production.

What’s changed: Platform accounts with Rego email updates enabled now receive an event-specific email when an event’s scheduled Rego or registration-prefill window opens, plus reminders 3 days, 24 hours, and 3 hours before its effective closing time. Each message links to the event’s public Rego page and shows the event-local closing time.

Impact: Unsent reminders are rechecked against the current event schedule and each recipient’s communication preference before delivery. This prevents stale schedule notices and respects opt-outs. Event-level windows are covered; a tier-specific schedule does not trigger a platform-wide email.

Upgrade notes: Organizers only need to set the existing Rego or prefill opening and closing times. Delivery runs through the platform’s scheduled email queue, prevents duplicates, and retries temporary delivery failures.

2026-09-1415:53

Account confirmation email hook response corrected

Repository: partners-api — deployed to production as ec2f968.

What’s changed: Successful authentication-email queueing now returns an empty JSON object with HTTP 200 and the JSON Content-Type header Supabase requires.

Impact: Corrects the API-side cause of the reported signup Content-Type error. The RegoSite request-header change described below alone does not resolve this hook-response failure. Password sign-in does not use this confirmation-email hook.

Upgrade notes: Retry account creation. Cloudflare’s production build passed for ec2f968 (Worker version 643dcdcc-ea90-40b4-9239-5d5b2d7f4338). Signed-hook response and invalid-signature checks pass, as does the Worker dry build. The full type check reports eight existing diagnostics in authEmailOutbox, profilePhotoMigration, and planning. Production rejects incomplete signup input and unsigned hooks as expected. End-to-end account creation and mailbox delivery remain to be checked.

2026-09-1415:53

RegoSite account creation request recovery

Repository: rego.furries.ph — attendee account creation updated.

What’s changed: RegoSite now explicitly labels every authentication request as JSON, including new-account creation. This prevents an absent request media type from stopping account creation.

Impact: New attendees can create accounts without the missing Content-Type error. No profile, registration, or existing-account data changed.

Upgrade notes: No action is required after the updated site is published.

All docs