Topic: kicking off operators that don't logoff.

[cdev]

how do you kick off an operator that has forgotten to logoff? Any changes I make to the istatus or dtmlastvisited in the chatoperator table get overwritten.  I've even tried remotely deleting the user's cookie and  doesnt help unless I restart apache. I can't going to that user's computer if they have it locked and I don't want to remote in to the client's system and close any open documents. Other than restarting apache, what can I do?

[cdev]

I hate to bump my old topic, but I still need help with this.

[faf]

First of all, why do you need that? More precisely, do you need your operators to become offline or to really log them out of system?

[MichaelTunnell]

I think is more an issue of annoyance because I have experienced this with operators leaving their account logged in over the weekend. I have also seen them leave chat threads open over the weekend. There should just be some timeouts set for both so if people navigate to the page they aren't granted access so easily.

[faf]

What exactly do you propose and how's that supposed to work?

[cdev]

When operators forget to log off, the chat button still shows as online or that there was an open operator in the queue when they were away.


I found a partial solution where I can set opening hours, thank to bheirman
https://mibew.org/forums/index.php?topic=471.0

This works great if operators forget to logoff during offline hours, but not if they take breaks or leave early during opening hours.
I wish there was a way I could code users to do things correctly, lol.