Skip to content
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

Error 404 when accepting new Live Chat request #11347

Closed
danshipt opened this issue Jul 4, 2018 · 1 comment · Fixed by #10731
Closed

Error 404 when accepting new Live Chat request #11347

danshipt opened this issue Jul 4, 2018 · 1 comment · Fixed by #10731

Comments

@danshipt
Copy link

danshipt commented Jul 4, 2018

Description:

Updated from 0.64.2 to 0.66.0 then to 0.66.1. Same problem.
When accepting new LiveChat, error appears both in MacOSX app and in browser.

Error:404
Oops, page not found
Sorry, page you requested does not exists or was deleted!

Steps to reproduce:

  1. Start new live chat on the site and write first message
  2. Operator clicks on new live chat from Incoming Livechats section.
  3. Message appeared with user message and Take It! button.
  4. Click button to accept new live chat. Error 404 appears instead of chat room.

Expected behavior:

No 404 error. Chat room with user activated.

Actual behavior:

Error:404
Oops, page not found
Sorry, page you requested does not exists or was deleted!

screenshot 2018-07-04 23 52 33

screenshot 2018-07-04 23 52 41

screenshot 2018-07-04 23 52 56

Server Setup Information:

  • Version of Rocket.Chat Server: 0.66.1
  • Operating System: CentOS 7 x64
  • Deployment Method: manual
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 8.9.3 - x64
  • MongoDB Version: v2.6.12

Relevant logs:

[Error] TypeError: undefined is not an object (evaluating 'chatMessages[this._id].input=e.find(".js-input-message")')
focus .js-input-message (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:251:66483)
(anonymous function) (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:87:38104)
_withTemplateInstanceFunc (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:87:37673)
(anonymous function) (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:87:38076)
(anonymous function) (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:87:27002)
_withCurrentView (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:87:23080)
(anonymous function) (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:87:26974)
(anonymous function) (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:87:9124)
dispatch (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:9:1392774)
trigger (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:9:1420538)
simulate (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:9:1421043)
n (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:9:1421333)
(anonymous function) (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:183:50411)
_compute (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:43:2360)
_recompute (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:43:2613)
_runFlush (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:43:3809)
a (1297c7571bedbb6cd4df2a377c401e0f105698e4.js:1:2695)

There are nothing in server logs.

@renatobecker-zz
Copy link

renatobecker-zz commented Jul 9, 2018

Hi @servancho!
Thank you for reporting this bug. I want to say that we've already fixed this issue and will be released on our next release.
Please follow the review process for this PR: #11406.
Thank's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants