eCart5 Display Manager crashes Dreamweaver

hi

Every time I try and use the Display Manager it crashes Dreamweaver.

I've uninstalled all of my extensions, deleted the Mac cache file and reinstalled Ecart 5 but the same thing happens.

Im using OSX 10.6.3, DW CS3, eCart 5

Please respond asap

many thanks

before applying the display manager, make sure you have completed the following:
1) Create a new site in Dreamweaver, on the testing server tab of the site definition, select PHP/MySQL as the server language.

2) Create a new PHP page and save it to your site.

3) Open the new PHP Page, then create a new eCart object. Go to Insert ->WebAssist -> eCart -> eCart Object.


If you continue to have problems, please post back the following information:
Site Settings - Local Info tab:
what is the Local Root Folder?
What is the HTTP Address

Site Settings - Testing Server Tab:
What is the Server model?
What is the Access?
What is the Testing Server Folder?
What is the URL Prefix?

can you send a copy of your WA_eCart folder so I can try to recreate the problem.

hi Jason

Apologies - it's actually the Checkout Wizard that's crashing Dreamweaver.

I've followed your instructions above and added a quick cart, but the Checkout Wizard still crashes DW immediately.

I've zipped up screen grabs of the local and server site tabs, plus the eCart folder and also one of the php pages.

Thanks for your help Jason, please shout if you need anything else.

I see you have the site files stored in a folder named "Work - rtmedia". can you try to create a new site in a folder that does not contain any special characters, such as the "-" in it and try running the checkout wizard again?

hi Jason

Yes that works - strange as I've been using this folder for all my work over the last 8 years... with eCart 4

Has eCart5 changed in that respect ?...

thanks for your help

It seams eCart 5 has an issue with site folders that have special characters in their names. I will log this as a bug.

Dreamweaver itself can be flaky with special characters in path's, it is listed in step 8 of the Adobe javascript error troubleshooting guide:
tn_19105.html