Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I've created a template site in SP2010, which will be used to create additional sites. I've noticed an issue with the current navigation (aka quick launch menu) when creating a site using this template. I have headings in the current navigation, some of which are links to site pages and others which are meant to organize additional links (also to other site pages) in the menu. The 'organizational' headings aren't meant to point to anywhere, only to group the sublinks.

For some reason, though, when I create a site using this template the 'organizational' headings become links which point to non-existent sites. For example: a heading titled "Planning" will point to https://site.domain.com/SiteTitle/Planning (note the lack of a page extension as well) when the template has no such URL.

My questions are: does anyone know why this is happening? I theorize that it has to do with SP's automated creation process, which will create the headings as links and does not look at exactly how they are configured in the template. Is there a way to prevent this from happening? Is there a simple solution that would not require much programming/development?

I've also created another template, whose menu only consists of these 'organizational' headings. It also performs this same behavior. At least it's consistent... I've attempted modifying the headings to remove the URL addresses, but leaving the field blank does not retain the change. It simply reverts back. The only fix I've found for this is to manually create new headings, migrate the sublinks to underneath the new heading, and then delete the old heading. This is cumbersome and wastes too much time. Any help is much appreciated. Thanks!

NOTE: The reason I need these to retain their non-link attribute is because of a jQuery solution I've modified (source 1, source 2) to have our current navigation collapsible with an accordion effect.

share|improve this question
    
Did you possibly have the solution to this?? I need the exact same thing and was wondering if you possibly had the solution to share. Thanks! –  Kam Nov 4 at 23:35
    
@Kam Yes, I provided my own solution in the second paragraph of the self-answer below. An additional clarification: the hash (#) is used to point to an element ID on the page, but no name is being provided so the headings route to nowhere. This is normal browser behavior. You could also use jQuery and preventDefault() on the click event for those elements. –  filoxo Nov 11 at 15:04

1 Answer 1

up vote 0 down vote accepted

My theory is correct. SharePoint does not respect the non-URL configuration of the headings in the template, and forces the new headings to point to the root directory. I'd like to also note that it is not consistent and sometimes points to non-existent folders in root.

To solve this, the links in the template will point to /#, and using javaScript I'll strip out the link attributes from headings which have child items (which I've already identified for the accordion current navigation solution).

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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