AngJS Always Tries To Use Hatch For Printing
Bug #1858118 reported by
Bill Erickson
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Evergreen 3.4+
Part of the code for bug #1830391 moved the "use hatch for printing" check away from local storage and into a workstation setting. Several spots in the AngJS code were not properly updated to reflect the now-asynchronous nature of the test, resulting in all print attempts trying to use Hatch.
Patch forthcoming.
Changed in evergreen: | |
assignee: | nobody → Galen Charlton (gmc) |
status: | New → Confirmed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixes pushed:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1858118- angjs-print- sans-hatch
From commit:
Teach code asking Hatch whether printing is enabled to properly handle the asynchronous response of the setting which now exists as a workstation setting instead of a localStorage setting.
Related, if Hatch is unavailable, use browser printing regardless of the hatch printing workstation setting.
Additionally update the "reprint last" handling to store the last_printed value in localStorage instead of attempting to save its value as a workstation setting.