Extension Manager 1.5 release notes

This document addresses known issues with the Extension Manager at the time of release. It may be updated as more information becomes available.

System requirements
What's New In This Release
Known issues
How to report bugs
Notices, Terms, Conditions, and Attribution

System Requirements
The Extension Manager requires 3 MB hard disk space and 10 MB RAM in addition to the system resources required for any product that you use in conjunction with it.

The Extension Manager works with the following products:

• Dreamweaver MX, Dreamweaver 4, and Dreamweaver UltraDev 4
• Flash MX and Flash 5
• Fireworks MX

Starting with this version (1.5), the Extension Manager does not support Dreamweaver 3 and Dreamweaver UltraDev 1.

What's New In This Release

Managing extensions on a multi-user configuration system
For extension files that are installed into Dreamweaver MX on a multi-user operating system (Windows NT, 2000, and XP, and Macintosh OS X), the Extension Manager manages and modifies files within the current user's configuration folder. On non multi-user systems, Dreamweaver files will continue to be managed and modified within the installed application configuration folder. See the Extension Manager Help for more information about installing on a multi-user operating system.

Support for new Dreamweaver MX extension types
The Extension Manager now supports the following new extension types in Dreamweaver MX:

• Code Snippet
• Code Hint
• Site
• Sample Content  
• Tag Library
• Toolbar
• Document Type
• Help Book

Backward compatibility support for Objects
Pre-existing Object extensions can be installed into Dreamweaver MX and will appear in the new Insert bar. In addition, extension developers can now explicitly update InsertBar.xml to support new extensions.

Better handling of missing tag IDs
Instead of failing while trying to install an extension that references a missing tag ID, the Extension Manager now places new items in a common place for each extension type. For example, when adding new items to the Dreamweaver menus.xml file, the default location will be Commands > Miscellaneous.

Extension files get placed in trash/recycle bin when removing an extension
When an extension gets removed/uninstalled, the Extension Manager now places the extension files in your system's trash can/recycle bin. However, on Mac OS X, files will not get placed in the trash can unless there is at least one file already in the trash can. The workaround is to leave one file in your trash can.

Known issues

Some extensions may not work in Dreamweaver MX. The version of the JavaScript API used in Dreamweaver MX has been upgraded to JavaScript API 1.5. This version of JavaScript is more strict about reporting errors on incorrect syntax than previous versions, which results in some extensions not functioning in Dreamweaver MX. For this reason, many extensions that worked in Dreamweaver 4 or UltraDev 4 may not work in Dreamweaver MX. Please inform the extension author if an extension known to work in Dreamweaver 4 or UltraDev 4 fails in Dreamweaver MX.

Installer may not find all prior versions of the Extension Manager. Earlier versions of the Extension Manager should be uninstalled before installing this new version of the Extension Manager. On Windows you can uninstall by using the Control Panel > Add/Remove Programs. On Macintosh, throw out the Extension Manager folder.

Extension Manager may not display all installed Macromedia products. If any supported version of Dreamweaver, Flash, or Fireworks does not appear in the Extension Manager's product display, try launching the Extension Manager while the "missing" product is running.

Importing large extensions or a large number of extensions may cause the Extension Manager to run out of memory on the Macintosh. To resolve this problem, increase the preferred memory size of the Extension Manager using File > Get Info and try again.

Importing extensions from Dreamweaver MX to Dreamweaver or UltraDev 4 does not work on the Macintosh. It is possible to import extensions from Dreamweaver 4 or UltraDev 4 to into Dreamweaver MX.

Extensions with very long descriptions (> 1000 bytes) cannot be installed. To resolve this issue, keep CDATA blocks in MXI files to less than 1000 characters.

The extension list columns cannot be resized on the Macintosh. If the name of the extension goes past the default column width, the user can not resize the column. The workaround is to resize the entire Extension Manager window.

Cannot install a user-defined file token into the root of the drive. Developers creating MXI files with a user-defined file token must specify a folder name for installation.

Include the required product as a dependency in the MXI file if you use a token. Extension developers using a token for a specific product must also specify that the product is required in the MXI file.

Flash MX does not support installation of Generator Objects and Generator Templates. Starting with the MX release of Flash, you will not be able to install Generator extensions into Flash. These extensions are only designed for use within Flash 5.

Reporting a bug to the Exchange team

Found a bug? Your first step should be to review the content at the Macromedia Customer Support site. There you will find informative TechNotes that can help to resolve your technical issues. If you are unable to see any information regarding a particular bug, please report it using the Macromedia Software Feature Request and Bug Report form.

Note: Due to the high volume of e-mail we receive, you may not receive a response to these submissions.

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.