Just upgraded to eCart 6.0.9

1. Is there a reason I get a splash screen that says eCart 5?
2. I get two javascript errors. One is in DW CC 2014.1 (build 6497) that prevents the app from running, one is in CC (v 13.2/build 6466) that is called on updating anything in a cart's settings (originally eCart 4). Both errors are attached with screenshots. Thoughts?

Thanks in advance.

1) sounds like eCart 5 may not have been properly ubnisntalled before installing eCart 6.

2) We are working on updates for compatibility with DW CC 2014.1

We are doing testing now and should start rolling out updates early next week.

We will do DataBridge, MySQLi, eCart, Design Extender, then Free tools in that order

It may take a week or two to get them all out since literally every interface is being touched and will have to be re-tested.

in the mean time, I have found that it is possible to install earlier versions of the creative cloud apps through the Creative Cloud Desktop Manager, this will allow you to install DW CC until we can update the extensions for CC 2014.1:

http://blogs.adobe.com/kevinmonahan/2014/01/29/revert-to-a-previous-version-of-premiere-pro-cc-or-any-creative-cloud-application/

1. I went from eCart 4 to 6, never installed 5 so that can't be it.
2. OK. I still have CC (13.2) installed and working from there, so no worries. But I still get JS messages with that. I will remove the config folder and do fresh installs of the .zxp files...

UPDATE: Please see attached screenshot. I dumped the config folders and started over with the .zxp files. This is CC (13.2), *not* CC 2014.1. It appears the error is due to the fact the js file is not there...

Please provide a Skype username or a US phone number and a good time to contact you when you will be in front of your computer and we will have an engineer contact you to resolve this issue over the phone.

We are available Monday - Friday from 9am - 4pm EST (except major U.S. holidays).

Updating to 6.1.0 (and updating all of the other WA plugins) fixed these errors. The script errors did go away after waiting for the full downloads and restarting. Thanks for your help and making the updates!

Glad to hear it is working.