Upgrade to Dreamweaver 8 Detail :: Dreamweaver MX - problems wihtout end

Since I've used Dreamweaver MX I've experienced so many problems the user would never guess, MX saving pages wrongly (this is a documented problem, even Adobe admits too) but most of all, the most irrating,  time consuming, and  business-preventing problem by far is that fatal exception error on pages.  MX closing down without warning by itself.  Now with (4) extremely valuable pages on a site that I absolutely must edit, right now,  --  I can't barely touch these pages without MX at will while shutting me out of these pages.   Several programmers tried steering me clear of MX way back when I started, but  I didn't take their advice obviously. The quality of MX, speaking of reliability, would take terms I don't care to mention on this post.

The response to this from Adobe, of course, who I have contacted by phone, is to upgrade. Spend  more  with us now if you want an actual working version.

Shouldn't software perform on at least a functional level no matter the version?  

Have the Impakt extensions 3.5.1 Impakt/MXCalender at least now work with Dreamweaver 8? 

Hi Brad,

I am sorry for the late reply. I am not sure I can help you with this problem, as it can be related to a native Dreamweaver MX 6.1 bug that causes pages that are of bigger code size (4 K on MAC machines and 65K on Windows) to crash the DW emvironment.

Please let me know if you have DW MX installed on a MAC machine or on a Windows and how bigger your files are.

Regards,
Ionut

The latest version of ImpAKT is 3.7.1 and latest MX calendar is 1.8.6 and yes, they work fine with DW 8.0.2.

Ionut

Ionut,

Thanks for the response. MX is installed on Windows XP

- file sizes around 150 kb

What about Impakt 2.8.1 (many files not yet converted over)

This is crashing expecially when there is a showif condition ( series of 10+ conditions) placed within a repeat region. (link directs)

The files actually work for a while, but only temporarily.  When re-opened, placing the curosor over these and it will crash.  I was more than a little disappointed to find MX can actually mis-save information, which has been the source of a number of problems. Not exactly a designers dream. Can I assume this have been corrected?

I've actually thought about hunting down Dreamweaver 2004 if 8 doesn't work with Impakt.

As I told you, the problem only stays with the MX 6 version of Dreamweaver and it is not related to our extensions. The should be no problem editing the pages in DW 2004 or DW 8.0.2.

You could attach here a zip with a sample page that has the problem, a screenshot form the Extension Manager window and tell me what are the exact steps you do to get to cause the crash. I will try to make a test myself with another DW version and let you know.

Ionut

Hi,

I have performed a test on the page you attached and it worked fine.

So please try these:

Ionut,

Were you able to replicate the errror?

(this should indicate  source of the error message)

Did you test with MX? Which as I said was giving the error mess. 

You tell me 'it worked fine' but this does not tell me the source of the problem.

I've tested the page with all 3 versions of Dreamweaver and couldn't reproduce the problem. So please try my advice above, because the problem may be related to some conflict within the configuration files of your DW.

Ionut

Ionut,

MX Kollection 3.7.1? ( not 3.6.5?)

I'm assuming it's okay to put these type of showif conditions within the repeat regions.

An alternative I guess is to write these showif's as straight php, which I'm trying to avoid.

MX Kollection 3.7.1 is designed to work (and tested) with DW 2004 and DW. So my advice is to stick to version 3.6.5.

The code you have looks OK, I did not face your problem.

Ionut

ENTRY OMITTED - I apologize for the inconvenience.