Closed pvdv closed 12 years ago
Tested with https://testchat1.e-hulp.nl/ When I force a collision, the chat of the client doesn't come up, it does show the questions, but stays on the pale yellow screen without any of the text fields/controls. Seems there is a js bug in the fix.
is xmpptk at the latest revision?
Am 24.10.2011 um 21:48 schrieb Winfried Tilanus:
Tested with https://testchat1.e-hulp.nl/ When I force a collision, the chat of the client doesn't come up, it does show the questions, but stays on the pale yellow screen without any of the text fields/controls. Seems there is a js bug in the fix.
Reply to this email directly or view it on GitHub: https://github.com/e-hulp/HelpIM/issues/80#issuecomment-2508418
or is there any js error you could show me?
Am 24.10.2011 um 21:48 schrieb Winfried Tilanus:
Tested with https://testchat1.e-hulp.nl/ When I force a collision, the chat of the client doesn't come up, it does show the questions, but stays on the pale yellow screen without any of the text fields/controls. Seems there is a js bug in the fix.
Reply to this email directly or view it on GitHub: https://github.com/e-hulp/HelpIM/issues/80#issuecomment-2508418
Op 24-10-11 21:56, Stefan Strigler schreef:
is xmpptk at the latest revision?
Yes, upgrades on 19:01, 20:21, 21:42.
Paul
On 10/24/2011 09:57 PM, Stefan Strigler wrote:
or is there any js error you could show me?
Nope, the client gets the invite to the room, it sends the presence to the MUC, but from there it seems to stay silent. I don't really get what goes wrong from there...
k, I'll look into it tomorrow
Am 24.10.2011 um 22:14 schrieb Winfried Tilanus:
On 10/24/2011 09:57 PM, Stefan Strigler wrote:
or is there any js error you could show me?
Nope, the client gets the invite to the room, it sends the presence to the MUC, but from there it seems to stay silent. I don't really get what goes wrong from there...
Reply to this email directly or view it on GitHub: https://github.com/e-hulp/HelpIM/issues/80#issuecomment-2508764
turned out those issue are due to a bug in tigase
Fix confirmed with prosody, but deploying prosody still has some issues.
prosody is deployed, fix is implemented.
When client and staff have the same nickname, there will be no conversation. I think the client should be renamed, e.g. in "name_", or "name ", or something like that.