Agent is not removed from Queue upon logout
-
-
-
-
-
-
-
Yes, that is the problem. There is no way to make both work. What happens is this: the plugin checks for logout events, but if it sees the user still being logged/connected, it won't execute the logout actions. The plugin will log you in and keep you connected, no matter if you logout from the main fop2 display. And so the logout actions won't kick in.
The problem here is that I had to make the logout actions only work when no sessions were active because different browser versions could have erratic management of websocket sessions, where you could have two sessions open at the same time (but only one actual session working), and one of them is then killed by the browser after some time. If the server detects that ang logs you off, while you still have a valid connected session, the result is unexpected and wrong.
When using the Chrome extension, you do have two valid connections using the same extension, and hence you are never logged out (unless you close/deactivate the chrome extension).
There is no easy way to make them work together. A plugin upgrade is not enough. But I will see if I can work on something for a next release, trying to identify chrome extension clients from regular browser clients and work from there.
-
Yes, that is the problem. There is no way to make both work. What happens is this: the plugin checks for logout events, but if it sees the user still being logged/connected, it won't execute the logout actions. The plugin will log you in and keep you connected, no matter if you logout from the main fop2 display. And so the logout actions won't kick in.
The problem here is that I had to make the logout actions only work when no sessions were active because different browser versions could have erratic management of websocket sessions, where you could have two sessions open at the same time (but only one actual session working), and one of them is then killed by the browser after some time. If the server detects that ang logs you off, while you still have a valid connected session, the result is unexpected and wrong.
When using the Chrome extension, you do have two valid connections using the same extension, and hence you are never logged out (unless you close/deactivate the chrome extension).
There is no easy way to make them work together. A plugin upgrade is not enough. But I will see if I can work on something for a next release, trying to identify chrome extension clients from regular browser clients and work from there.
-
-
Hello, i am just opening up this discussion to possibly see if you were able to get the agent logout to work the chrome extension being enabled.
I suppose the solution would be to allow agents to just status themselves as DND but there are some old dogs here...
please let us know if there was ever a fix for this.
thanks!! -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login