Home is probably hardcoded? Take a look at the xslt that generates the menu.

HTH,

Peter

Hi Daniel

Thanks for installing!

Anyhow, the test or umbracoNaviHide should definitely be working, I just tested it at http://beta2.geckonm.com

Here's the line in topNavigation.xslt

<xsl:for-each select="$homePageNode/node [string(./data [@alias='umbracoNaviHide']) != '1']">

A few things:

• Is the above line in your topnavigation.xslt file?
• What happens when you print out the value of $currentPage/data[@alias='umbracoNaviHide'] to the page? Is it 1?
• Is the field on your document definitely called umbracoNaviHide, with same capitalisation and spelling?

It's not a problem I've seen before, but thanks for reporting it. Hopefully we can get it sorted...

Dan

Yeah, the homepage node is in the XSLT and assumed to always be there....

Urgh, thanks Peter

Yeh, the homepage is hardcoded (I never imagined a situtation where it would be hidden!)  but I left the option to hide it in. doh

@daniel Here's the line in the xslt that need to be changed

change

<li>
   <xsl:if test="$currentPage/ancestor-or-self::node [@level=1]/@id = current()/@id">
      <xsl:attribute name="class">current</xsl:attribute>
   </xsl:if>
   <!-- NiceUrl takes a node ID and gives us a 'nice url' to the page -->
  <a href="{umbraco.library:NiceUrl($homePageNode/@id)}">
     <xsl:value-of select="$homePageNode/@nodeName" />
   </a>
</li>

to

<xsl:if test="string($homePageNode/data[@alias='umbracoNaviHide']) != '1'">
    <li>
        <xsl:if test="$currentPage/ancestor-or-self::node [@level=1]/@id = current()/@id">
          <xsl:attribute name="class">current</xsl:attribute>
       </xsl:if>
       <!-- NiceUrl takes a node ID and gives us a 'nice url' to the page -->
      <a href="{umbraco.library:NiceUrl($homePageNode/@id)}">
         <xsl:value-of select="$homePageNode/@nodeName" />
       </a>
    </li>
</xsl:if>

hope this helps,

Dan

Thanks, it worked :).

Well, i was just wondering why it wouldn't dissapear and i usually dont have a home button.

I was working under the mistaken assumption that everyone works the same way I do! ^^

This package is due a major update, esp. with the new xml schema in 4.1.   Will add this to my list of fixes and improvements.

Just realised I said "thanks for installing!" when we've been here before, and I've credited you with a fix!  Do you think you could check something for me? I think that 1.3 may have regressed the fix we made in 1.2 for events and months.  Could you double-check?

Dan

Hi again Dan,

Yeah - I'm going to use your package for smaller business sites as it is almost as I would do things.

As I recall the problem was that the months is hardcoded, and when we change the months to fx Danish the events won't appear, right?

Isn't it possible to make the calendar more dynamic, so that you can choose timeformat etc.? Have you looked into that?

Also it could be cool to have the package in different languages - i'm up for translating it to danish? :)

is working on a reply...