I’ve been working on my first html template to Wordpress theme conversion and every thing was going great (aside from having millions of tabs open trying to figure out how to best use the template tags), until I started working on a theme options page in functions.php.

Originally this was working ok, and then after one save BAM!  The damn thing crashed on me.  So I opened Dreamweaver back up again and it was working just fine, until again, I opened the functions.php file and it crashed.

I renamed the file to have a .txt extension and when I opened it up this time it worked just fine.  I started getting sick of editing the file as a .txt and then renaming it to .php to test it out on my local Wordpress installation so I took time from being neck deep in template tags and php code to see if I could find a solution.

Lucky for me I found it!

Issue

Adobe Dreamweaver CS3 crashes when working with certain PHP or ASP files in Code view or Design view after the clock goes back one hour, when Daylight Savings Time ends. The crashes only occur when selecting certain lines in Code view, or selecting certain objects in Design view. The crashes only occur in files that have PHP or ASP code, intermingled with HTML code. The crashes do not occur in Dreamweaver 8 or earlier (Ref. 229536).
Reason

The Dreamweaver CS3 WinFileCache-AD76BB20.dat file has been corrupted by the time change.
Solution

1. If Dreamweaver is open, quit the application.
2. Delete the WinFileCache-AD76BB20.dat file from the Dreamweaver user configuration folder. Note that on Windows, the Application Data and AppData folders are hidden by default, so verify that your Windows Explorer folder options are set to View Hidden Folders. The location of this file is as follows:
* Dreamweaver CS3 on Windows Vista:
C:\Users\[username]\AppData\Roaming\Adobe\Dreamweaver 9\Configuration
* Dreamweaver CS3 on Windows XP:
C:\Documents and Settings\[username]\Application Data\Adobe\Dreamweaver 9\Configuration

This solution was found after looking through several forums and was taken here from the Adobe websites.

So if you are having the same issue, and it matches the problem description – try this out.  I hope it works for you and doesn’t slow down your work-flow as much as it did mine.