Error on Dreamweaver Startup

I have just updated Design Extender 1.0.4. Now when I start Dreamweaver I get the attached error message.

A few people have reported this today. I think it is probably a conflict with eCart. We'll be looking into it and getting out a fix shortly.

The good news is, it appears you can just ignore that message and it won't cause any problems with any functionality for now.

I got it too, and furthermore, I got the attached message when I tried to run the import site wizard for the first time, before activation. Hope this helps.

After that error pane, it said "Failed to create panel 25" or some such number. And then I got the activation screen, which worked, and so did the Import Web Page(s) wizard.

But when I ran it, I got the second attachment about panel 159, then the third attachment about line 262, twice. The wizard then bailed, with no resulting download. The errors were repeatable, exactly, over & over.

Hope it's ok to tack this on here. I thought it was pertinent.

similar error even after having delted the extension (via extension manager) and dreamweaver cache file. please see attachement showing 3 errors i get when launching dreamweaver.

windows xp sp3, dreamweacer cs4

I think at least some of the errors reported in the last two post are caused by Dreamweaver trying to render a dock that doesn't exist anymore. I believe the Momento has been removed from the new extensions there may well be others. If you hade a saved workspace that included this in the dock then you will get an error. Try deleting your saved workspace and recreating it. Might help.

i have reconstructed my workplace and second and third error message go away.
i still have first message "at line 12 of file .... shared.js : wa is not defined.
ecart 5.0.3 is installed in my dreamweaver cs4.

we have identified that the error:

shared.js : wa is not defined.


is being caused by eCart 5.0.3 and CSS Sculptor 3.0.2.

We have released an update to ecart 5.0.4 to correct the problem, and will be releasing an update to CSS Sculptor as well. in the mean time, this error should not effect functionality if you just ignore it.