-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Converse UI should present 'offline settings' when queue is closed #49
Comments
Confusingly, when the queue is closed, end-users clicking on the chat button appear to join a chatroom immediately. As I assume their messages will be lost, that's undesirable. |
Falling back to a chatroom was added as a feature, not a bug, in https://github.com/guusdk/openfire-fastpath-plugin/blob/64d9a35e693ec7429d958dc1cc6d7e03738566ae/classes/ofmeet.js#L114 We've discussed this desired functionality in #48 and agreed to replace this with a new 'offline setting' instruction "offer to join chatroom" (#51) |
This introduces a new configurable 'offline setting': redirect to a chat room, adding this option to the database and the admin console. The embedded converse client is modified to no longer hardcoded falling back to a chatroom, but to do this only when the offline settings instruct it to do so. This routine needs a lot more work (see igniterealtime#49).
This introduces a new configurable 'offline setting': redirect to a chat room, adding this option to the database and the admin console. The embedded converse client is modified to no longer hardcoded falling back to a chatroom, but to do this only when the offline settings instruct it to do so. This routine needs a lot more work (see #49).
When a workgroup queue is not open (eg: no logged in agents), then the Converse UI should not show a functional chat button (the button that's used to start a new chat).
That button should either be removed, or be disabled somehow.
Note that ideally, the state of the button is dynamically adjusted, to ensure that, when the queue state changes, the button on the page (that has already been loaded) also does.
The text was updated successfully, but these errors were encountered: