Troubleshooting

This is a collection of quick tips to avoid trouble.

Compile Tree - Link Tree process:

• It is critical that you do not forget to upload the ldmt.js file along with the tree.js file after you compile your tree.
• You can compile the tree anywhere you like within your site's directory structure. This decision should not be affected by the location of the pages you want to link the tree to.
• For example, if you want to link the tree into a Dreamweaver template, you are not required to compile the tree into the Templates directory. On the contrary, we do not advise you to do so as you will have to upload the Templates directory on the server too.
• In general, simply compile your tree into your root directory or into a manually-created subdirectory and you will be able to link it to any page, shared border, template or library of that web site directory structure you want.
• If you use FrontPage, the tree should not be compiled inside the _borders folder or any other special folders used by the authoring tool to manipulate common objects. The obvious reason is that these folders are not uploaded on the server when publishing the site. Instead, compile the tree in the root or in any other manually-created subdirectory.

Font selection:

For cross-platform compatibility, it is advisable to use the generic font families instead of any system-specific font. For example, if you use "Arial" and a specific platform does not have the Arial font, then the tree will use the browser's default font. But if you use "Sans Serif" instead of "Arial", the browser will use the appropriate Sans Serif font (in most cases it will be "Arial", but in platforms that do not have Arial it will be a similar font; not the default font)

Filenames:

• It is known that Netscape cannot read images that contain spaces in their filenames! Therefore, always use "my_image.gif" or "myimage.gif" instead of "my image.gif".
• Spaces in the compiled tree name are not allowed as they are not parsed properly by some browsers, such as Netscape. As an example, use "main_tree.js" or "maintree.js" instead of "main tree.js".
• Avoid using filenames that contain special characters, like quotes ("), apostrophes ('), etc. In most cases these characters will produce an error.

Note on <Javascript Command> syntax:

You may use only quotes (") or only apostrophes (') inside the text of the property but not both! Using both quotes and apostrophes will cause a javascript error.

Note on <Link> syntax:

Always use slashes instead of backslashes

(example: ../users/~user10/user10.html)