-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
LIvechat user activation #1963
Comments
Yes, that makes sense, and is definitely not the expected behavior. We'll work on fixing that! Thanks for reporting it. |
If you have activated manual activation you get following error: To work around this issue just disable the manual user activation (Settings -> Accounts -> Registration) Running current Dev |
I ran into this problem. I turned off "manually approve users" but I still get "Token already exists" after restarting the server even. Not sure how to get rid of the token. |
Same issue for me. How to workaround that? |
Same here, |
yup - just hit this as well. I was hoping that livechat would enable me to allow visitors to the website to open a "support" chat - there are 2 things stopping me from doing that #1 having to have a user defined (what if I get 10000 support calls ? ;) ) |
Is it planned to be fixed ? |
I get this error only if I close a chat and then try to reopen another with a different email address using the same browser. |
A simple patch:
|
I'm running the current develop (0.14.0) with livechat turned on. It took me a while to figure this out and I'm not sure it is the expected behavior - when I have user registration turned on, with "manually aprove new users" turned on - my livechat guests receive "User not active" message when they try to write something in chat.
Everything works fine, when I change the registration options to "manually aprove users" turned off.
I understand this is because the livechat users are "standard" rocket.chat users, but I think this is wrong in the first place and should be stated in large typeface in the docs, because it's not obvious.
The text was updated successfully, but these errors were encountered: