Adobe Extending Dreamweaver CS4 - Manual (Page 17)

11 EXTENDING DREAMWEAVER CS4
Customizing Dreamweaver
Note: To install extensions that all users can use in a multiuser operating system, you must be logged in as Administrator
(Windows) or root (Mac OS X).
The first time you run Dreamweaver, it copies only some of the configuration files into your user Configuration folder.
(The files that it copies are specified in the version.xml file in the Configuration folder.) When you customize
Dreamweaver from within the application, Dreamweaver copies the configuration files into your user Configuration
folder. For example, Dreamweaver copies the files when you modify one of the predesigned code snippets in the
Snippets panel. The version of a file in your user Configuration folder always takes precedence over the version in the
Dreamweaver Configuration folder. To customize a configuration file, it must be present in the user Configuration
folder. If Dreamweaver has not copied the file already, copy and edit the file in the user Configuration folder.
Deleting configuration files in a multiuser environment
When working in a multiuser operating system, if you do something within Dreamweaver that would delete a
configuration file (for example, deleting a predesigned snippet from the Snippets panel), Dreamweaver creates a file
in your user Configuration folder called mm_deleted_files.xml. When a file is listed in mm_deleted_files.xml,
Dreamweaver behaves as if that file doesn’t exist.
Deactivate a configuration file
1 Quit Dreamweaver.
2 Using a text editor, edit mm_deleted_files.xml in your user Configuration folder; add an item tag to that file, giving
the path (relative to the Dreamweaver Configuration folder) of the configuration file to deactivate.
Note: Do not edit mm_deleted_files.xml in Dreamweaver.
3 Save and close mm_deleted_files.xml.
4 Start Dreamweaver again.
The mm_deleted_files.xml tag syntax
The mm_deleted_files.xml file contains a structured list of items that specify configuration files that Dreamweaver is
to ignore. These items are specified by XML tags, which you can edit in a text editor.
In the syntax descriptions of the mm_deleted_files.xml tags that follow, optional attributes are marked in the attribute
lists with curly braces (
{} ); all attributes not marked with curly braces are required.
Description
Container tag that holds a list of items that Dreamweaver should treat as deleted.
Attributes
None.
Contents
This tag must contain one or more
item tags.
Container
None.