Troubleshoot JavaScript errors | Dreamweaver CS4, CS5, CS5.5, CS6

When you perform tasks within Dreamweaver, you sometimes encounter a JavaScript error message. These design-time JavaScript errors usually prevent you from implementing a portion of Dreamweaver functionality.

Example: The following JavaScript error message can appear when you save a file:

Another example of a possible JavaScript error: "While executing onLoad in tempURL_afterSave.htm, a JavaScript error occurred."

Important: These pop-up JavaScript errors in Dreamweaver are different from JavaScript runtime errors you encounter when viewing a page in a web browser. JavaScript errors in a web browser indicate a problem with embedded or linked JavaScript in the HTML page. These types of runtime JavaScript errors are beyond the scope of this TechNote. See the Dreamweaver Help files for errors resulting from JavaScript that Dreamweaver generates. Or, see a third-party JavaScript reference for troubleshooting hand-coded JavaScript.

Sometimes, a translator error message accompanies these internal JavaScript errors:

The following translators were not loaded due to errors: ASP.htm: has configuration information that is invalid. ASP.NET.htm: has configuration information that is invalid. ColdFusion.htm: has configuration information that is invalid. PHP_MySQL.htm: has configuration information that is invalid. JSP.htm: has configuration information that is invalid. XSLT.htm: has configuration information that is invalid.

Dreamweaver uses JavaScript to perform numerous internal actions. Adobe has implemented much of Dreamweaver functionality by using JavaScript files. This heavy use of JavaScript helps to make Dreamweaver easily extensible. Developers only have to have a good knowledge of JavaScript and access to the Dreamweaver API to add to or change the native functionality of Dreamweaver. However, the errors that Dreamweaver generates if it encounters a problem executing some action tend to be JavaScript errors.

JavaScript errors in Dreamweaver usually indicate a conflicting Dreamweaver extension, a conflict with the code on a page or a bad installation of Dreamweaver. Here are a few questions that can help you isolate the problem:

• Does the error occur when using a specific feature?
  For example, do you see the same error message every time you attempt to create a web photo album? This error can indicate a conflicting extension or a bad installation of Dreamweaver.
  
  
• Does the error occur on a specific page or with all pages?
  If the error doesn't occur with all pages, then you can have a conflict with some code on a particular page.
  
  
• Does the error occur in all sites or just one?
  To test this issue properly, make sure that you test a different site that does not use the same files. If the error only occurs in a certain site, then the issue can be specific to files and code within that site.
  
  
• Does the problem persist if you restart Dreamweaver?
  If the problem does not recur on relaunching Dreamweaver, then it's possible that a JavaScript file loaded incorrectly.
  
  
• If using a server behavior, does the problem occur with all databases and tables?
  If not, then it's possible that you have an issue with the database connection files or with the tables of the database itself.
  
  

After answering the questions above, follow the steps below to troubleshoot the errors:

Adobe has documented a number of known errors within Dreamweaver and have provided information to assist you in resolving the problem.  For a list of known issues, see the Known JavaScript Errors Chart.

Updates provide fixes for a number of issues identified within Adobe applications. Download updates from the Adobe Updates page.

For example, if you have a behavior applied to an image, then that image must have a name. Likewise, if the behavior references another image, then that image must also have a name. All object names must be unique and must meet other criteria. Object naming is described in Naming strategies for Dreamweaver and various interpreters (tn_14610).

Delete the WinFileCache-7A9586CB.dat, MacFileCache-BFE7CE2E.dat, or FileCache.dat file from the Dreamweaver user configuration folder. Adobe recommends that you delete the FileCache.dat file if you are experiencing a JavaScript error related to "dwscripts. " Also delete the file if you receive a "translators were not loaded" error. The string of characters after "FileCache-" can differ on your machine. The location of the FileCache.dat file depends your operating system and your version of Dreamweaver. 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.

Note:  The [language] folder below is an abbreviation of the language you are currently using.  Typically there is only one folder in this location.

• Mac OS:
  
  Dreamweaver CS6: /Users/Your User Name/Library/Application Support/Adobe/Dreamweaver CS6/[language]/Configuration
  
  Dreamweaver CS5.5: /Users/Your User Name/Library/Application Support/Adobe/Dreamweaver CS5.5/[language]/Configuration
  
  Dreamweaver CS5: /Users/Your User Name/Library/Application Support/Adobe/Dreamweaver CS5/[language]/Configuration
  
  Dreamweaver CS4: C/Users/Your User Name/Library/Application Support/Adobe/Dreamweaver CS4/[language]/Configuration
   
