TPAC: Request for non-existent record results in server error
Bug #976864 reported by
Dan Scott
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
* Evergreen master
If a request is made for a record that does not exist, the TPAC displays a raw server error and the Apache error log contains:
"""
egweb: Context Loader error: Empty String at /usr/local/
"""
The simplest way of side-stepping this is to return early if we detect the lack of existence of the desired record.
user/dbs/
Revision history for this message
| Thomas Berezansky (tsbere) wrote | #1 |
| Changed in evergreen: | |
| status: | New → Fix Committed |
| Changed in evergreen: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
As mentioned in IRC, could use some extra work (like a "this record doesn't exist" warning), but this works for now. Pushed to master and rel_2_2.