You shouldn't have to create the duplicate homepage node. Try just selecting the root page using the content picker?

Chris

That's odd.

I don't have a content picker in your Simple Website example. But I do have a physical node.

It's best to avoid creating a duplicate node where you can as it just causes hassle for you and confusion for your editors.

I'd advice running your navigation from a content picker where you can select nodes from any level. Is this not how Basic Website does it?

Chris

Is there any specifi requirement you do so ( Creating duplicate home pages)? let us now may be there can be alternate way to do this.

Cheers,

Jigar

I think you are missing my point. I have created a vanilla site and installed the your Standard Site 1.1 and in the content pane I get this node. I didn't create this its part of the site.

I can see why its there to allow for naviagtion to pickup all the level 2 nodes.

BasicSite and StandardSite use 2 different approachs for Navigation.

I would go with the one in BasicSite, it requires uComponents MultiTreePicker. I wanted the StandardSite package to have no dependencies otherwise I would have taken the same approach as BasicWebsite.

However, I think StandardWebsite does the redirect through the umbracoUrl field on the child homepage.

Yes. That is what I am asking... How did you do it. Its doesn't work for me. I get a blank page.

I am trying trying to figure how you got it to work as I cannot.

Gotcha.

I have a field on the child homepage called "RedirectUrl"

The navigation xslt then contains the following choose statement

<xsl:choose>
          <xsl:when test="string-length(data[@alias='RedirectUrl']) > 0">
            <a href="{data[@alias='RedirectUrl']}" title="{@nodeName}">
              <xsl:value-of select="@nodeName"/>
            </a>
          </xsl:when>
          <xsl:when test="string-length(data[@alias='RedirectPageId']) > 0">
            <a href="{umbraco.library:NiceUrl(data[@alias='RedirectPageId'])}" title="{@nodeName}">
              <xsl:value-of select="@nodeName"/>
            </a>
          </xsl:when>
          <xsl:otherwise>
            <a href="{umbraco.library:NiceUrl(@id)}" title="{@nodeName}">
              <xsl:value-of select="@nodeName"/>
            </a>
          </xsl:otherwise>
        </xsl:choose>

Sorry Chris.

This is my mistake. You don't use the Home link in the side navigation which uses the navigation.xslt script.

I do have that working. Apologies.

What doesn't work for me is the:

1. headerNavigation
2. primaryNavigation

 Both based on the RelatedLinksList.xslt script. I get nothing back.No output.

 From what I have figured out it relates to the navigation and header tabs on the homepage. This relies on the Page Picker data type pointing to the Home Page Node ID. 

OK so within the homepage I get the list of nodes to select in both tabs but the macro doesn't render anything.

The macro passes the variable  PropertyAlias  such as "headerNavigation" to the script but when I view the script I can't follow what it is doing...

Could you please tell me if this macro is calling anyting other than the navigation.xslt script?

Apologies for all the questions but I am nearly there.

It is only calling the xslt.

Try outputting any variables straight to the screen using value-of or copy-of to check they're what you're expecting.

is working on a reply...