Fixed: Accepting student applications no longer crashes when the parent already has an account.
If a parent submitted an application weeks ago and already had a user account in the system, accepting their application via the bulk dropdown would fail with an internal error. This happened because the system tried to create a parent profile in the wrong database location. Schools with a backlog of applications may have seen this error repeatedly.
This is now fixed. Accepting applications works correctly whether the parent is a brand-new user or already has an existing account. The parent's account type is updated to "Parent" and their profile is created in the correct location.
Fixes¶
- Bulk-accepting applications no longer crashes for parents with existing accounts
- Parent profile creation now happens in the correct database schema
- Added a safety guard that prevents profile creation in the wrong schema even if future code misses this pattern