OPAC timeout within the client
Bug #1036318 reported by
Tim Spindler
This bug affects 14 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.3 |
Fix Released
|
Medium
|
Unassigned | ||
2.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
version 2.2.0
We have the following library settings
GUI: Idle timeout 22000
Security: OPAC Inactivity Timeout 22000
Security: Staff Inactivity Timeout 3600
Self Check: Patron Logon Timeout: 300
We find that when the client is running. The login on the TPAC while in the client times out and staff are unable to get to actions for this record and other functions. This time out seems to be inconsistent with the above settings because it has logged out in 10 minutes, 20 minutes and other times.
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
summary: |
- OPAC timeout withn the client + OPAC timeout within the client |
Changed in evergreen: | |
milestone: | 2.4.0-rc → none |
no longer affects: | evergreen/2.2 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We have had reports of this from our staff, complete with screen shots. However, I have been unable to reproduce the reported behavior.
Basically, what we've had reported is that staff are sometimes prompted with a tpac login screen when trying to place a hold in the staff client.
Yesterday, I tried reproducing this in production and in development and was unsuccessful. I would leave my staff client sessions logged in and retry the tpac functions at increasing intervals of 10, 15, 20, and 30 minutes. Not once was I prompted to login. On development, I even left the client with the tpac screen up and did nothing else.
There have been some issues with different time outs in the past when staff use operator change in the client. Are your staff using this, by chance? (I thought that this operator change timeout might have been fixed, but I am not 100% sure.)
Jason