Hi Ulla

I'm thinking you should add a content picker property on the horse document type (since the relation is 1-1), which you can use to select the parent horse.

Then in your XSLT you can fetch the id with the umbraco.library:GetXmlNodeById() extension and then retrieve the information about the parent horse. It should'nt be too complicated to achieve what you're after then.

Alternatively you can configure an instance of the ultimate picker where you can get the possible horses listed in a dropdown box on the content node - this also returns the id and the process in the XSLT will be the same...so I think you should go with the first mentioned option, unless you're client is liking the dropdown better than the content picker. It could be that the latter approach makes more sense to him/her.

Let us know if you need some further explanation and XSLT examples to get you moving :)

Hope this helps.

/Jan

Hi. I would suggest changing the whole structure a bit. So that all horses would be in one single tree of parents and their offspring. Then turn the top level category ("Horses for sale", Horses Sold", "Competing horses" etc.) into a property (e.g. "Category") of the horse doctype (a drop-down list or a checkbox list). There'll be also additional profit that you will be able to let a horse to belong to several categories in case you implement this property as a checkbox list.

Hi guys

Thanks for all of your great feedback - there's good stuff in all of your posts, so I've decided to do bit of a cocktail of al them. I have Installed uomponents - and I've got the Multiple-Node Tree Picker working on my Horse document Type. But the XSLT is causing me problems. I've called my Data Type:"SelectFoal"

I've made an XLST and macro called "ListFoals" Which I have included on my Horse template. Ive tried modyfing the xslt from your article, but I'm a bit of a novice when it comes to XSLT - so it's not really working.

My XSLT looks like this:

<xsl:output method="xml" omit-xml-declaration="yes"/>

<xsl:param name="currentPage"/>
    
<xsl:key name="document-by-id" match="*[@isDoc]" use="@id" />

<xsl:template match="/">
<xsl:apply-templates select="$currentPage/SelectFoals" mode="multipicker" />
</xsl:template>

<xsl:template match="MultiNodePicker" mode="multipicker">
<!-- Handle all the nodeIds in one go (!) -->
<xsl:apply-templates select="key('document-by-id', nodeId)" />
</xsl:template>

    

<xsl:template match="Horse">
  <div class="horseBlock">  
    <div class="horsePicsmall">
    <xsl:choose>
        <xsl:when test="normalize-space(horsePic)">
                <img src="{umbraco.library:GetMedia(horsePic, false())/umbracoFile}" />
        </xsl:when>
        <xsl:otherwise>
                <img src="http://stutterigroenvang.com/css/pictures/EmptyImage.jpg" />
        </xsl:otherwise>
    </xsl:choose>
    </div> <!-- END horsePicsmall -->
    <div class="horseItemText">
      <h3 class="headline"> <a href="{umbraco.library:NiceUrl(@id)}">
          <xsl:value-of select="@nodeName"/></a>
      </h3>
      <p class="introduction">
          <xsl:value-of select="umbraco.library:ReplaceLineBreaks(introduction)" disable-output-escaping="yes"/>
      </p>
    </div><!-- END horseItemText -->
  </div><!-- END horseBlock -->

</xsl:template>
    
</xsl:stylesheet>

At the bottom I've reused the XSLT that I originally made for displaying the offspring in a list - This might have to be remodelled a bit, but It contains most of the properties that I'd like to display in the list.

However I'm convinced that the problems is that I'm not getting the data from the Picker right - Can you guys see what wrong?

Hi Ulla,

It looks pretty good, actually - it's probably down to a typo or similar at this point; Check that the *property* on $currentPage actually has the alias "SelectFoals" (i.e.: The Umbraco GUI will try hard to name it "selectFoals" if you type "Select Foals" in the Name field, but it's still possible to override that).

/Chriztian 

Hi Christian

You just nailed it - that was exactly the problem :) I changed "SelectFoals" to "selectFoals" and it now works like a treat. Thanks so much for your help :)

And btw. I also changed the strucure so that all the horses a now contained under the same parent note. I have then applied true/false checkboxes for wether the horse is in the breeding programme, for sale etc. Now I can call the horses into lists using XSLT, according to which checkboxes are checked. This is much easer for the Client to handle - so thank you to all of you :D

Cheers Ulla :)

is working on a reply...