Jump to content


Error when linking ticket with chat - Livezilla 7.0.3.1

7.0.3.1 bug

2 replies to this topic

#1 lzst3rer

    Advanced Member

  • Members
  • PipPipPip
  • 71 posts

Posted 30 April 2017 - 07:39 PM

When I link a ticket to a chat, I get the error below. If it helps, I created the ticket from that same chat (testing out the app) and I don't know why it didn't auto-link.

Error shown in "Client" tab on Livezilla:

TypeError: winObj is null | https://xxxx.com/mobile/js/lzm/classes/ChatTicketClass.js?acid=1493580509 | 2905

Hope this helps Livezilla team iron out these bugs. There are a lot of bugs (or my setup is incorrect, which I've tested with multiple versions of PHP, etc.)

EDIT: Also, I just checked and I cannot see the ticket listed under that same chat. Even after the chat is closed, the tickets won't show as linked. I also tried to create a ticket from that closed chat and it went through fine but no link between the two. Hope this gets fixed because it's crucial for us that links between chats and tickets are visible.

I'm using Ubuntu 16.04 with:
* PHP 5.6.3
* Nginx 1.10
* MariaDB 10.1

Attached Thumbnails

  • Attached Image: screenshot-2017-04-30-15-38-06.png


#2 Patrick Keil

    Administrator

  • Administrators
  • 3190 posts
  • LocationSingen, Germany

Posted 02 May 2017 - 01:12 PM

Hi,

I tried to reproduce this in 7.0.3.1 with no luck. This is what I tried:

1.) Open ticket
2.) Hit "Actions" -> "Link this ticket with chat"
3.) Enter chat id
4.) Hit "Ok"

No error. Same from chat archive:

1.) Right click archived chat
2.) Link with ticket
3.) Enter ticket id
4.) Hit "Ok"

No error.

Quote

Even after the chat is closed, the tickets won't show as linked.
Yes, same for feedbacks. We have that on our list already.

Cheers

#3 lzst3rer

    Advanced Member

  • Members
  • PipPipPip
  • 71 posts

Posted 04 May 2017 - 02:19 PM

Thanks for the response, Patrick. Good to know that you've identified and fixed the ticket-chat-feedback reference issue.

I may have fixed the Client error somehow or maybe it was related to something else. I will track it down again and localize it.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users