• Windows 7 or Windows Vista:
  
  Dreamweaver CS6: C:\Users\Your User Name\AppData\Roaming\Adobe\Dreamweaver CS6\[language]\Configuration
  
  Dreamweaver CS5.5: C:\Users\Your User Name\AppData\Roaming\Adobe\Dreamweaver CS5.5\[language]\Configuration
  
  Dreamweaver CS5: C:\Users\Your User Name\AppData\Roaming\Adobe\Dreamweaver CS5\[language]\Configuration
  
  Dreamweaver CS4: C:\Users\Your User Name\AppData\Roaming\Adobe\Dreamweaver CS4\[language]\Configuration
   
• Windows XP:
  
  Dreamweaver CS6: C:\Documents and Settings\Your User Name\Application Data\Adobe\Dreamweaver CS6\[language]\Configuration
  
  Dreamweaver CS5.5: C:\Documents and Settings\Your User Name\Application Data\Adobe\Dreamweaver CS5.5\[language]\Configuration
  
  Dreamweaver CS5: C:\Documents and Settings\Your User Name\Application Data\Adobe\Dreamweaver CS5\[language]\Configuration
  
  Dreamweaver CS4: C:\Documents and Settings\Your User Name\Application Data\Adobe\Dreamweaver CS4\[language]\Configuration
   

For older versions of Dreamweaver, the configuration paths are as follows:

Dreamweaver CS3 on Windows Vista:
C:\Users\[user name]\AppData\Roaming\Adobe\Dreamweaver 9\Configuration

Dreamweaver CS3 on Windows XP:
C:\Documents and Settings\[user name]\Application Data\Adobe\Dreamweaver 9\Configuration

Dreamweaver 8 on Windows XP:
C:\Documents and Settings\[user name]\Application Data\Macromedia\Dreamweaver 8\Configuration

Dreamweaver 8 on Windows Vista:
C:\Users\[user name]\AppData\Roaming\Macromedia\Dreamweaver 8\Configuration

Dreamweaver CS3 on Macintosh:
Mac HD/Users/[user]/Library/Application Support/Adobe/Dreamweaver 9/

Dreamweaver 8 on Macintosh:
Mac HD/Users/[user]/Library/Application Support/Macromedia/Dreamweaver 8/

There can be conflicting code or Dreamweaver behaviors on the page. Try to build a page from scratch with minimal behaviors and other design elements and see if you can reproduce the error. Custom code or modified Dreamweaver code can occasionally cause problems.

In particular, this step is useful for JavaScript errors related to templates, library items, and uploading files. This step is only available if the site is defined to use a site cache:

If the JavaScript only occurs in one site definition, then delete the site cache file for that site. To delete the cache, choose Site > Advanced > Recreate Site Cache.

Check for any special characters in the hard drive name, in the path to the Dreamweaver configuration folder, or in the path to your site files. Examples of special characters that can cause conflicts include the following:

~ @ # $ % ^ & * ( ) + | / \ ';

There can be a conflicting extension installed in Dreamweaver. For example, an extension could have been designed to work with an older version of Dreamweaver. Check the extension developer's website to see if the extension is compatible with your version of Dreamweaver.

There are several JavaScript errors associated with third-party extensions. Adobe recommends searching the Dreamweaver forum. Search using some of the keywords in your JavaScript error message (for example, search using the text of the JS filename).

To manually test for an extension conflict, open the Extension Manager and disable the extensions that you installed in Dreamweaver. If turning off the extensions solves the problems, then turn them back on one-by-one, until you isolate the problematic extension. If you identify a problematic extension, then notify the extension developer.

If the JavaScript error persists after you disable all of the extensions, then uninstall the extensions in the Extension Manager. If you identify a problematic extension, then notify the extension's author.

For Dreamweaver CS4, CS5, CS5.5 or CS6, see Restore preferences | Dreamweaver CS4, CS5, CS5.5, CS6.

For Dreamweaver CS3 on Windows, see "How to re-create the Dreamweaver user configuration folder (CS3 on Windows XP, Vista)" (TechNote kb401118).

On Mac OS

• To start Windows XP in diagnostic mode, see Start Windows in Diagnostic mode (Windows XP) (kb404860) for details.
• To start Windows Vista/7 in modified mode, see Restart Windows in a modified mode (Windows Vista/7) (kb404913) for details.

If the JavaScript errors persist after you follow the suggestions above, then see the following TechNotes for additional troubleshooting suggestions. Uninstalling and reinstalling Dreamweaver, with anti-virus software disabled, is an important test to perform:

• Troubleshooting Dreamweaver for Windows (tn_15481)