-
-
Notifications
You must be signed in to change notification settings - Fork 430
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
Messages Not Working #36
Comments
When you attempted to try with MongoDB version 3.4 was it with a fresh database or the one created from 2.6? Trudesk Demo Site is running version 0.1.10 with MongoDB 3.4 from mLab.
My best guess right now is that the MongoDB database was created with an older version of MongoDB mongoose v4 is incompatible with. If thats the case you can upgrade MongoDB and clear the |
OK, I will try with mLab and see if it works. Can you confirm what version of Node you are using? I wonder if that is my issue as well. edit: I tried again, this time using mLab and messaging still does not work. messages/conversation/start seems to initiate fine, work but not when clicking on the user, messages/conversation/user comes back with a 400 error message start - http post conversation/start
message start - response
message conversation - http post conversation/5a051b4c57fe4334eb21dd2d
message conversation - response
node console
chrome console
|
update: I tried using different versions of node with fresh installs and still receive the error |
Thank you for all the information, it was very helpful. I have been able to reproduce the error and working on a fix. Stay tuned 👍 |
Fix is on master. |
Hey, thanks for the help! I just reloaded and its working! |
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
Starting a message does not open any type of window
What did you expect to happen:
Message popup
How to reproduce it (as minimally and precisely as possible):
I am using Chrome v61, click on any user in the online panel. Also clicking messages on the left hand side-panel does not seem to be showing anything besides the attempted conversations
server-side logs
chrome logs
Anything else we need to know?:
Environment:
no
The text was updated successfully, but these errors were encountered: