Macromedia Dreamweaver MX - Release Notes

About Dreamweaver MX
What's New In Dreamweaver MX
System Requirements
Helpful Information and Known Issues
General
Cross-Product Integration
Macintosh Specific
Windows Specific
ColdFusion
ASP.Net
PHP
JSP
Notices, Terms, Conditions, and Attribution

About Dreamweaver MX

Macromedia Dreamweaver MX is an easy, powerful, and open authoring tool that every member of the development team can use to quickly build robust websites and Internet applications. Work within one environment to easily create and manage any professional website, whether it's built using HTML, XHTML, XML, web services, ColdFusion, ASP.NET, ASP, JSP, or PHP. Dreamweaver MX combines the renowned visual layout tools of Dreamweaver, the rapid web application development features of Dreamweaver UltraDev, and the extensive code editing support of HomeSite.

What's New In Dreamweaver MX

Get a quick overview of what is new in Macromedia Dreamweaver MX by reviewing the Top 10 Features in Dreamweaver MX. For a listing of new and enhanced features, take the interactive feature tour. For detailed information about this release, read the Dreamweaver MX Product Overview.

Check out the in-product tutorials and the many resources available for learning about Dreamweaver MX at the Dreamweaver Designer & Developer Center. Find inspiration with tips, articles, tutorials, and resources, or steer your project to success with forums, code examples, exchanges, and reference materials for the taking.

System Requirements

Helpful Information and Known Issues

The following lists known issues with Dreamweaver MX at the time of release. To learn the latest news on tips or known issues, please visit the Dreamweaver Support Center.

General
Helpful Information and Known Issues

Tabbed panels within panel groups have changed slightly in appearance and functionality, although your interface is still customizable. Tabbed panels that can be rearranged now offset like pages of a book as you switch between tabs. These changes were made to comply with U.S. court decisions. Panels can be moved between panel groups by choosing Group Panel With from the Options menu in the title bar of each expanded panel. In Dreamweaver MX and Fireworks MX you can also change panel groupings using a context menu: Right-click (Windows) or Control-click (Macintosh) the panel group’s title bar to view the context menu. When you attempt to drag a tab, an alert dialog reminds you to use the context menu or panel Options menu to move tabbed panels between panel groups.

There are known issues using Dreamweaver MX on a system that has Zone Labs ZoneAlarm. If you experience any problems, configure ZoneAlarm to allow Dreamweaver MX to act as a server and connect to the internet. If problems still persist, consult the Dreameaver Support Center for additional information.

Secure FTP login integrates with MacSSH and PuTTY for Windows to allow for SSH enabled secure transfer of login information from the integrated Dreamweaver FTP client. For detailed instructions on creating an SSH tunnel for secure authentication, see the following technotes:
16143 (Macintosh)
16126 (Windows)

There are many new Dreamweaver MX Template features and new template code to accompany them. Because of the changes from prior versions of Dreamweaver, you should note the following:

• If you create a new template in Dreamweaver MX, it will not work in Dreamweaver 4 or UltraDev 4. You will not be able to create instances of that template, or apply it to an existing page, in Dreamweaver 4/UltraDev 4.
• If you add a new editable region to a Dreamweaver 4/UltraDev 4 template in Dreamweaver MX, that template will still work in Dreamweaver 4/UltraDev 4, but the new editable region won't be recognized and will be rendered as an html comment.
• If you add a new editable region to a Dreamweaver 4/UltraDev 4 template and update existing pages based on it in Dreamweaver MX, the template-based pages will still work in Dreamweaver 4/UltraDev 4. However, if you create new instances of that template in Dreamweaver MX, the new instances won't work in Dreamweaver 4/UltraDev4.
• If you use any of the new Dreamweaver MX features in a template (repeated regions, optional content, and so on), that template will not work in Dreamweaver 4/UltraDev 4.
• Otherwise, you can freely exchange templates and template-based pages created in Dreamweaver 4/UltraDev 4 between use in Dreamweaver 4/UltraDev 4 and Dreamweaver MX. Editing a Dreamweaver 4/UltraDev 4 template in Dreamweaver MX will not render the template unusable in Dreamweaver 4/UltraDev 4 unless you add an editable region or use one of the new template features.
• Be sure to save a backup version of any template created with a prior version of Dreamweaver before editing it in Dreamweaver MX in case you need to revert to the original file.

In the online Help, the code samples provided in 'Writing a template expression' and 'Creating a Multiple If condition' contain a typographical error. To use the template code samples to create your own template expressions, remove the space before and after the equals sign (=) to correct the code.

For example, the correct template expression code is:

<!-- TemplateExpr expr='your expression' -->

Empty cells that were drawn using Layout View in Dreamweaver 4 will not appear when the page is opened in Layout View in Dreamweaver MX. The workaround is to redraw the cell in Layout View in Dreamweaver MX. Only empty Layout cells are affected by this problem.

Cross-Product Integration
Helpful Information and Known Issues

Dreamweaver MX includes the recently released Flash MX plug-in (r29) in the configuration folder. This means that movies made with Flash MX will play in the Dreamweaver document window. If a new version of the Flash plug-in becomes available, you can update it in Dreamweaver MX in the folder Dreamweaver MXConfigurationFlash Player.

Macintosh Specific
Helpful Information and Known Issues

On some systems, upon the first launch of the Dreamweaver MX Trial, you may get the following error message:

Privilege: Failed to initialize
Privilege (87) for: drmet. Please re-install the product and try again.

To fix this, double-click on the VSetupT file, which is located in the Dreamweaver MX folder, and then re-launch Dreamweaver MX. Double-clicking VSetupT will not display anything, but it will initialize the setup so that Dreamweaver MX can be launched. This only needs to be done once.

Using Preview in Browser to view an XHTML document on a Macintosh with Internet Explorer 5 fails. To resolve this issue, use Internet Explorer 5.1 or later.

Mac OS 9.1 & 9.2 users must have CarbonLib 1.5 installed. Dreamweaver MX is a Carbon-based application and requires CarbonLib 1.5 if you are running on Mac OS 9. The Dreamweaver MX installer will install CarbonLib 1.5. The CarbonLib 1.5 installer may also be downloaded from Apple at: http://docs.info.apple.com/article.html?artnum=120047.

Cannot apply CSS styles in Code view in a ColdFusion document. To resolve this issue, click in Design view after making edits to trigger synchronization between Code view and Design view. Then switch back to Code view and apply the CSS style.

Panels and windows are black when Display is set to 256 Colors on Macintosh OS X. Dreamweaver MX requires Display to be set to Thousands of Colors or better on Macintosh OS X.

Windows Specific
Helpful Information and Known Issues

Dreamweaver MX won't launch on Windows NT and the following error message appears: The Dynamic Link Library SHLWAPI.dll could not be found in the specified path. To correct this problem, install Microsoft Internet Explorer 5.1 or later.

ColdFusion debugging may not be compatible with some versions of browsers. Microsoft Internet Explorer version 5.50.4807.2300 is known to be incompatible with the ColdFusion debugger.

During installation on Windows 98 systems with F-Secure (virus-detection software) running, an error message appears warning of a possible virus for the file codee33e.rra. To resolve this issue, apply hotfix 3 for FSAV 5.30, then install Dreamweaver MX. The hotfix is available at:
http://www.europe.f-secure.com/support/top-issues/avwrks-top-issues-page_2002011000.shtml.

ColdFusion
Helpful Information and Known Issues

Easy ColdFusion MX setup will work only if you have a ColdFusion server and choose the Edit and Test Locally option in the Site Setup Wizard. If you choose any of the other options, you will not be able to take advantage of the Easy ColdFusion MX setup functionality.
If you have ColdFusion MX installed and select the Edit Locally, Then Upload to Remote Testing Server option in Site Setup, Dreamweaver MX will prepopulate your testing server with c:CFusionMXwwwrootfolder, and will populate your URL prefix to http://localhost. If you are running standalone ColdFusion MX, you can edit your URL prefix with the appropriate port number. Otherwise, replace the testing server path with the actual path of your testing server.

Dreamweaver MX will not correctly populate the URL Prefix in the Site Wizard if you have both ColdFusion MX and another server on your machine. The site wizard will recognize ColdFusion servers running on your machine; if you choose to use the local ColdFusion servers, the site wizard will create the details of your site, including application server path and URL prefix. If you have a standalone version of ColdFusion MX installed, and choose to use another server on your machine (for example, IIS) Dreamweaver MX will not populate the URL prefix correctly. It will append your local root folder path to the end the ColdFusion MX URL prefix. For example, if you have a local root of 'c:inetpubwwwrootfolder' and you choose to use a server on your system other than the standalone ColdFusion MX server, the URL prefix will be 'http://localhost:8100/inetpub/wwwroot/folder'. To correct this problem, replace the supplied URL prefix with an accurate one.

To use the ColdFusion debugger, you must have Microsoft Internet Explorer 5.1 or later on your system.

ColdFusion server behavior code has been changed for Dreamweaver MX. Dreamweaver MX offers new and improved server behaviors. Because the code is different, these new server behaviors cannot coexist on the same page as those created in UltraDev 4. Each file must contain only Dreamweaver MX ColdFusion server behaviors or UltraDev 4 server behaviors. You can specify whether your site will contain Dreamweaver MX pages, UltraDev 4 pages, or both, in the Site Definition Dialog box. If Both is selected, you will be prompted to decide which type of server behaviors should be used upon creating each new page.

RDS File Browsing does not support high-ASCII or double-byte character sets. RDS File Browsing will only work with low-ASCII character sets.

ColdFusion does not recognize column heading names that contain a space character in Microsoft Access databases. To resolve this problem, make sure that column heading names in Microsoft Access databases do not contain any space characters.

ASP.Net
Helpful Information and Known Issues

When using a SQL Server connection, SQL statements are parameterized with named placeholders, not question marks, as would be the case when using OLE DB connections. For example:

SQL Server: SELECT * FROM foo WHERE xyz=@myParam
OLE DB: SELECT * FROM foo WHERE xyz=?

Connection strings and other information about connections persist in the web.config file in the root of the Dreamweaver site.

When creating or modifying the Add Key tags in web.config (used to define a connection) be sure to maintain the same order of the keys that Dreamweaver uses. The order should be:

<add key='MM_CONNECTION_HANDLER_foo' value='default_oledb.htm or sqlserver.htm' />
<add key='MM_CONNECTION_STRING_foo' value='the connection string ' />
<add key='MM_CONNECTION_DATABASETYPE_foo' value='OleDb or SQLServer' />
<add key='MM_CONNECTION_SCHEMA_foo' value='empty string or a schema name' />
<add key='MM_CONNECTION_CATALOG_foo' value='empty string or catalog name' />

To use server behaviors in ASP.NET, you must copy a Macromedia custom tag file to the bin directory on your testing server. You can copy the file by clicking the deploy link displayed in the Server Behaviors panel or the Bindings panel. You can also select Site > Deploy Supporting Files. A dialog box appears that lets you designate the transfer method and location of the testing server's bin directory. Enter the local/network or FTP path to the server's bin directory (for example, c:Inetpubwwwrootbin), then click the Deploy button to deploy the file in the designated directory. Note that the dialog box won't create the bin directory for you; you must create the folder before deploying the file.

Dreamweaver does not automatically deploy the web.config file or auto-merge its connection data into the web.config file on the testing server or the remote server. This file may have to be Put (copied) to the server manually in order to run ASP.NET pages that use connections. This is not a problem when using Preview In Browser or Live Data mode. It is only an issue when running that actual page on the server.
To use the Dreamweaver MX custom tags in your own ASP.NET code, you must include the following directive at the top of each .aspx page that uses the tags:

