Accessibility

TechNote

Dreamweaver 8 Emerging Issues

Issue

Last updated: November 6, 2006
(There are two updates to report)

Some users have reported that the following issues are affecting their usage of Dreamweaver 8. Issues described in this document may prove to be platform or system specific, and may not affect all users. Adobe Technical Support will update this document as we learn more about any of the issues, so check back periodically.

Dreamweaver 8.0.2 Updater

The Dreamweaver 8.0.2 Updater (released May 9, 2006) includes all of the fixes in the 8.0.1 update. If you havent installed the 8.0.1 update yet, then install the 8.0.2 update to get all of the fixes for both updates. All Dreamweaver users should apply this update, regardless of operating system. Download the updater and read the release notes for more information. The 8.0.2 update fixes the following three issues:

  • SQL injections in web applications - 8.0.2 updates server-side code generated by Dreamweaver to protect databases against SQL Injection. Because the server-side code is written differently in 8.0.2, it is recommended to backup your original files before converting the server-side code with 8.0.2, in case the new code is incompatible with your web application. If you are using third-party server behavior-related extensions, it is recommended to ask the extension developers if their extensions are compatible with Dreamweaver 8.0.2.
  • Active content - The 8.0.2 update fixes a problem with the code generated by Dreamweaver when it inserts active content such as a Flash file in a web page. In the latest versions of Internet Explorer, the generated code by Dreamweaver does not allow users to interact with the active content unless they click it. The update fixes the code generated by Dreamweaver so that users dont have to click the active content. The update also provides a way to repair the code of existing pages with active content. When using 8.0.2 for active content pages, make sure to upload the Scripts folder to the server after creating your pages.
  • Lost FTP logins - The 8.0.2 update fixes a problem of FTP usernames and passwords in Dreamweaver site definitions being deleted when you close and re-open Dreamweaver 8 or when you reboot your machine. This problem is the result of a change introduced in Internet Explorer 7.

If you have identified an issue that is not listed here, then please do the following:

  • Search the Dreamweaver Support Knowledge Base to see if the issue is covered in a separate TechNote.
  • Contact Adobe Product Support. Issues confirmed as bugs are not counted against complimentary or paid support incidents.
  • Report the issue on the Feature Request / Bug Report form.
    • Also use this form for Dreamweaver feature requests.
    • Submissions from this form go straight to the Dreamweaver Engineering team.
    • Not all submissions receive replies, but all submissions are reviewed. See the form for further information.

Note:Known issues (no longer emerging) can be found in the bottom section of this document.

Emerging Issues
Known Issues
Emerging Issues

Technical support will update this document as we learn more about any of the following issues.

Dreamweaver 8 for Windows loses FTP login settings after installing Internet Explorer 7
topic update: November 6, 2006

Some Windows users are reporting that after installing Internet Explorer 7, their FTP usernames and passwords in their Dreamweaver site definitions are deleted when they close and re-open Dreamweaver 8 or when they reboot their machine. This issue does not occur in earlier versions of Dreamweaver. Installing Dreamweaver 8.0.2 should resolve this problem for most users. For more details, please see Dreamweaver 8 for Windows loses FTP login settings (TechNote 3491671c). (Ref. 205051, 210466)

PHP/MySQL issues with Dreamweaver 8.0.2 Updater
topic update: November 6, 2006

Some Dreamweaver 8.0.2 issues have been reported specific to the PHP/MySQL server model. Adobe has created a Dreamweaver extension fix for both Windows and Macintosh that resolves these issues. You should only install the extension fix if you are using the PHP/MySQL server model and experiencing one of the specific issues listed in the following TechNote: PHP/MySQL issues with Dreamweaver 8.0.2 Updater (TechNote b6c2ae2a). (Ref. 207218, 207225, 207462, 208374)

Active content not displayed in browser after converting page in Dreamweaver 8.0.2
topic update: June 26, 2006

In Dreamweaver 8.0.2, after creating a new page with active content (for example, Flash Player content) or after converting an existing page with active content, the active content does not display when the page is uploaded to the server and viewed in a web browser. Most users are able to solve this problem by uploading the Scripts folder automatically created by Dreamweaver up to the server. For more details, please see Active content not displayed in browser after converting page in Dreamweaver 8.0.2 (TechNote 9c3f9367). (Ref. 207277)

Document relative paths to locked Flash objects incorrect in child pages after converting template for active content
topic update: June 26, 2006

If you have a template that has active content (for example Flash Player content) in a locked region, and you convert the template for active content in Dreamweaver 8.0.2, the path to the active content is incorrect in the child pages of the template. For more details, please see Document relative paths to locked Flash objects incorrect in child pages after converting template for active content (TechNote c65e8513). (Ref. 207250)

