It doesn't seem to be stored in the node

<node 
    id="1076" 
    version="f4b05a70-c7a2-4e3b-a52f-d5a79eb06d23" 
   parentID="1050" 
  level="2" 
    writerID="0" 
 creatorID="0"
 nodeType="1043" 
  template="1044" 
  sortOrder="3" 
    createDate="2009-09-30T15:31:29" 
 updateDate="2009-10-27T17:19:07" 
 nodeName="Primary" 
   urlName="primary" 
    writerName="Administrator" 
   creatorName="Administrator" 
  nodeTypeAlias="TextPage" 
 path="-1,1050,1076">

So it may need to be a case of finding from the document type in 'settings' which nodes inherit and putting the nodeTypeAlias' in the for-each manually...

Unless someone has more info?

Dan

Mike, could you hook on to any unique properties on the parent docType?

For example, lets say you have a parent docType called "BaseDocType" and a property in it called "inheritedDocType". Then in the XSLT you can do this:

<xsl:for-each select="$currentPage/ancestor-or-self::node[@level=1]/node[@nodeTypeAlias != 'BaseDocType' and count(data[alias='inheritedDocType']) &gt; 0 and string(data[@alias='umbracoNaviHide']) != '1']">
    <xsl:value-of select="@nodeName" />
</xsl:for-each>

Here is what is happening in the select... the first condition is checking that it not the base doc-type, the second is checking if it has the inherited property, and the third is your usual 'umbracoNaviHide' test.

It would be much nicer to have a node-level attribute/property called "parentNodeAlias", but then where do you draw the line, as you have several nested doc-types ... unless they went down the @path route? (with comma-separated doc-type ids).

Let me know if it works out!

Cheers, Lee.

Hi Mike,

I think Dan is probably right. What are you trying to do? Maybe there is another way to solve your problem?

Chris

Under my home page, I have several pages (some standard pages, maybe some other pages which inherit from a standard page - like a 'section page'), but I also have a couple of folders for pages which will go in header and footer navigation elements. In my primary nav xslt, I'm trying to exclude everything under the home element which isn't something which inherits from a standard page.

I could list all the inherited types, or conversely I could select everything except the folder types - I just thought that if there was a quick way to select nodes based on their inherited type, that would be a tidy way of doing it.

Thanks for your help,

Mike

If I understand you correctly, you currently have the following structure:

home
home/blog/blog post
home/etc.....
home/footerfolder/terms and conditions
home/headerfolder/contact us

Why not move the footer & header folders up to the root of your content structure?

Another option is to add a couple more parameters, I.e. umbracoNaviFooterHide / umbracoNaviHeaderHide ( or the opposite... "show" )

Cheers,

Chris

I want to keep the header and footer folders underneath the 'home' node because there's a chance this could be a multilingual site. Lots to consider... :-)

Personally I think the true/false switches for header/footer links (as Chris mentioned) is the way to go ... it's a more scalable solution.

Hi,

I usually have a top level node called "site" which holds site wide parameters, this could be where your multiple lingual seperation happens as you'd have multiple site's each with their own "home" / "footer" / "header" sections.

Just an idea :)

Cheers,

Chris

One of the advantages of Master Templates is that all of the children inherit all of the data types. Since this is the case, you can add a datatype to the master template, similar to the UmbracoHideNavi checkbox that the navigation will look for. Since the folder's don't inherit this data type, then the folders will not display.

Chris,

That sounds interesting --- quick question though - how do you prevent NiceUrl links from reading "/home/section/page.aspx"? (I wouldn't want the "/home/" part in there...

Cheers,

Mike

Does the "hideTopLevelNodeFromPath" setting not do that?  It's in umbracosettings.config  (I think!)

@Dan: "umbracoHideTopLevelNodeFromPath" is in the Web.config ;-)

Ah, probably should check these things instead of dropping disclaimers!

The hideTopLevelNodeFromPath setting is already true; Chris was suggesting a structure like this, to enable a multi-lingual approach, but also to logically separate normal site content from header and footer elements:

+ Content (root)

     + Site

          + Home

               (normal site content pages)

          + Header

               (header navigation pages - glossary, downloads, site map etc)

          + Footer

               (footer navigation pages - accessibility, privacy policy etc)

Hi Dan - this seems like a really tidy solution, thanks for your help.

Mike

Hi there - it looks like you solved the problem, but I thought I'd toss in my 2 cents because I had a similar issue and used a bit of a workaround - I'm relatively new to Umbraco so please feel free to shoot it down ;)

Due to the project specs and the way I've handled the inheritance, I need to display all pages that inherit from a specific master page and have a given tag - I used a naming convention and filtered by "contains" rather than an exact match to the parent type - every document type under the "ContentPage" doc type has "ContentPage" in its alias (ie "ContentPage2Column"):

Is there a more elegant way?

Cheers, Saxon

sigh, new to the boards, sorry about that....

<xsl:for-each select="umbraco.library:GetXmlNodeById(number($source))/descendant::node [contains(@nodeTypeAlias,'ContentPage') and contains(Exslt.ExsltStrings:lowercase(./data [@alias='Categories']), Exslt.ExsltStrings:lowercase(string($filter)))]">
  <!-- node code -->
</xsl:for-each>

is working on a reply...