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 611-620 of 1462
2026-09-2315:53

Dealers Den inclusion designs retain their questions

Repositories: Rego, Partners API and Docs. Status: Local certification passed; hosted verification pending.

What’s Changed

Dealers Den attendees now receive the base inclusion’s questions separately for each fixed or randomly assigned design in their table package. The API recognizes when those designs replace the base item, so it no longer asks for a base-item answer that the form did not show.

Impact

Representatives and assistants can each answer the questions for their own included items during table registration. Organizers can continue configuring alternative or bundled designs in the tier editor.

Upgrade Notes

No operator action is needed. Targeted local API/browser checkout passed 207 checks at each mobile and desktop width, with temporary fixture records removed. The broader headless tab-close reservation-release check and hosted checkout remain unverified.

2026-09-2315:53

Waitlist offers keep their promised inclusion designs

Repositories: Rego, Partners API and Docs. Status: Local certification passed; hosted verification pending.

What’s Changed

Attendees can now join the waitlist for an active event. When a spot is offered, its included designs are saved with the offer. The offer, accepted checkout and resulting rego receipt show the same alternative or bundle components; a design hidden until collection remains unnamed. The base inclusion’s questions appear separately for each promised component. Disposable local test runs now clean up those saved promises after checkout.

Impact

Waitlisted attendees see the items they were offered, rather than a later catalog revision, when they accept and register.

Upgrade Notes

No operator action is needed. A 30-check desktop/mobile local API and browser journey passed; hosted acceptance and provider settlement have not been verified.

2026-09-2315:53

Gifted inclusion designs checked through redemption

Repositories: Rego, Partners API and Docs. Status: Local certification passed; hosted verification pending.

What’s Changed

A local desktop/mobile gift journey now verifies creation, redemption and saved receipts against the real local API and database. Alternatives omit the base item, bundles include it, and a design hidden until collection stays unnamed in gift and rego receipts. The base inclusion’s questions appear separately for every supplied design or random draw. Disposable test-run cleanup now removes saved gift promises in the correct order.

Impact

Gift recipients can review the promised components and answer each supplied item’s questions during redemption.

Upgrade Notes

No operator action is needed. Local checks passed; hosted gift purchase, redemption and provider settlement remain unverified.

2026-09-2315:53

Group registration saves inclusion designs together

Repositories: Partners, Partners API, Rego and Docs. Status: Database published and source branches pushed; hosted verification pending.

When an organizer submits a group registration, every accepted member’s registration and assigned inclusion design now save together. If a design runs out or the tier offering changes before submission, the whole group stays unsubmitted for review; no member is left with a partial registration or inventory allocation. The existing attendee review flow retains compatible item answers, including the base inclusion’s questions for each design or random draw. A separately accepted waitlist offer is not silently used by a group booking.

Who may notice: Group organizers and event operators reconciling design-level inventory. Next: Verify a hosted multi-member checkout and shortage recovery after Git-linked deployment. The database migration and follow-up dry-run passed; rollback, API typecheck and focused group tests passed locally. Hosted checkout has not been verified.

2026-09-2315:53

Random inclusion designs can stay hidden until collection

Repositories: Partners, Partners API, Rego and Docs. Status: Database published and source branches pushed; hosted verification pending.

Event organizers can now set a random inclusion group’s design reveal rule in the tier editor. Immediate reveal remains the default; an optional collection-time reveal keeps the assigned design out of attendee-facing gift, waitlist, registration and Dealers Den details until the item is claimed. The actual design and its SKU are still assigned and tracked by the event systems. Fixed variations continue to display normally. Each variation or random draw still asks the base inclusion’s questions separately, with saved gift and waitlist question wording preserved.

Who may notice: Event organizers configuring randomized items and attendees receiving designs such as tote bags.

Next: Verify a hosted registration and physical claim after Git-linked deployment. Database publication, local rollback, API typecheck and focused tests, Rego typecheck/browser fixtures and tier-editor mobile checks passed. The hosted claim-and-reveal journey has not been verified.

2026-09-2315:53

Rego shows tier inclusion variations

Repositories: Rego and Partners API. Status: Source branches pushed; hosted verification pending.

What’s Changed

Tier previews now show the actual inclusion offering: alternatives show the selected variations instead of the base item, while bundles show the base and their additions. Fixed designs can show their names, quantities and artwork; random designs remain an unassigned promise until the event assigns them. Gift, Dealers Den, group, upgrade and registration previews follow the same display rules. Gift redemption and accepted waitlist checkout show their saved item promises; rego and transfer detail show saved component names and quantities where recorded, even if the current catalog is later renamed. For standard, Dealers Den and group registration, each included design or random draw slot now asks the inclusion’s existing questions separately. Bundles also ask those questions for the base item; alternatives do not add a base-item answer set for an item that is not supplied. Group drafts keep each attendee’s answers separate, and upgrades ask questions for newly included components.

Impact

Attendees can compare what each tier includes without seeing inventory IDs or random-draw candidates. Event operators still create variations in the inclusion editor and set alternative/bundle and selection rules in the tier editor; Rego only displays those settings. If a fixed design reference is broken, the event offering now stops loading rather than showing a different or generic item as though it were promised. The same safety check rejects an empty or invalid random-design pool before advertising a draw promise; invalid item quantities also stop the preview rather than showing a different number of items from what inventory would allocate. Availability is still confirmed at registration submission. Current tier previews also follow active inclusion links, so an archived item is not shown as part of a new registration merely because an older tier record still references it. Checkout questions follow those same active links. A published database safeguard also prevents archived items’ design groups from being assigned to new registrations or offers. Saved historical promises and receipts remain separate.

Upgrade Notes

The API and Rego type checks and focused desktop/mobile browser fixtures passed locally, including two fixed designs in one inclusion, per-unit and per-draw questions, and upgrade question fixtures. The mobile event page also shows a retryable unavailable state when the API cannot provide a trustworthy offering, with no substitute item displayed. The new group-draft database column was applied before the API branch was pushed. Historical transfer items without a saved component snapshot are identified as current-catalog fallbacks rather than historical facts. Hosted registration, media and receipt checks remain necessary after release. The hosted public event and registration sign-in pages now pass a read-only desktop/mobile check, but none of the currently public events has an authored variation. This does not certify a hosted variation checkout or claim. A separate sealed local checkout now passes 88 API and desktop/mobile browser checks for two group attendees. Their saved receipts show an alternative’s fixed and assigned random designs without its excluded base item, alongside a bundle’s base item and added design. Local inventory rows retain each design’s own SKU and quantity; the fixture was cleaned up. Hosted purchase and physical claim remain unverified. An additional sealed individual checkout passes 35 local API/browser checks at desktop and mobile widths. Each supplied fixed unit and random draw asks the base inclusion’s required question separately; a bundle asks it for its base as well, while an alternative does not ask for the undelivered base item. Distinct answers and the saved receipt survive submission. This is local evidence, not a hosted checkout or claim certificate. The local individual receipt now also verifies a random design configured to be shown only at collection: its exact design stays hidden before claim, while fixed designs and bundle items remain visible. A separate local collection check showed the saved design appearing afterward. That local claim-and-receipt path now passes repeatedly with complete disposable-fixture cleanup, including desktop and mobile claimed receipts. Hosted checkout and claim are still unverified.

2026-09-2315:53

Inclusion designs commit with registration

Repositories: Partners database and Partners API. Status: Database published and API source pushed; hosted verification pending.

When an attendee submits a standard registration, the selected inclusion designs and their inventory identities now commit with the registration. If the tier offering changed or a required design is unavailable, submission stops without leaving a partial registration. Gift and accepted waitlist checkouts keep their previously promised designs; they do not draw again. The base inclusion’s questions still appear for every selected design or random draw slot, including alternatives where the base item is not supplied.

Who may notice: Attendees retrying a changed or sold-out tier, and event operators reconciling exact inclusion inventory. Next: Verify hosted individual, group, gift and waitlist checkouts. Local rollback-only database fixtures, API question-scope tests and type checks passed. Group members are still created sequentially with cleanup if a later member fails. Group checkout now checks the offering version for each member too; if it changed, attendees see the updated design and must explicitly review and resubmit. A mobile browser fixture passed this recovery path locally.

Dealer Den checkout now commits the table registration and all attendee slots with their included designs as one database operation. If a later slot cannot receive its required design, none of the slots is registered. Dealer Den also refreshes a changed tier offering, retains compatible answers, clears prior payment details, and waits for a new explicit submission. Local two-slot database checks and a mobile browser fixture passed; hosted behavior still needs verification.

2026-09-2315:53

Inclusion variation authoring simplified

Repositories: Partners and Partners API. Status: Source branches pushed; hosted verification pending.

What’s Changed

Event operators can add or edit inclusion variations in a focused form with a name, description, image, and active status. New variations receive a permanent inventory identifier automatically; existing identifiers remain unchanged. Variations use their parent inclusion’s item type and options, while retaining their own inventory and reporting identity.

Impact

Operators no longer need to invent a SKU for every design or version. Existing variation allocations and historical registration records keep their saved identities and details.

Upgrade Notes

The local variation-editor fixture, Partners type check, and API verification cover this change. A persisted catalog round-trip and managed-image upload on a non-production deployment remain required before hosted certification.

All docs