QuickTime objects do not display in Internet Explorer after converting page in Dreamweaver 8.0.2
topic update: June 26, 2006

When converting a page for active content in Dreamweaver 8.0.2, QuickTime movies aren't displayed when viewed in Internet Explorer. Instead, a QuickTime place holder appears. QuickTime movies are displayed correctly in other browsers. For more details, please seeQuickTime objects not displayed in Internet Explorer after converting page in Dreamweaver 8.0.2 (TechNote df8a0f1d). (Ref. 207348)

Can't install Dreamweaver 8 updaters after canceling updater installer (Windows only)
topic update: May 10, 2006

If you press cancel during the Dreamweaver 8.0.2 (or 8.0.1) for Windows installation process, Dreamweaver will not be able to update to 8.0.2 in the future. To update to 8.0.2 in the future, you will have to uninstall and re-install Dreamweaver. For more details, please see Can't install Dreamweaver 8 updaters for Windows after canceling updater installer (TechNote 785362aa). (Ref. 203720)

Dreamweaver 8.0.2 Updater prompts you for CD during installation (Windows only)
topic update: May 10, 2006

If you installed Dreamweaver 8 for Windows from a CD, you will be prompted to insert the CD when running the 8.0.2 updater. If you no longer have the CD, there is a workaround described in the Dreamweaver 8 Release Notes. (Ref. 206055)

Extensions related to server behaviors may not function as expected after installing Dreamweaver 8.0.2 Updater
topic update: May 10, 2006

In Dreamweaver 8.0.2, the server-side code generated by Dreamweaver has been updated to protect databases against SQL Injection. Because several of the server behaviors have been updated, extensions that leverage some of the same functionality may not function as expected. The Dreamweaver team is helping extension developers update their extensions so they are compatible with the 8.0.2 Updater. (Ref. 207279)

Known Issues

The following issues have been removed from the emerging issues list because the issue is resolved or has been moved to its own TechNote. When appropriate, the TechNote link will be included with the issue.

Dreamweaver 8 does not launch
topic update: January 16, 2006

Some users are reporting that Dreamweaver 8 does not launch. The common characteristic is that the splash screen appears momentarily, then the application closes. Some users report being able to launch Dreamweaver 8 two or three times before experiencing the problem, while some users were never able to launch Dreamweaver 8. For more details, please see Dreamweaver 8 does not launch (TechNote fb181c10). (Ref. 201530)

Help viewer does not show content (Macintosh only)
topic update: October 13, 2005

When attempting to view Help within Dreamweaver (Help > Dreamweaver Help), the viewer content is empty. There are two possible reasons for this: (1) the alias to the Help files did not get created correctly or is pointing to the wrong location; or (2) the Help cache may be corrupted. For more details, please see Help viewer does not show content on Macintosh (TechNote 133bc2a3). (Ref. 198631)

Dreamweaver is unresponsive when expanding the Files panel or viewing the Assets panel (Macintosh only)
topic update: January 16, 2006
Issue

After clicking the Expand icon in the Files panel, or attempting to view the Assets panel, Dreamweaver appears unresponsive. This can also occur when opening a folder with a large number of files (1000+). The wait time is related to the number of files in the site or folder. (Ref. 200312)

Solution

The Dreamweaver 8.0.1 Updater resolved this issue. Install theDreamweaver 8.0.2 Updater as it includes all of the fixes in the 8.0.1 update, plus additional recommended fixes.

If the Dreamweaver 8.0.2 Updater doesn't solve the problem, an alternative workaround is to place the Assets panel in its own panel group. Panel docking is covered in Dreamweaver Help. The most efficient approach for moving the Assets panel is as follows:

  1. Create a new site in Dreamweaver with the Local Info pointing to an empty folder.
  2. Move the Assets panel to its own group as directed in Help with the new site selected.
  3. Close the new Assets panel group.
  4. Quit and restart Dreamweaver.

Moving the Assets panel with a new, empty site selected will avoid the delay associated with selecting the Assets panel in a large site.

Time stamps are not correctly updated on remote/testing server
topic update: January 16, 2006

When connecting to the Remote or Testing server via Local/Network, Dreamweaver does not update the remote file's time stamp. The Dreamweaver 8.0.2 Updater resolves this issue. For more details, please seeTime stamps are not correctly updated on remote/testing server (TechNote 136227ec). (Ref. 201278)

Recent updates to ColdFusion pages do not show in browser
topic update: January 16, 2006

When viewing a ColdFusion page in a browser, the page does not reflect recent changes made. The Dreamweaver 8.0.2 Updater resolves this issue. For more details, please seeRecent updates to ColdFusion pages do not show in browser (TechNote 135f2158). (Ref. 199111)

