Why I don't use Dreamweaver - or How to lose 2 hours with a single character

I don't use Dreamweaver personally - I've used CFEclipse for pretty much all CF development since August 2004.

Some of my colleagues however (mainly those of a less code centric bent) do persist in using Dreamweaver - although after this fiasco, at least one of them may move over to CFEclipse.

A colleague asked for my assistance because Dreamweaver had crashed on his machine, and when he tried to reload it Dreamweaver would close immediately after displaying the splash screen.

I initially suspected that Dreamweaver's site cache may have become corrupt when Dreamweaver crashed, and that this might be preventing Dreamweaver from reloading. After a brief google, I found this adobe technote which gives instructions on diagnosing and fixing these kind of issues.

I started by deleting Dreamweaver's site cache - this was progress, as Dreamweaver now took slightly longer to crash, as it had to rebuild the site cache first.

I then renamed the key in the registry that Dreamweaver uses to store its site definitions. Dreamweaver now loaded without crashing.

I then restored the site definitions, and went through removing sites until I had identified which site had caused Dreamweaver to crash (Which not surprisingly was the one he had been working on before Dreamweaver crashed).

My colleague then attempted to recreate the site, but as Dreamweaver attempted to build the site cache, once again it crashed (although it did at least give a (meaningless) error message this time. Fortunately it did crash before saving the site definition - otherwise we would have had to delete the site from the registry again.

My colleague then tested creating another site, pointing to a different location, and had no problem in doing so. This suggested to me that there must be something in one of the files in the problem site that Dreamweaver did not like - possibly an invalid character in the middle of being written to a file when Dreamweaver crashed.

I then instructed my colleague to check all the files that had changed since last checkin - opening them individually to look for anything strange - strange characters, mid file truncation etc.

The 6th file he attempted to open, immediately caused Dreamweaver to crash.

So what, you may ask, was the problem with this file?

The file was a css file.

The invalid line:

width: 489 p'x;

So, there you go - inadvertently inserting a quote mid dimension in a css file, will cause Dreamweaver to go FooBar - and, because of the site cache, this will prevent you from opening the site at all!

Related Blog Entries

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)
waterbaby999's Gravatar Just had the very same thing happen to me with Dreamweaver 8 - even tried uninstalling/reinstalling with no joy then assumed it was something to do with the registry. Mine happened when DW crashed my pc while uploading to my site - i guess that was how it corrupted itself. Thank you muchly for the link to the technote, saved me ejecting my machine out the window!
# Posted By waterbaby999 | 12/04/07 20:29
Dan Lancelot's Gravatar Heh waterbaby999 - glad to help...

