SSL support for desktop client

Hi,

Just mande last weekend update. Now desktop client supports SSL. Just enter address with https://. Also now you won't have to enter / at the end. So it's more user friendly.

Have a fun.

New version 1.50v third parties cookies dependency drop.

This version brings one enchancements on which I spend about 20 hours. From front end part nothing changes but there is big change how backend works. Here is summary what was done.

As we all know, FF has plans to block third party cookies and I have seen this effect while some mails I got told, that they cannot a help session question because of captcha and the reason sometimes was, that chat was working on different domain than their site itself. So this updated fixes this problem. This problem is relevant only if you have embeded chat in different domains.

Some technical info what was doone

1. PHP sessions support for frontend users was dropped. We now relay on single cookie record and HTML5 Web Storage.
2. This allows us to have single installation and use chat on multiple domains without a problems even if user has disabled third parties cookies. This app will work smoothly.
3. Added header to prevent JS caching. This was the issue with IE. Why does all the problems comes with IE always? :D :D

So even after http://howto.cnet.com/8301-11310_39-20042703-285/disable-third-party-cookies-in-ie-firefox-and-google-chrome/ these settings in user browser chat will work. I do not know any other open source client which would support multiple domains without any issues,

P.s If you notice any issue let me know. No database update required this time.

We have icons for tabs instead of names now :)

Screenshot tells it all.

Just update your version from github. No database update required if you have 1.49v. Demo also was updated.

New version 1.49v few usability updates

New version.

1. From now messages like "user has left chat", "user has joined chat" will be shown where you see what user is typing or user is typing message. This will avoid flood in chat itself.
2. You can configure default Operator name for proactive chats.
3. If user starts chat from proactive widget, to user won't be shown message that we are pending operator to join chat.
4. Adjusted how print icon is shown in widget.

execute doc/update_db/update_33.sql and follow standard upgrade instructions

Don't forget to donate if you like LHC :)

New version 1.48v securing application

This update brings security enchancements in various places and focuses to pervent CSRF attacks.

No database required this time.