Pages with absolute links (for example, a link such as http://www.mysite.com/image1.jpg) take a long time to render in Design view. Dreamweaver may appear to be not responding. After several minutes, the page may render as expected, or Design view may be blank while Code view functions as expected. This applies to any absolute link in the page, whether they are images, external CSS files, or other files. An alert may also display after a period of time reporting "No Error Occurred". (Ref. 199708) The Dreamweaver 8.0.1 Updater resolved this issue. Install the Dreamweaver 8.0.2 Updater as it includes all of the fixes in the 8.0.1 update, plus additional recommended fixes.. See the following TechNote for more information: Problems with pages containing absolute links (TechNote 54d76ef).

In certain situations, paths to files in templates are unexpectedly rewritten.
topic update: January 16, 2006

This issue has been reported in both regular and nested templates. The following code:

<!--#include -->

is rewritten to:

<!--#include -->

The Dreamweaver 8.0.1 Updater resolved this issue. Install theDreamweaver 8.0.2 Updater because it includes all of the fixes in the 8.0.1 update, plus additional recommended fixes. See the following TechNote for more information: Relative paths pointing to items located in the Templates folders are rewritten in new pages created from templates (TechNote 52195a7). (Ref. 192209)

Issue

When a site's local folder is not stored on the local machine, Dreamweaver 8 may not define the correct path in site-root relative links.

  • Images and other inserted objects display as placeholders
  • SSI files may render correctly in Design View, but attempting to edit the file results in an invalid path error.

These issues have been reported using UNC and DFS paths to access the site's local folder. (Ref. 200915)

Solution

Either use document relative links, store the site's local folder on the local machine, or connect to the site's local folder using a mapped drive.

Edit in Fireworks launches Fireworks MX 2004 instead of Fireworks 8
topic update: September 16, 2005
Issue

After selecting an image and clicking on the Fireworks icon in the Properties panel to edit the image in Fireworks, Fireworks MX 2004 (or other previously installed version) launches instead of Fireworks 8. (Ref. 196137)

Solution

In the Preference for File Types/Editors (Edit menu > Preferences > File Types/Editors), perform the following steps:

  • Remove any Editors for file types that are associated with Fireworks (.png, .gif, .jpg) by selecting the editor and pressing the minus button.
  • Add back an editor pointing to the Fireworks 8 executable (Fireworks.exe). Fireworks.exe is located in Program Files > Macromedia > Fireworks 8, unless installed to a non-default location.
Unable to install Studio products on Windows 2000
topic update: September 12, 2005

This issue is documented in Unable to install Studio products on Windows 2000 (TechNote 9554c475).

Issue

In some Windows 2000 environments, attempting to install any Studio product generates the following warning message:

"The package requires a newer version of the Windows Installer. Do you want to update the version of the Windows Installer in your system?"

Subsequently attempting to update the Installer fails.

Reason

The MSI technology used in Studio products requires the Installer engine version 3.0. In order to update the Installer, Windows 2000 customers must have installed Windows 2000 Service Pack 3 or above.

Solution

Perform Windows Update on the Windows 2000 system (in Internet Explorer choose Tools > Windows Update). Be sure that Service Pack 3 or above is installed as part of the Windows Update process. (Ref. 200065)

Dealing with duplicate site definitions when upgrading to Dreamweaver 8
topic update: September 12, 2005

While not an issue with Dreamweaver 8, important information is available for those upgrading from a previous version of Dreamweaver who encountered the duplicate site definition issue.

Please review Dealing with duplicate site definitions when upgrading to Dreamweaver 8 (TechNote a354d1b1) for further information.

Corruption errors when installing downloaded Dreamweaver 8
topic update: September 14, 2005
Issue

You receive the following error message after downloading Dreamweaver 8:

"The contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again."

Solution

Information in the Download Help ServiceNote (ServiceNote tn_15296) should help you identify the problem and provide a solution.

If the ServiceNote does not help resolve the issue, then pleasecontact Customer Service.

Customers who ordered Studio 8 as a download are reporting some downloads missing
topic update: September 14, 2005
Issue

Customers who ordered Studio 8 as a download are reporting some downloads missing.

Solution

Studio 8 consists of 8 downloads, and there are two pages for this in the customer's membership download section. Use the arrow at the top of the first download page to move to the second page.

AlertThis content requires Flash

To view this content, JavaScript must be enabled, and you need the latest version of the Adobe Flash Player.

Download the free Flash Player now!

Get Adobe Flash Player

Creative Commons License

Search Support

Document Details

ID:a3f38dcf
OS:Windows (All)
Mac OS (All)

Products Affected:

dreamweaver