You know, I did suggest that option (throwing the machine out of the window) after about an hour - for some reason our MD did not think this a viable option :(
# Posted By Dan Lancelot | 14/04/07 00:53
Mike L's Gravatar I just tried commenting out styles within an external style sheet using /* and */ in Dreamweaver MX 6.1, Mac 10.4, resulting in crash after crash, but only when working with files from that specific site. Other sites worked fine. As soon as I removed the /* and */ (I had to use text edit to do it), Dreamweaver behaves as usual.
# Posted By Mike L | 05/06/07 03:21
bclow's Gravatar Ah ha! You just saved me from hours of troubleshooting and from reinstalling dreamweaver cs3 on vista. Dreamweaver crashed on me while saving a css file. It was a simple addition, but when I saved the file Dreamweaver crashed. Then when I restarted DW, it would get as far as loading the site cache and then quit. I thought that was the problem so I deleted the site cache, then the config folder and was about to reinstall when I came across your post. I removed my one css line change and deleted the "LCK" (contribute) file that related to my css file. It was able to rebuild the cache and launch completely. You get extra karma points for that one! Thank you!!
# Posted By bclow | 27/07/07 00:13
Daniel Lancelot's Gravatar Glad to be of help :)
# Posted By Daniel Lancelot | 31/07/07 00:00
talavan's Gravatar I also had a problem when I added comments with /* */ in my CSS file: Dreamweaver CS3 didn't load nor apply the CSS styles in the design view, which was quite annoying. Browsers displayed the page correctly. Removing the comments would restore the correct behaviour.
It seems even the most recent version of Dreamweaver don't get on well with commented CSS files :(
# Posted By talavan | 01/08/07 09:08
Carl's Gravatar I had the same issue. I tied reinstalling and deleting everything under the sun. Nothing worked until i read your blog and found this line in my CSS.

<div class="code">#sign img, {</div>
# Posted By Carl | 02/08/07 11:28
Damian's Gravatar wow the web gods are smiling on me tonight...this just happened to me i was like wtf...i googled and read your blog and comments before doing anything else and prolly just saved myself hours of cursing and punching holes in the walls.

my house and my stress levels thank you all for sharing.
# Posted By Damian | 07/08/07 04:24
Shawn S's Gravatar Wow! Great post. I had never run into that issue before until today. I did repair Dreamweaver CS3, but did not completely reinstall, so I didn't lose all my sites/settings/preferences.

As you and others have mentioned, I too was editing a .css file when it crashed. The bit that apparently crashed me was a reference in the .css to a class file that I hadn't put in yet in the .html file: .h_link h2 a { display: block; height: 30px; } .h_link h2 a:hover { background: transparent; }

The class had originally been a div id and I was trying to save myself some extra cod by trying it as a class instead. It crashed right after I changed the id to a class and saved the .css file. Putting the two lines back as an ID instead of a class fixed things.

Again, thanks so much for this fix.
# Posted By Shawn S | 11/10/07 19:42
Tim's Gravatar Thanks for the information.

My Dreamweaver (CS3, Windows XP) crashes when I try to open a particular ASP file. I stripped my code and eventually found the cause of this problem. It crashes when I add this line in my code:
"Set comProfLocSet = Server.CreateObject("ADODB.Command")"

When I delete this line, or when I edit this line (rename comProfLocSet to comProfLocZet) it runs fine...

I have no clue why, but it works fine. I might be the name of the object (comProfLocSet), but it's very strange.
# Posted By Tim | 22/10/07 11:01
jesse's Gravatar my long css comments were broken into two lines instead of one liners.
# Posted By jesse | 15/11/07 02:33
jason's Gravatar weird dreamweaver keyboard mapping problem... fixed the problem, but hope this helps someone...

email me at "fred ((((at))) thought foundry (dot) com"

I was having a weird problem in dreamweaver... Whenever I was in code view and typed "shift+i" to make a capital "I", instead it would paste from the clipboard.

I finally figured out what was happening. I compared the menu.xml in my app support folder in the user library to the original menu.xml file that was in the application folder. I went through until I came across the diff:


menu.xml in my library/app support folder:
<!-- Windows Navigation Shortcuts -->
   <shortcut key="Cmd+Ins" name="Copy2" platform="" command="if (dw.canClipCopy()) { dw.clipCopy() }" domRequired="FALSE" id="DWShortcuts_HTMLSource_Copy2" />
   <shortcut key="Shift+Ins" name="Paste2" platform="" command="if (dw.canClipPaste()) { dw.clipPaste() }" domRequired="FALSE" id="DWShortcuts_HTMLSource_Paste2" />
   <shortcut key="Shift+Del" name="Cut2" platform="" command="if (dw.canClipCut()) { dw.clipCut() }" domRequired="FALSE" id="DWShortcuts_HTMLSource_Cut2" />


orig menu.xml file:

<!-- Windows Navigation Shortcuts -->
   <shortcut key="Cmd+Ins" name="Copy2" platform="" command="if (dw.canClipCopy()) { dw.clipCopy() }" domRequired="FALSE" id="DWShortcuts_HTMLSource_Copy2" />
   <shortcut key="Shift+Ins" name="Paste2" platform="" command="if (dw.canClipPaste()) { dw.clipPaste() }" domRequired="FALSE" id="DWShortcuts_HTMLSource_Paste2" />
   <shortcut key="Shift+Del" name="Cut2" platform="" command="if (dw.canClipCut()) { dw.clipCut() }" domRequired="FALSE" id="DWShortcuts_HTMLSource_Cut2" />


There was a diff in the "platform=" tags. The orig stated [platform="win"], my config stated [platform=""] (nothing in between the ""'s). So, I reset the platform tag to be [platform="win"] in my settings and then relaunched dreamweaver. It fixed the problem.

Not sure how this occurred, but it works now.
# Posted By jason | 20/11/07 19:49
Mike Padgett's Gravatar Also ensure that, if your CSS crashes Dreamweaver CS3, it's not because of the filesize (crazy but true):
http://www.mikepadgett.com/blog/template_permalink...
# Posted By Mike Padgett | 16/02/08 13:52
john's Gravatar I had the same issue-an invalid CSS declaration: margin::0; Thanks for the posting!
# Posted By john | 19/11/08 16:14
Tovi Ellesse's Gravatar Aaaarrgghhh, just saw this after a WHOLE day of pulling my beard out. Even went for a shave after a while.

Thanks a lot!! If I had just seen this in the morning. I uninstalled, reinstalled, made a new user .... $%#^^
# Posted By Tovi Ellesse | 13/01/09 18:06
LuFace's Gravatar I had the same problem. Some manually edited margins didn't have a px value--for example    margin:0; I just added the    margin:0px; value and it worked fine. I went through an hour of adobe support and realized it was crashing everytime it got near the non-valid css file.
# Posted By LuFace | 18/02/09 05:39
Michiel's Gravatar While your issue was more that two years ago, it's still helpful!
I've spend several hours reïnstalling DW CS3 and deleteing keys and caches because of crashes.
At first, it wouldn't startup at all. Later on it crashed when rolling over the files of a particular site only (the one I was working on).

I found your issue. I changed my CSS comment:

/* INTRO PHOTO'S */

to

/* INTRO PHOTOS */

And that was all. ONE SINGE CARACTER was causing a mayor crash and after that not even starting up again!!
I've removed it with the freeware Cream text editor... Wich I'll probably will use more ofter in the future ;)

Thank you very much for sharing this, I wouln't have found this myself.

(actually it was in Dutch: intro foto's)
# Posted By Michiel | 29/07/09 22:03
prhmusic's Gravatar Thank you for posting this. I found my site cache here:
C:\Users\<user ID>\AppData\Roaming\Adobe\Dreamweaver 9\Configuration\SiteCache
I use Vista.
# Posted By prhmusic | 31/12/09 13:43
rhino boombox's Gravatar Thanks for this post! I tried repairing and deleting the site cache, and was running out of options. Just edited my CSS with a text editor, and it appeared to fix my issue.
# Posted By rhino boombox | 17/08/10 19:27
A dev's Gravatar Thanks a lot for putting up this post.... you have helped again a Dreamweaver user ;-) ... more then 3 years afterwards!

Have a great day!
# Posted By A dev | 10/09/10 12:37
BlogCFC was created by Raymond Camden. This blog is hosted by DotLance Ltd.