TOPIC:

The new Menu Position feature for Custom Web Pages is intended to allow you to *optionally* change the position of Custom Web Pages and Links in the left side menus.

The "*optionally*" part is the key word here. The menu ordering needs to work regardless of whether you set a Menu Position # or not for Custom Web Pages. The positioning is all done with a three level sort based on whether or not you have set a Menu Position # or not, the Menu Position # if you did set it, and finally the alphabetical order of the items based on the page/link title.

Here's an example to illustrate how this works:

Menu Position set?(Y/N)	Menu Position #	Web Page/Link Title
Y	20	Schedule
Y	30	Member Bios
N	0 (default if not set)	Fun Times Photos

For the above case, the Custom Web Pages would be listed in the menu in the above order. Here is why...

1. All Custom Web Pages that have a Menu Position # set, are listed first. The presumption is that if you set this, then it is likely you want to move the associated item higher in the menu ordering. Thus, by default, all *new* Custom Web Pages/Links that you do not explicitly set a Menu Position # for get listed alphabetically at the *bottom* of the appropriate left side menu.
    
2. Menu Position #'s do not actually have to be a strict sequence of numbers. The sequence can start with any postive whole number and there can actually be gaps in the sequence. All that really matters is where they end up via an ascending sort. In fact, it is actually a good idea to leave gaps in the sequence, to make it easy later on for you to move items around in the menu. (I use 10, 20, 30, etc. for the Menu Position #s in my club's website instead of 1, 2, 3, etc.)
    
3. If you use a Menu Position # to force an item to the *bottom* of the menu (e.g. Menu Position #=999), then implicitly *all* Custom Web Pages/Links in that menu will need the Menu Position # set, since any new Custom Web Pages/Links will get put at the bottom of menus if you do not explicitly set the Menu Position #.