Trying to update patron CSS color fails at message editing, so don't try
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.3 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
For Evergreen 2.2+:
Trying to update patron CSS color fails here, so don't try
After modifying user standing penalties ("messages" in the staff client
patron interface), you could get this error message in an alert() dialog:
TypeError: patron.display is undefined.
We were apparently trying to use patron.
so the commented out changed verison of the call got farther, but stopped at
Which probably has something to do with unfleshed data. Somebody can
get to the bottom of this if they want, but for now it's easier just not
to try to do this and make the alert() dialog go away.
Changed in evergreen: | |
importance: | Undecided → Low |
importance: | Low → Medium |
Changed in evergreen: | |
milestone: | 2.2.1 → 2.2.2 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
That is indeed annoying. Agreed on avoiding the alert as a first step. Tested and pushed to master, rel_2_3, and rel_2_2.