|
Home > Archive > WebSphere Portal Server > April 2005 > Regarding setting customized 2nd level navigation
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Regarding setting customized 2nd level navigation
|
|
|
| hello
everyone
is there any way we can have the second level navigation changed. for example i have 2 labels HOME and Products. and i am browsing some page in HOME label and if i now move to the Products label and then click again the HOME label then i will again see t
he same page in Home label (i.e 2 nd level) as i had left before i went to Product label.
Is there any way to change this default behaviour of portlets? what i want to achieve is that a user should always return to the same page anytime he clicks on a particular label say an overview page rather than the page he left when he switched to anothe
r label
please help me on this one
Thanks in advance
nk
| |
| Michael Harris 2005-04-03, 8:49 pm |
| Use the <wps:urlGeneration> tag to make a link to the exact page you
always want the user to navigate.
| |
|
| hello
micheal
, thanks for the reply. However can you give me more details as to where to specify the tags etc. i could not understand where exactly and how to specify the tags.
thanks
nk
| |
| Michael Harris 2005-04-04, 6:03 pm |
| First, you need to understand that implementing the technique below
isn't necessarily going to be simple. Also, it may not be the only
solution.
You will also need to write your own theme with custom navigation logic
in it.
If you only have a few pages that need this behavior, then you can
assign "custom unique names" to them using the portal administration.
The <wps:urlGeneration> tag can build a URL to pages that have a custom
unique name. Look in the InfoCenter for information on how the
<wps:urlGeneration> tag works. You'll need to edit the navigation logic
in the theme to replace it with a set of hardcoded <wps:urlGeneration>
links. This means that each time you want to add a page to the UI, you
will need to edit the theme JSPs to modify them. In order for this to
work, you'll need to build the "Home" tab (from your example) such that
it doesn't link to the "Home" page, but to the first child of the "Home"
page instead. Similarly, you'll need to build the "Products" tab such
that it links to the first child of the "Products" page.
If you want to change the behavior of the entire site and you
dynamically want to be able to add pages via the existing portal UI,
then you have more work to do. You can use the same technique as before
(changing a link so it really "clicks" on the first child") but you'll
need to use the Model API inside the <wps:navigation> and
<wps:navigationLoop> tags to locate the first child page's navigation
node. Then use the <wps:urlGeneration> tag to output that link instead
of the link to the current node. Look at the AdminLeftNavigation theme
for an example of using the <wps:urlGeneration> tag inside the
<wps:navigation> tag.
Note that the Model API is not a public API. You will need to work with
your IBM customer representative to obtain permission and documentation
for using it if your company doesn't already have it.
|
|
|
|
|