I am currently new to the Navigation control that is used for the top nav bar on MOSS publishing sites. The collection is using a top navigation bar that has a series of subsites listed as defined by the navigation link area under site settings. The issue I have is that the parent(root) site always has a few styles defined by a theme. Here is one of the styles.

    background-color:#f3bf38 !important;
    border-right:solid 1px #ffffff;

The problem is that only the root, parent site, will remain in this state. If I click to another site available on nav control, this rule isn't enforced. You will get to the site but the parent remains in selected state rather than the site I click on. How can I modify so the site I click on is hghlighted according to style above.

  • Just to double check, the link you click in the top nav is actually to a different sub-web, not to a view of a list or library within the same site, correct? I have seen this happen when items within the same site were added to the top nav bar and clicked, because, you actually are in the same site. – Lori Dec 23 '09 at 15:25

So I figured this out and it was pretty trivial but ignorance is bliss. The links across the top nav were set up as headings according to the publishing navigation control that I viewed from the site settings/navigation section. Once I changed the setting to show sub sites the control now showed each site on the top nav in addition to the headers. I deleted the headers and was left with the site links that were working fine and the CSS for the active link was working fine. This now forces me to ask why I would use headers on the top navigation. Maybe I am missing something obvious.

The bottom line is that publishing sites over quite the learning curve for admins coming from the basic collaboration portal set up using WSS 3 navigation.

| improve this answer | |

Have you changed the attribytes of your navigation treeview controls or data source in the master page?

If so what are your settings?

Anders Rask

| improve this answer | |
  • I haven't changed anything with the master page settings for the top nav control. The settings are default as far as I am aware. – Paul Akerlind Dec 23 '09 at 14:21

When looking at the html, is the css classes being assigned correctly? Or is the parent site the one that had the topnavselected css?

If it's a css issue, then maybe your stylesheet is not being loaded properly on this subsite. Otherwise the sitemapprovider isn't determining that the site you are currently visiting matches item in the top nav. Are the links to the subsites automatically created for your or did you put the link in? If you typed or copied and pasted the link, you might need to make sure that SharePoint knows that you are referring to an internal url. Sometimes you need to modify the url by removing the pages/default.aspx or something similar.

| improve this answer | |
  • The top nav bar was originially created with publishing not activated. It was a collaboration site only so the subsites were just one layer as the limitation with the WSS provider. The site links were created through the UI site settings page and each site inherited navigation from the parent. The theme is the same. The style is part of a custom theme that was created. – Paul Akerlind Dec 23 '09 at 14:25
  • Right, but how did the subsites get added? Did sharepoint do it for you when you created the subsites, or did you do it manually? What about the HTML? Did you check that out? – Steve Lineberry Dec 24 '09 at 3:58

My Top Navigation bar is not showing as selected. I am using a url to link to my custom pages in the same site. do you have any idea, why this is not working?

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.