Adding support for top-level navigation

In V5.x, themes typically began rendering navigation at level 2 of the navigation model tree. Level one nodes (Home and Administration) were accessed by a Web address in the themes banner that explicitly identified that page. With migrated themes, this method creates problems if in V6.1 you assign the V5.x theme to a page that it was not assigned to in Version 5.x portal environment. For example, if you assigned the Version 5.x Administration theme to the Home page in V6.1, the theme would not provide any way to navigate to Administration because the V5.x Administration theme contained only a link to the Home page in the toolbar.

1. Add a NavigationLoop

   For detailed instructions, see the Implementing a single layer of navigation topic.

2. Hide unwanted pages from the navigation.
   In V6.1, you can hide top-level pages that you do not want to display in the top-level navigation by using a page metadata attribute. The following code is from mainMenu.jsp in the V6.1 Portal theme. Use this code inside a <portal-navigation:NavigationLoop> tag.

   <%
   boolean isNodeVisible = true; //default to display it
   //page metadata value used on top level nodes to hide from main menu
   if (wpsNavNode instanceof com.ibm.portal.MetaDataProvider) {
   	com.ibm.portal.MetaData iMetaData = ((com.ibm.portal.MetaDataProvider) 
   		wpsNavNode).getMetaData();
   	Object hiddenValue = iMetaData.getValue("com.ibm.portal.Hidden");
   	isNodeVisible = hiddenValue == null ? true: false;
   %>

   For more information on this code example, refer to mainMenu.jsp in the Portal theme