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.
Unfortunately the queue login plugin won't work if you use the chrome extension (as the chrome extension will keep the agent logged all the time, there would not be a logout event if you use it). I did not find a way around that yet.
Comments
[attachment:56775306c2f11]
Any way to make both work?
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.
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.
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!!
Best regards,