Support forums - Upgrading from version 3 to 4

Support forums » Products » Cute Live Support » Re: Upgrading from version 3 to 4

Upgrading from version 3 to 4

Last post 02-13-2008, 10:41 AM by phat_bastard. 4 replies.


	Sort Posts: Previous Next

01-31-2008, 5:18 PM 36712

ppritchard
Joined on 07-26-2007
Posts 6

Upgrading from version 3 to 4

Reply Quote

I'm starting a new thread to ask about the upgrade process from Live Support 3 to Live Support 4. I downloaded the installation package and read the deployment guide. This seems to assume that you are deploying a brand-new installation. What is the process for upgrading an existing installation to version 4?

Also I see that the SQL creates a new set of tables, all prefixed with "CuteChat4". For example, now we have CuteChat4_SupportAgent instead of CuteChatUser. How do we transfer configuration, users, support logs, etc. from version 3 into version 4? I don't see an SQL upgrade script.

One of the main reasons we purchased CuteSoft Live Support was the ability to integrate it with our existing database and our existing authentication system. We modified the GetUserUniqueName, GetUserDisplayName, SearchUserUniqueNameByDisplayName, and SupportLogin functions in global.asax for this purpose. I do not see these functions in global.asax in version 4. We need to have, at a minimum, the same functionality that we have now. How do we accomplish integration with in version 4?

02-01-2008, 8:39 AM 36728 in reply to 36712

Adam
Joined on 09-23-2003
Aurora, ON
Posts 18,678

Re: Upgrading from version 3 to 4

Reply Quote

ppritchard,

There is no upgrade path from version 3.0 to 4.0.

You need to install 4.0 from scratch.

>>I don't see an SQL upgrade script.

The version 4.0 uses different DB table than version 3.0.

>>How do we accomplish integration with in version 4?

Please check the following article:

http://cutesoft.net/Live-Support/Developer-Guide/scr/Integration_Overview.htm

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

02-12-2008, 2:09 PM 36980 in reply to 36728

phat_bastard
Joined on 05-31-2007
Posts 20

Re: Upgrading from version 3 to 4

Reply Quote

Wow, I'm glad I don't have any integration to port over. Nice of you to just change the db schema and not provide a tool to convert exiting users, canned messages, etc. Is anyone else a bit miffed about this? Isn't the point of paying for software to save the users and admins time?

02-12-2008, 9:50 PM 36984 in reply to 36980

Adam
Joined on 09-23-2003
Aurora, ON
Posts 18,678

Re: Upgrading from version 3 to 4

Reply Quote

phat_bastard,

The version 4.0 release is a major version release. We totally rewrote the application.

This is the choice we have to make to improve this product.

If you ingegrate the live support with your own membership database, the integration is easier.

http://cutesoft.net/ASP.NET+Chat/Developer-Guide/scr/DeploymentIntegration.htm

>>canned messages

The canned messages in version 3.0 can be used in version 4.0.

For the exisitng users, please recreate them using the admin tool.

In version 3.0, the user can register in the web portal.

In version 4.0, the user can register in the web portal, all users are created by admin.

Hope it helps.

Let me know if you have any further questions.

02-13-2008, 10:41 AM 37005 in reply to 36984

phat_bastard
Joined on 05-31-2007
Posts 20

Re: Upgrading from version 3 to 4

Reply Quote

Oh I will have further questions. Moving to new threads...

Regarding the schema changes:

Where are the canned messages stored?
You've stated in other threads that all the v4 data is stored in tables prefixed by CuteChat4_..., but why are the users stored in a table named SampleUsers?
Which if any of the old v3 tables can be deleted?
Would it really have been that much work to build an import routine? Essentially you added one row to the previous users table.
The 'deployment' documentation should reflect that there is no upgrade path so everyone will know not to pollute their old v3 database with v4 changes.