<%@ Register TagPrefix='MM' Namespace='DreamweaverCtrls' Assembly='DreamweaverCtrls,version=1.0.0.0,publicKeyToken=836f606ede05d46a, culture=neutral' %>

The directive might already be included on the page if the page contains a Dreamweaver server behavior. When you add server behaviors to ASP.NET pages, Dreamweaver automatically includes the Register directive when needed.

Next, copy the file called DreamweaverCtrls.dll to the bin folder of your site, or to the bin folder beneath any virtual directory that uses its own application space. You can also place the DLL in the Global Assembly Cache (GAC). For more information on the GAC, see the Microsoft website at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmag01/html/buildapps2.asp. The DLL file, which contains the logic for the custom tags, is located in the following folder in the Dreamweaver MX folder on your hard disk:

Dreamweaver MX/Configuration/ServerBehaviors/Shared/ASP.Net/Scripts/DreamweaverCtrls.dll

If you added server behaviors to other ASP.NET pages in your site, the file may already be in the bin folder.

The dynamic menu and dynamic radio buttons generated by the Update Server object incorrectly append a semicolon. A compiler error 'Compiler Error Message: BC30037: Character is not valid.' results. Remove the semicolon at the end of the line to correct this error. This only happens on ASP.Net VB pages that use web form controls. Normal HTML form objects won't encounter the problem.

If you specify SQL reserved words for column names when adding recordsets or server behaviors to your page, Dreamweaver adds quotes around the reserved words in the SQL statement to ensure the code doesn't break. However, if you're using a Microsoft Access database, the quotes can cause the code to break at runtime. To avoid this problem, make sure you don't use SQL reserved words for your column names. For a list of reserved words, see the Microsoft website (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndao/html/daotoadoupdate_topic16.asp).

PHP
Helpful Information and Known Issues

Dreamweaver MX is not compatible with PHP version 4.1.0 dueto a bug in mysql_pconnect(). You can use PHP 4.0.6 and earlier, or PHP 4.1.1 and later.

In PHP applications, Dreamweaver adds quotes around column names that match SQL reserved words. However, these quotes are not correctly escaped, which results in a compilation error. To correct the code, place a backslash () before all quotes within the SQL statement, or avoid using column names that match SQL reserved words. SQL reserved words include: catalog, data, date, day, default, desc, group, hour, identity, level, names, parameter, path, prefix, result, statement, time, value, values, year.

The online Help for the PHP document type's Add Parameter dialog box is incomplete. The Add Parameter dialog box lets you define parameters contained in a SQL statement by entering the parameter’s name default value and runtime value. To define a SQL parameter for a PHP document type:

1. Enter a parameter name in the Name text box.
2. Enter a default value for the parameter in the Default Parameter text box. The default value is the value the parameter should use if no runtime value is returned.
3. Enter a runtime value for a parameter in the Runtime Value text box. The runtime value is usually a URL or form parameter entered by a user in an HTML form field.
4. Click OK.

JSP
Helpful Information and Known Issues

The online Help describes introspecting a web service proxy using the .NET framework. The same dialog box and procedure applies to JSP document types as well.

To select a proxy class reader for a JSP page:

1. Click the plus (+) button in the Components panel.
2. Select Add Using Proxy Class from the pop-up menu. The Add Using Proxy class dialog box appears.
3. Enter the location of the folder containing the proxy class files in the text box. You can browse for the folder by clicking the Browse button to the right of the text box.
4. Select the proxy reader you want to use from the pop-up menu. The default proxy reader for JSP document types is the Java Class Reader.
5. Click OK.

Notices, Terms, Conditions, and Attribution

This software may contain third-party software which requires notices and/or additional terms and conditions. Such required third-party software notices and/or additional terms and conditions are made a part of and incorporated by reference into the End User License Agreement (EULA) covering this software.