You'll definitely need to edito xsltsearch to do this, but it should be fairly manageable.

Results are stored in a $matchedNodes variable, so there's nothing stopping you doing several different

<xsl:for-each select="$matchedNodes/node [@nodeTypeAlias='Whatever']">
...

To split out the results.  You'll just need to be careful about paging - removing paging and using an improbably large page size would be easiest.  Once you have the results split out you could just use any of the tab implementations out there (such as jqueryui) to make your interface

Dan

thanks dan.

i'll post an update when i am finished

UPDATE:

i have tried a couple of options:

single search

mulitple search

• the 'tabs mark-up' placed in the template allowed me to drop in 3 instances of the search, picking alternate sources for the searches means that i am returning the results as they should be
• result count is correct per tab
• paging is correct per tab
• mark-up is wrong as there are now duplicate 'id', but i should be able to sort that out pretty quickly

glad you're getting somewhere!

regarding the empty divs, it's probably that when there are no results your div becomes self-closing (breaking css)

<div />

In this case you can change the output method from xml to html but this could break images

<img src="whatever.jpg"></img>

So you can put a non-breaking space in your div so that it doesn't close itself

 

Hope this helps,
Dan

Thanks dan

Hello everyone,

I've been constructing something similar with a XSLTSearch. However I've run into a pickle and I was wondering if anyone had any ideas.

Essentially I to am filtering search reasults by @documentTypeAlias to split out 'News' 'Articles' etc. However what I'm trying to create is checkbox list that allows users to pick which of these they would like to see at the same time. Trick is that although I can easily split matched nodes into set's for each area

<!-- get the actual matching nodes as a nodeset -->
<xsl:variable name="matchedNodes" select="$possibleNodes[contains($matchedNodesIdList, concat(';', concat(@id, ';')))]" />
<xsl:variable name="articleNodes" select="$matchedNodes [@nodeTypeAlias = 'Article']"/>
<xsl:variable name="newsItems" select="$matchedNodes [@nodeTypeAlias = 'News Article']" />
<xsl:variable name="eventItems" select="$matchedNodes [@nodeTypeAlias = 'Event']" />
<xsl:variable name="caseStudies" select="$matchedNodes [@nodeTypeAlias = 'CaseStudy']" />
<xsl:variable name="reviewItems" select="$matchedNodes [@nodeTypeAlias = 'Review']" />

I've having trouble selectively combining them. The closest I could fathum is.

<xsl:variable name="nodesToDisplay">
   <xsl:choose>
        <xsl:when test="string(umbraco.library:RequestForm('rbFilterArticles')) = 'on'">
            <xsl:copy-of select="$matchedNodes [@nodeTypeAlias = 'Article']"/>
        </xsl:when>
        <xsl:when test="string(umbraco.library:RequestForm('rbFilterNews')) = 'on'">
           <xsl:copy-of select="$matchedNodes [@nodeTypeAlias = 'News Article']"/>
        </xsl:when>
        <xsl:when test="string(umbraco.library:RequestForm('rbFilterEvents')) = 'on'">
            <xsl:copy-of select="$matchedNodes [@nodeTypeAlias = 'Event']"/>
        </xsl:when>
        <xsl:when test="string(umbraco.library:RequestForm('rbCaseStudies')) = 'on'">
            <xsl:copy-of select="$matchedNodes [@nodeTypeAlias = 'CaseStudy']"/>
        </xsl:when>
 </xsl:choose>
</xsl:variable>

Unfortunately the resulting variable cannot be proccessed with xsl:for-each without producing an error.

Any ideas would be welcome as I've had quite the head scratch today on the subject!

Hi DrewJigsaw,

You can process the resulting variable using the node-set extension function:

<xsl:for-each select="msxml:node-set($nodesToDisplay)/node"> ... </xsl:for-each>

/Chriztian

is working on a reply...