Jump to content


Clients not receiving messages from operators


31 replies to this topic

#21 grevalve

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 09 June 2017 - 08:56 PM

Hello, we tried from mobile and different PC browsers and there are no stuck messages anymore. There is still a slight delay but that has been noted as normal

EDIT: Forgot to mention that we tested this without enabling Visitor Monitoring (we don't use it anyway)

#22 lhcampos

    Advanced Member

  • Members
  • PipPipPip
  • 61 posts

Posted 16 June 2017 - 07:08 PM

Since we uploaded the file to the server we are not facing this problem anymore.

I will wait some more days to confirm 100%, but seems like it is fine now. I did not active the visitor monitoring.

Thanks

#23 taidaniel

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 18 June 2017 - 01:24 AM

Hi Patrick,

Have applied the fix for a few days. Working well now. Thanks

#24 Patrick Keil

    Administrator

  • Administrators
  • 3132 posts
  • LocationSingen, Germany

Posted 19 June 2017 - 05:43 AM

Glad to hear that!

#25 grevalve

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 21 June 2017 - 01:23 PM

View PostPatrick Keil, on 19 June 2017 - 05:43 AM, said:

Glad to hear that!

Hi Patrick, is this fix going to be included in an official update for LZ? I would hate to have the file rewritten by the next update if it's not included. I know we can manually track this but the right way is to have the fix in the update.

#26 Patrick Keil

    Administrator

  • Administrators
  • 3132 posts
  • LocationSingen, Germany

Posted 21 June 2017 - 01:58 PM

Hi,

The official fix will be included in 7.0.5.0 but we also updated the 7.0.4.1 build on 2017-06-16.

You can install this setup or wait for 7.0.5.0 coming next month.

#27 grevalve

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 21 June 2017 - 02:04 PM

Excellent, thank you!

We will proceed with the 7.0.4.1 on our live server this week then.

#28 Kevman1982

    Member

  • Members
  • PipPip
  • 27 posts

Posted 26 June 2017 - 09:18 AM

View PostPatrick Keil, on 21 June 2017 - 01:58 PM, said:

Hi,

The official fix will be included in 7.0.5.0 but we also updated the 7.0.4.1 build on 2017-06-16.

You can install this setup or wait for 7.0.5.0 coming next month.

I see 7.0.5.0 is now available on the download page I thought we'd have a longer wait when you said next month? I assume the fix is in this release and we are good to go ahead with deployment?

#29 Patrick Keil

    Administrator

  • Administrators
  • 3132 posts
  • LocationSingen, Germany

Posted 26 June 2017 - 10:58 AM

Hi,

correct, 7.0.5.0 was released a little earlier than expected.

#30 BH1

    Advanced Member

  • Members
  • PipPipPip
  • 49 posts

Posted 07 July 2017 - 03:01 PM

Hi Patrick,

We're still having this process in 7.0.5.0, has it returned? How can we resolve this please? Unfortunately, it's making our chat service unusable.

Bex

Version 7.0.5.3

#31 lhcampos

    Advanced Member

  • Members
  • PipPipPip
  • 61 posts

Posted 26 July 2017 - 01:22 PM

We are using the version 7.0.4.1 with the fix downloaded here. It is working fine.

Now I am thinking about update to the last version, but I am afraid of this bug, specially after reading the BH1's message.

Is it safe to update?

#32 Patrick Keil

    Administrator

  • Administrators
  • 3132 posts
  • LocationSingen, Germany

Posted 26 July 2017 - 02:28 PM

Unfortunately, I don't know.

As you know, we never managed to reproduce this problem and the fix provided was on spec. I don't know if the problem was actually fixed in 7.0.4.1 and we don't know if it came back in any later update.

What I can tell you is:

1.) The change provided in 7.0.4.1 was not removed or revoked. It's still included in 7.0.6.0
2.) There are no other users reporting that the issue has returned (which does not necessarily mean much since all affected users seem to be contributing to this topic).





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users