Note: These changes refer to users that have version 3.1.522 or below.
Prior to version 3.1.524 PRO (or 3.1.444 LITE), the menu-linking code was inserted at the very end of the page, right before the </BODY> tag. This was necessary for cross-browser issues with older browsers.
From version 3.1.524 (released on June 21, 2004) and above, we have optimized our code so that these cross-browser issues do not cause problems, allowing us to move the menu-linking code at the beginning of the page. In that respect, version 3.1.524 (or above) now places the menu-linking code at the very beginning of the page, right after the <BODY> tag. This results in smaller loading times for your menus, as they are one of the first elements to be loaded on page!
To enhance your sites with the new menu-linking technique, please take into account the following guidelines:
Download and install v3.1.524 or above in your machine (v3.1.444 for LITE users).
Re-compile your menu with the new AllWebMenus version and re-upload the compiled files on your server, both the compiled menu (eg: menu.js) and its associated compiled menu folder (eg: awmData-menu or awmdata).
Re-link your compiled menu to your web page(s), so that the menu-linking code moves from the end of the page to the beginning of the page, right after the <BODY> tag. To re-link your menu use the "Link menu to page" command of AllWebMenus. This action will delete the old menu-linking code from the page and will add the new one at the beginning of the page.
You can also move the menu-linking code by hand. In such a case, please make sure that you do not move the code inside table cells but only right after the <BODY> tag.
Please note that moving the menu-linking code at the beginning of the page is not required. It is just recommended so that you get your menus faster on page.
If you are using element-relative positioning (the <SPAN> technique), make sure that you update your menu-positioning code to the following one:
<span id='awmAnchor-menuname'> </span>
The major change here is the inclusion of an character inside the <span> element. You can replace the with any other content you like (an image for example), but always make sure that the <span> element is not left empty, as this may cause positioning problems with older browsers.
The optimized code used by v3.1.524 (or above) makes some "browser-specific Offsets" obsolete. You may need to delete or change these "browser-specific Offsets" and re-compile your menu so that they do not affect the proper positioning of the menu.
This concludes the guidelines for using the new AllWebMenus menu-positioning and menu-linking techniques.
We will be happy to assist you in any difficulties you may experience when implementing the changes described above. In such a case, please send us a detailed description at support@likno.com.
Thank you,
The Likno team
