Holds - patron account vanishes when another tab refreshed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Evergreen version 3.11.1
Since we upgraded to version 3.11.1 this past weekend, we have received reports from libraries about what happens now when they are placing holds for patrons with multiple tabs open.
According to them, in the past, as they are placing lots of holds for patrons (for example, for homebound services), they would typically keep two tabs open connected with the same patron account. One is for actively placing holds and the other is for keeping track of how many holds they have placed for the patron. However, after the upgrade they noticed that when they go to check how many holds they have placed for a particular patron, after they have refreshed the tab with the holds listed, the other tab loses the connection with the patron account and then acts just as a catalog search screen. They said they have tested this on another user's login and received the same results.
Another library described it thus:
1. One browser tab open to patron account --> Holds (to show all holds)
2. Open another browser tab to place hold while on patron account.
3. If you refresh the first tab with the patron’s account, then the second tab changes to regular staff catalog screen.
I have been able to reproduce this myself, and it has been suggested that it might be related to the patch that was implemented for the following bug:
https:/
Specifically, bullet point 4 in comment #5.
It was noted that he patron's Holds tab is in AngularJS, so when that is reloaded, the catalog loses the hold target.
Does this seem accurate? If so, and this issue was caused by the patch (whether intentionally or unintentionally), is there any possible way to resolve the issue without affecting the patch, since the patch was necessary for resolving another, separate issue? Or is this just how the staff catalog is expected to function now?
Thank you.
tags: | added: circ-holds |
Confirmed this occurs in 3.12 also.