This release is available for Creative Cloud members and point product subscribers only. To join Adobe Creative Cloud, see Adobe Creative Cloud.
Release Date: 24 September 2012
This document lists the known issues, limitations, and workarounds in the Dreamweaver release for Creative Cloud.
Ensure that you read this document before you upgrade.
To avoid losing your personal settings and preferences in Dreamweaver CS6, ensure that you follow the instructions listed below.
Before upgrading to Creative Cloud, do the following:
After you upgrade, refer to the exported file to set the shortcuts again.
Items in the Favorites section of the Insert panel are removed after upgrade. Note down the items so that you can manually add them after upgrade.
This 12.1 upgrade includes fixes from the earlier Dreamweaver 12.0.1 patch release.
If you upgrade from Dreamweaver CS6 to Creative Cloud, your previously installed extensions do not appear in Dreamweaver menus.
To display previously installed extensions, open Adobe Extension Manager, select all extensions, and re-enable them.
The items you inserted into the Favorites section of the Insert panel in Dreamweaver CS6 are removed after upgrade. Manually reinsert items into the Favorites panel.
Live search does not work if FileVault is enabled for site local root folder.
The local root folder is inside the user folder (/Users/<user>/). Point the site local root folder outside the Users folder.
HTML keywords are no longer localized in the Property Inspector. They appear in English only.
Previewing Edge Animate compositions in the Live View slows down Dreamweaver considerably. Adobe suggests that you use browser preview for Edge Animate Compositions.
Only OAM files can be inserted into Dreamweaver. OAM files with double-byte, high-ASCII, or special characters in the filename cannot be inserted.
Preview HTML5 audio/video in a browser.
If your video plays well on your local computer but doesn’t play on a live web server, it’s probably because the remote web server isn’t configured properly for your video format.
For HTML5 video support on your websites, ensure that you correctly configure MIME (Multi-purpose Internet Mail Extensions) types on your webserver .
For choosing the correct MIME type, check the format of your videos (MP4, OGV, WEBM). Adobe recommends that you have all the formats or at least MP4 and WEBM for maximum browser compatibility. You set MIME types for each format separately.
For video encoding, you can try HTML5 Video Player. The player can convert your videos into different HTML5 video formats in a batch mode.
If you plan to host your websites on different web server types such as Windows server with IIS, or Linux server with Apache, configure HTML5 MIME types in accordance with the server type.
Add the following code to your httpd.conf file or to a .htaccess file in the directory containing your video file.
The first line is for videos in an Ogg container. The second line is for videos in an MPEG-4 container. The third is for WebM.
To set up HTML5 video MIME types on IIS servers, open IIS Manager on the Windows server. Navigate to the MIME Types settings.
There are some differences between the IIS versions. Consult your server’s documentation or your hosting company on how to set the HTML5 video MIME type for specific file types on Windows servers.
If you use IIS Express and don’t have a full instance of IIS running, use the Web.config file. This method works on any IIS7 web server, and is ignored on all non-IIS7 web servers. So, it is safe regardless of the type of application or content.
Add the following code to your configuration file:
<mimeMap FileExtension=":mp4" mimeType="video/mp4" />
<mimeMap FileExtension=".ogv" mimeType="video/ogg" />
<mimeMap FileExtension=".webmv" mimeType="video/webmv" />
If you use a web server other than Apache or IIS, consult your server’s documentation on how to set the HTML5 video MIME type for specific file types.