Aloha,

An interesting problem.

We have been using the desk with long statements, and have not found this problem so far.

1. if at all possible, please upgrade to the latest version, if your not already 2.1.7.

2. If the problem persists, please repost and we can go from there.

3. You can find the link for 2.1.7 here:  http://www.helpcenterlive.com/downloads/

The author corrected many things since older versions, so dealing with problems in older versions is just too much to deal with... Thanks for understanding.

Respectfully,

AR

Aloha,

Sorry, that is going to be an issue for the author then.  You may have discovered a new BUG.

Please do the author a big favor...please post a very specific followup here with details to save him time ok.

1.  Server OS your using, ie; Linux Debian, Centos, etc.
2.  Server software, ie; apache, etc.
3.  PHP Version
4.  MySQL version
5.  Operator OS and Browser
6.  Visitor Browsers tested.

Also any other details that may help him check your problem. 

Then, after posting this info.  Please PM HCL ADMIN with your URL and mention this post, so he can take an expert look see.

Cool.

Thanks

Sorry I can't help more with this one.  I will be watching however, as we are going to upgrade ours from 2.1.4 to 2.1.7 next, and I don't have that problem now, so hope it is not a bug, but need to see what the Author figures out...

Aloha, AR

Aloha,

Sorry I cannot answer for him on that...

Note, I am still unsure of your version.  But, I think your problem is TIMERS...

See file:  config.php

Note TIMERS AT END:

    // Timers
        // The default settings should be ok.

        // The number of second to put a chat on hold
        $conf['chat_hold'] = '6000';

        // The number of seconds the operator has to accept chat before
        // it polls to next operator
        $conf['session_timeout'] = '15';

        // The number of miliseconds to refresh the tracker.
        // This checks for initiated chat requests and updates the
        // visitors timer so they do not reamin idle and -- timeout 5 seconds
        $conf['tracker_refresh'] = '5000';

        // The number of seconds the visitor can remain idle until
        // they timeout.
        $conf['traffic_timeout'] = '180';

        // The number of seconds the visitor can remain idle until
        // their total time on site updates as a new visit.
        // Note that if this is different to $conf['traffic_timeout'] and the
        // user revisits a page after between the $conf['traffic_timeout']
        // and $conf['traffic_newvisit'] period the traffic monitor will not
        // refresh to show the visitor again.
        $conf['traffic_newvisit'] = '180';

        // The number of milliseconds to refresh the chat window to check 
        // for new chat messages recommended is 3000 to 6000  3-6 seconds
        $conf['chat_refresh'] = '2000';

        // The number of seconds until the chat session times out
        $conf['chat_timeout'] = '300';

        // The number of miliseconds to refresh the cobrowse tracker.
        // This checks for new cobrowse, coforms and comarkers activity.  5 seconds
        $conf['cobrowse_refresh'] = '5000';

        // The number of milliseconds to refresh the request monitor to check
        // for any new visitors or chat requests recommended is 3000 to 5000 3-5 seconds
        $conf['monitor_refresh'] = '2000';

        // The number of seconds the operator can remain idle until
        // their status changes to offline
        $conf['live_timeout'] = '120';

        // The number of milliseconds to show the initiate image 30 seconds = 30,000 ms.
        $conf['initiate_timeout'] = '300000';

Set these carefully, and I think you may solve your problem..

Aloha

AR