Links in portal toolbar no longer working after navigating within a room

Question

Hi!
We have a rather strange problem. Say a user navigates to the collaboration room list ("collaboration" -> "rooms") and enters a room. When he/she then changes the part of the room (e.g. from "Room Discussions" to "Room Documents"), the second row of the top navigation bar gets inoperable.
Our portal menu looks like this ("=some entry=" means "selected"):
Intranet
Help
Content-Administration
=Collaboration=
=Rooms=
My Tasks
My Meetings
After entering a room and changing to any other room page than the one initially shown, the menu jumps to this state:
=Intranet=
Help
Content-Administration
Collaboration
=Rooms=
My Tasks
My Meetings
So suddenly the first entry in the top bar is highlighted, not "collaboration" anymore. (I can tell it's always the first entry who gets selected, since not every user's view has "Intranet" as the first entry - and still the first entry gets selected.) From now on, "Rooms", "My Tasks" and "My Meetings" are inoperable. They are still clickable links, but clicking on them causes a javascript error and nothing happens. ("'gNavTree.children[...].children' is null or no object")
Clicking on "Collaboration" in the top level navigation bar fixes the problem. The page reloads and everything is as it should be. This is reproducible in IE and Firefox. A complete reboot of the portal did not help. This only occurs when browsing within a room. Browsing within other parts of the portal does not have this effect.
Unfortunately I don't recall which change we made to the portal that caused this. (It definitely worked at some point before.) I do recall, however, that we translated "collaboration" (and only "collaboration") to another term better suited to our needs using the portal content translation feature. However, to rule this out as a cause of the problem I reverted to the original naming and the problem remained. Just thought I'd mention it for what it's worth.
Does anyone have any ideas?
Thanks a lot in advance for your input! It's no showstopper, but it's confusing the users and kind of a weird problem I can't explain.
Regards,
Jens

Answer 1

Hi Prabhakar,
we have an open call on this issue. SAP replied on the 10th of March:
"As this DTN issue isn't reproducable on our SP15 system, please upgrade your KM version to PL1, as per NOTE 911395(same as our test system). If for some reason the issue still exists after this upgrade I will further this issue with our Dev colleagues."
I read the note mentioned (which contains a list of the changes in PL1) and it says nothing about this issue in particular, if I'm not mistaken. Our system is on SP15 (not SP15 PL1), so we'll have to upgrade to PL1 first before we can investigate this any further. I currently don't know when this update is scheduled by our systems engineering department.
Is your system on PL1 by any chance? If so, then the problem has not been fixed in PL1 - which would be interesting for us to know.
Thanks,
Jens