Chat+ v.0.20.0

Download

Upgrade instructions

What were the changes from 19 to 20?

Upgraded with no problems. Thanks.

Well, I spoke to soon.

After restarting chat server, all I get now is a redirect to https://localhost/.

Just to make sure it was not me or my servers. I tried this twice.

I have two chat servers, the first one I upgraded was the latest working version .19 which was working fine.

The other server was running version .13 and running for testing only..

As my above post states, after upgrading to .20 from .19 I get redirected to localhost.

So to prove myself it was not something I did, I decided to upgrade the second chat server to .20, I am now getting the same redirect to nothing!! I'm very frustrated and am at a dead end on how to continue.

Killing the chat, then removing the "bundle" directory and re-uploading .19 and extracting has not helped. Same results on both servers now no matter what version.

Have I missed a step with the node? MongoDB need to be changed?

I'm a complete freshman to this so any help is appreciated.

Its says that the db should be updated with the correct information after update...  i have it running on a cPanel server i was just going to try and upgrade....  

not sure if i feel like it now.   For the life of me though i cant get it to work with https with a comodo ssl cert.  tried for hours.

.19 version

well i said screw it and did the update...  seems ok on my end.  

linux/centos7/cpanel server  running it straight from domain.com rather then a sub domain. 

this time i installed it with https://domain.com but it still loaded with http://domain.com   

not sure what gives with that.

 0.20.0

 I was able to do that.

No progress yet on fixing what I did. 

Even if "Site URL" is different in the chat settings, it shouldn't redirect automatically, upon admin login it should ask you if you want to change "Site URL" to different one. 

Please check your HTTP server settings, maybe something was changed there, since redirect most probably happen on web-server side.

Also did you unpack new version to the new directory or old directory was overwritten with new version ?

Also try to access Chat+ directly, without web-server, like http://1.2.3.4:3000

One more thing is to try in another browser, for the case if redirect was cached in the browser.

Hi Alex,

my 7.2.1 to 7.3 was done today and Chat+ runs fine at Google Chrome.

At Safari though can not see the messages at Chat and Helpdesk is transparent partly.

:-) I love it though :-) and I'm happy to be back after 2 years off :-)

 PM me if you still cant get the ssl to work properly.

 The servers were never rebooted, therefore nothing changed with the servers as far as configuration.

I extracted the files to the current "bundle" folder as I did with the other upgrade.

The only way it works now is removing the redirect and pointing to a ".com" site I have.

.19 works there but not redirecting to a subdomain like previous.

I gave up and just using it now pointing to a domain and not subdomain, members are not interested with it, so I have time to see if I go with this chat.

 Members will only be interested in Chat+ if it is integrated with dolphin properly, means it will replace the simple messenger along with Real Time Notifications. Right now chat+ is doing same what a timeline does. Consider timeline in a group and you will have Rocket.Chat.

 what I did was add a button on the profile page that opens a small window with the Chat+ - but in a direct message between you and the other person. What I need to do next is set it up so that if the person is not online, then the button will not show. Then - finding some way to give them a desktop notification within dolphin.

As it stands right now, if the chat is open in another window (full window mode in 7.3), there are desktop notifications. If the Chat is NOT open in another window and NOT open in the Dolphin site (7.3), then the desktop notifications do NOT work. Push Notifications for mobile devices DO work as long as user has NOT logged out of mobile app chat - chat may be closed, though.

So,  I would recommend that the chat open in its own window - possibly with no navigation links, search block, breadcrumb, footer, or service menu - just the logo. This way - desktop notifications do work, and the chat can still be ran in the background if user wants to browse through site.