Troubleshooting

Top Previous Next

This is a collection of quick tips to avoid trouble.

Compile Menu - Link Menu process:

·	It is critical that you do not forget to upload the awmmenupath.gif and the awmData-*menuname* directory along with the **menuname.js** file after you compile your menu.

·	You can compile the menu 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 menu to.

For example, if you want to link the menu into a Dreamweaver template, you are not required to compile the menu 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 menu 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 menu 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 menu 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 menu 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".

·	Since version 1.3.356, spaces in the compiled menu name are not allowed as they are not parsed properly by some browsers, such as Netscape. As an example, use "main_menu.js" or "mainmenu.js" instead of "main menu.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 <URL> syntax:
Always use slashes instead of backslashes
(example: ../users/~user10/user10.html )

Menu above Flash or other objects:
The <Z-Index> property will not work for some objects, such as the Flash Object.
To make the menu appear above these objects you need to do the following:

1. Go to the <object> tag

2. Add the following code into the tag:

The above solution does not apply for the SELECT element as it always gets the highest priority by the browser. Therefore, avoid placing this element close to the area where the menu expands.

Netscape 4.x limitation:
Netscape 4.x cannot show a tooltip when the <Item Cursor> is set to "default" value. It only shows a tooltip when the <Item Cursor> is set to "hand" (or to any other cursor, as it will be automatically displayed as "hand" due to another Netscape 4.x limitation on displaying cursors other than the "default" or the "hand" ones).

Frame Show is the ideal software for desktop enhancement, desktop wallpaper and digital photo frame solutions.

Frame Show: Frame images, pictures, photos with the most innovative framing software!