Fix waiver duplicate key error + wrong fee calculation + member search name mismatch
TKT-71: Fixed duplicate entry for membership_number by reversing operation
order in WaiverProcessor — source member's number is now NULLed BEFORE
assigning it to target member, preventing unique constraint violation.
TKT-71: Waiver fee now calculated from current pricing_configs value instead
of the member's stored membership_value (old/historical price).
TKT-69: Member search duplicate check now shows the entity type (spouse/child)
and the parent member's number, clarifying which person is being shown.
Co-Authored-By:
Claude Opus 4.6 <noreply@anthropic.com>
Showing
Please register or sign in to comment