Save & Clone Action Results in Pending Address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Evergreen 3.0.13
Evergreen 3.2.4
We have the following library settings set, (though I don't know how much of an impact they have on this bug):
Allow Pending Addresses: UNSET
Patron Registration: Cloned patrons get address copy: TRUE
When a patron account is saved and cloned in the web client, the resulting patron record ends up with a pending address. This does not happen in the XUL client and it didn't happen in our installation of an earlier release of 3.0.
This seems to have begun in 3.0.12 as we had no pending addresses in our database prior to our 3.0.12 upgrade. (I'm wondering if it's related to this fix: LP #1724083).
If staff try to approve the address before the account is fully created, (i.e while still on the registration screen), staff receive the following pop-up error message: Event: 1528:ACTOR_
Save & Cloning a patron should not result in a pending address.
tags: | added: webstaffclient |
Changed in evergreen: | |
status: | New → Confirmed |
tags: | removed: webstaffclient |
Changed in evergreen: | |
assignee: | nobody → Bill Erickson (berick) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
We're seeing this in 3.1.7