Invalid lib.timezone breaks record summary
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.0 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Evergreen 3.0
If you have an invalid timezone value for the lib.timezone org setting, attempting to view a record in the OPAC results in an internal server error.
Steps to reproduce:
1. In Library Settings Editor, edit the "Library time zone" setting for Example Branch 1, setting the value to something that's not the name of a time zone (like "invalid" or "UTC-07:00").
2. In the OPAC, retrieve a record with holdings at Example Branch 1. You will get an Internal Server Error.
3. Edit the library setting to use a valid timezone name, like "America/
4. Retrieve the same record again. This time, the record will display properly.
It appears that only valid tzdata timezone names are acceptable values for lib.timezone, so "America/Vancouver" will work but "Pacific Time Zone" or "PST" will cause the 500 error in the OPAC.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
no longer affects: | evergreen/3.1 |
Changed in evergreen: | |
milestone: | none → 3.1-rc |
Changed in evergreen: | |
milestone: | 3.1-rc → 3.1.1 |
Changed in evergreen: | |
milestone: | 3.1.1 → 3.1.2 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Working branch user/jeffdavis/ lp1752753- invalid- timezone has a minimal fix, using try/catch to avoid an internal server error on invalid timezone values. Better documentation (including an updated description for the setting) would also help.