Upgrading from v2.2.6

If you're upgrading from v2.2.6 you'll have to go through the changes mentioned in this document. You do not need to read the upgrade notes for v2.3.0 as all things mentioned there are also mentioned here.

User-configurable options

In version 2.3.2 all user-configurable options have default values. Therefore you might not have to set each specifically. For a list of all the options and their corresponding default values see the Installation Guide under List of default values. All options mentioned below link to their corresponding document in the Install Guide.

The following user-configurable options have changed values in v2.3.2:

MTMSubsGetPlus
Has gone from a true/false-value to a string and therefore it must be changed. New default value is "submenu" which corresponds to a previous value of false.

The following options are new from v2.2.6 to v2.3.2 (some were introduced in v2.3.0 or v2.3.1, but that's not relevant):

Menu creation changes

There has been substantial changes to the menu creation code, but backwards compatibility has been kept. Therefore you do not need to change your existing menu code when upgrading. Should you wish to use the new code structure for your menus you'll find it described in the Install Guide under Making the menu.

Two of the methods used in the menu structure code have changes to their arguments. Specifically they are:

MTMItem()
The 4th argument is now the tool tip text and the 5th argument is the item's icon.
MTMakeSubmenu()
Takes up to 4 arguments, the additional three are expansion state, and icons for closed and open sub menu respectively.

Please note that in v2.3.2 the usage of new MTMItem() is no longer necessary, the method addItem() takes the arguments directly, and that usage of menu.items[x].MTMakeSubmenu() is discouraged in favour of the more flexible menu.makeLastSubmenu(). This is of course also mentioned in the Install Guide.

Tracking code

The tracking code has been changed to work with Netscape 6 and Opera 5/6. To ease maintenance the tracking code has been moved to the file mtmtrack.js. If you use a code frame name other than "code" you will need to change the option in that file too since it points to the right frame name. See the Install Guide's section Tracking code if you're unsure about how to reference the mtmtrack.js file.

HTML changes

Two files have changes that you should look into. In menu_empty.html (or any other document you have present in the menu frame) there has to be a style sheet present in the document head for Mozilla/Netscape 6 to work correctly. The element should look like this:

<style type="text/css" id="mtmsheet">
/* this is only a Mozilla quirk fix */
</style>

In code.html there are two changes. First of all the framebuster script is inserted to fix the problem with IE bookmarking code.html instead of the parent frameset. You can copy and paste the small script code over from the code.html found in the example-site directory. Lastly the call to MTMStartMenu() has changed, it's now like this:

onload="MTMStartMenu(true);"