You can customize Dreamweaver in a multiuser operating system such as Microsoft® Windows® XP, Windows Vista, or Mac OS® X. Dreamweaver prevents the customized configuration of any user from affecting the configurations of other users. The first time you run Dreamweaver in a multiuser operating system, Dreamweaver copies configuration files into a user Configuration folder. When you customize Dreamweaver by using dialog boxes and panels, the application modifies your user Configuration files instead of modifying the Dreamweaver Configuration files. To customize Dreamweaver in a multiuser environment, edit the appropriate user Configuration file, rather than the Dreamweaver Configuration files. To make changes that affect most users, edit a Dreamweaver Configuration file. However, users who already have corresponding user Configuration files do not see the change. To make changes that affect all users, create an extension and install it using the Extension Manager.

Note:

In older multiuser operating systems (Windows 98, Windows ME, and Mac OS 9.x), all users share a single set of Dreamweaver Configuration files.

The location of the Configuration folder of the user depends on the platform of the user.

Windows XP platforms use the following location:

hard disk:\Documents and Settings\username\Application Data\Adobe\Dreamweaver CS5\Configuration

Note:

It is possible that this folder is inside a hidden folder.

Windows Vista platforms use the following location:

hard disk:\Users\username\AppData\Roaming\Adobe\Dreamweaver CS5\Configuration

Mac OS X platforms use the following location:

hard disk:\Users/username/Library/Application Support/Adobe/Dreamweaver CS5/Configuration

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.

Example

 <deleteditems> 
<!-- item tags here --> 
</deleteditems>

Description

Specifies a configuration file that Dreamweaver should ignore.

Attributes

name

The name attribute specifies the path to the configuration file, relative to the Configuration folder. In Windows, use a backslash (\) to separate parts of the path; on the Macintosh®, use a colon (:).

Contents

None (empty tag).

Container

This tag must be contained in a deleteditems tag.

Example

 <item name="snippets\headers\5columnwith4links.csn" />

Reinstalling and uninstalling Dreamweaver in a multiuser environment

After you install Dreamweaver, if you later reinstall it or upgrade to a later version, Dreamweaver automatically makes backup copies of existing user configuration files, so that if you’ve customized those files, you can still access the changes you made. When you uninstall Dreamweaver from a multiuser system (which you can do only if you have administrative privileges), Dreamweaver can remove each user Configuration folder for you.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy