Null circ_modifier causes "Network or server failure" error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Low
|
Jason Etheridge |
Bug Description
Reported in Evergreen 1.6.0.7:
Attempting to save a copy with a null circ_modifier results in a message like the following:
Network or server failure. Please check your Internet connection to [app server] and choose Retry Network. If you need to enter Offline Mode, choose Ignore Errors in this and subsequent dialogs. If you believe this error is due to a bug in Evergreen and not network problems, please contact your help desk or friendly Evergreen administrators, and give them this information:
method=
params=
THROWN:
{"payload"
Postgres logs show the underlying problem:
2010-08-23 10:08:06 [db server] postgres[2182]: [172-1] 2010-08-23 10:08:06 EDT ERROR: insert or update on table "copy" violates foreign key constraint "circ_mod_fkey"
2010-08-23 10:08:06 [db server] postgres[2182]: [172-2] 2010-08-23 10:08:06 EDT DETAIL: Key (circ_modifier)
2010-08-23 10:08:06 [db server] postgres[2182]: [172-3] 2010-08-23 10:08:06 EDT STATEMENT: COMMIT;
Desired behavior: It should be possible to have a null circ_modifier. If it weren't possible to have a null circ_modifier, I would want the staff client to say "circ_modifier cannot be null. Please assign a circ_modifier before saving this copy." rather than throwing a "Network or server failure" error that doesn't even hint at the problem.
description: | updated |
Changed in evergreen: | |
milestone: | none → 1.6.1.5 |
Changed in evergreen: | |
assignee: | nobody → Jason Etheridge (phasefx) |
Changed in evergreen: | |
status: | Confirmed → Fix Committed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Steps to reproduce:
1. Open the drop down box for Circulation Modifier
2. Do not select one of the options and leave it as 'undefined'
3. Click Apply
4. Click Create Copies