Hi Dwayne

Did you use the default build in XSLT template for your navigation? I think it could be a lot easier to help if you could provide us with the XSLT code you are using to render the navigation. Thanks.

/Kim A

Davs Kim,

Yeah, code helps. Just thought I'd throw out the question first. Maybe it's something simple. Anyway, I am checking hidden docs: [not(&hidden;)]

    <xsl:template match="/">
      <xsl:variable name="siteRoot" select="$currentPage/ancestor-or-self::* [@level=1]" />
           
      <xsl:variable name="mainMenuItems" select="$siteRoot /* [@isDoc] [not(&hidden;)]"></xsl:variable>
        <ul class="nav" id="nav-level1">
          <xsl:apply-templates select="$mainMenuItems" />
        </ul>
    </xsl:template>

    <xsl:template name="ShowMenuItem" match="*">
        <xsl:variable name="isCurrent" select="@id = $currentPage/ancestor-or-self::* /@id" />
        <li>
          <xsl:if test="$isCurrent">
            <xsl:attribute name="class">
              <xsl:text>current</xsl:text>
            </xsl:attribute>
            </xsl:if>
            <a href="{umbraco.library:NiceUrl(@id)}">
                <xsl:value-of select="@nodeName"/>
            </a>
          <xsl:variable name="subPages" select="./* [@isDoc] [not(&hidden;)]" />
            <xsl:if test="$isCurrent and $subPages">
              <ul class="nav" id="nav-level2">
                  <xsl:apply-templates select="$subPages" />
                </ul>
            </xsl:if>
        </li>
      </xsl:template>

Could you try this instead:

<xsl:template match="/">
      <xsl:variable name="siteRoot" select="$currentPage/ancestor-or-self::* [@level=1]" />
           
      <xsl:variable name="mainMenuItems" select="$siteRoot /*[@isDoc and string(umbracoNaviHide) != '1']"></xsl:variable>
        <ul class="nav" id="nav-level1">
          <xsl:apply-templates select="$mainMenuItems" />
        </ul>
    </xsl:template>

    <xsl:template name="ShowMenuItem" match="*[@isDoc and string(umbracoNaviHide) != '1']">
        <xsl:variable name="isCurrent" select="@id = $currentPage/ancestor-or-self::* /@id" />
        <li>
          <xsl:if test="$isCurrent">
            <xsl:attribute name="class">
              <xsl:text>current</xsl:text>
            </xsl:attribute>
            </xsl:if>
            <a href="{umbraco.library:NiceUrl(@id)}">
                <xsl:value-of select="@nodeName"/>
            </a>
          <xsl:variable name="subPages" select="./* [@isDoc and string(umbracoNaviHide) != '1']" />
            <xsl:if test="$isCurrent and $subPages">
              <ul class="nav" id="nav-level2">
                  <xsl:apply-templates select="$subPages" />
                </ul>
            </xsl:if>
        </li>
      </xsl:template>

Does that make a difference?

I can see that you are using an entity called "hidden", could you maybe show us this as well, if the above doesn't work.

/Kim A

Works like a charm, Kim ;~) Thanks. Not sure what you mean by "show you the entity"? I had some help creating that script, and as far as I recall there are no created entities. Where would they be created?

I was looking on W3C and could not locate hidden. It appears you simply substituted this with

and string(umbracoNaviHide) != '1'

correct?

Wait! I did create that entity and forgot about it. DOH!

<!DOCTYPE xsl:stylesheet [
    <!ENTITY nbsp "&#x00A0;">
    <!ENTITY hidden "data[@alias = 'umbracoNaviHide'] = 1">
]>

Not sure why it prevents the pages from hiding. Any clue on your end?

Yeah that's correct.

I thought that you where using some kind of entity since you where reffering &hidden; which might contain the umbracoNaviHide, or something like that. If this doesn't make any sense to you don't mind :)

Anyway, I'm glad you got it working.

/Kim A

Cool. I created that entity at an early developmental stage because my menu was not presenting any links. The entity helped initially, before I learned I need to initialize umbracoNaviHide by setting the property on a docType so the xslt can run properly. Was not certain that &hidden; was a call to it. Now the pieces are falling into place.

I'm glad to have it cleared up, and changing the legacy will most likely allow that script to run. But I think the change you provided is cleaner. Still nice to know. Learned something new.

I tested the entity that corresponds with the new XML schema and that did the trick. Both methods work, but I'm checking the entity change as a solution, as that was the initial problem. Thanks for the help Kim!

Cool! Great to hear that the entity trick worked as well :)

/Kim A

is working on a reply...