How do we change tabs in the header?

Incident code 16384-45821 reported 7/31/2008
Customer would like to remove some of the tabs from the header, as well as add new ones that link to resources outside their catalog? How can they do so?
At the moment, we can’t connect to see the interface, but external access is being requested.
8/1/2008 Hi Toni,

The following explanation will show you how to add new tabs to the header. The first part of it will instruct you to add new XML to the pageProperties.xml file–for each new XML element you add, a new tab will be created. If you would like to REMOVE existing tabs from the header, just comment out the XML you would like to remove. So, for example, to remove the “My List” tab, you would comment out the XML that calls it at the top of that file, as follows:

<!– This comment removes the "My List" tab

End comment to remove the “My List” tab. –>

(It’s clearer when you have a look at the file in question.) See the instructions below for full paths to the files you’ll edit.
Adding a new tab to the header

First, establish a unique variable that you use for this action. It should be one string that you will use to bind properties to this action across the three files you edit. (For example, the variable for the “My Account” tab is “myAccount”.) For ease of maintenance, choose a variable that will clearly communicate which tab you’re describing. In this example, it will be “exitSession”.

To add the new tab, you’ll edit three files:


XML you add to pageProperties.xml will be used by header.xsl to write the HTML for the tab to the page. Locate the comment in pageProperties.xml, and add new “tab” element between the and tags. Where you place it will depend on in what order you want it to display. To add it to the right of the existing tabs, place the new element immediately before the tag. It will look as follows:


* exitSession is the unique variable you’ve established for this tab.
* The value of the “name” attribute matches the .button variable set in (see next step).

In the “Header” section of, set the new tab’s label as follows:

#Custom “Exit Session” tab labels
page.header.buttons.exitSession.button=Exit Session
page.header.buttons.exitSession.message=Exit the catalog

where: exitSession is the unique variable that you’ve established for this tab.

* .button value is the text that display in the tab
* .message value is the alternative text that displays on mouse hovering and for screen readers

In the “Header” section of, set the tab’s action as follows:

#Custom “Exit Session” tab action


* exitSession is the unique variable that you’ve established for this tab.
* .action value is a URL. This can be an existing WebVoyage action, or a complete URL (such as

I’ve set this incident to a status of “W4I” so you’ll have some time to try this and get back to me with any further questions. If you would like clarification, give us a call or update this incident via eService. If it works out as you’d like, let me know and we’ll close this incident.

John Larson
8/1/2008 Thanks, John–we’re working through the tabs instructions and making progress. Regarding viewing our WebVoyage sandbox URL, our IT staff has made port 7008 available to the Ex Libris domain and can see Ex Libris traffic coming over port 7008. We’re wondering if you could try accessing the URL at another computer to see whether the display problem could be local to your PC? Toni
8/5/2008 This worked and also helped us with footer tab changes, too. Thank you–please close this incident. [We moved our development skin so that access to port 7008 was no longer needed and Ex Libris support was then able to view our test catalog. Toni]

This entry was posted in Miscellaneous. Bookmark the permalink.