Symphony.

@ratdoesit: It seems like you are very fast in understanding the inner workings of XSLT. Most of us needed more time.

@michael-e: Yes, you’re right, ideally you’d leave the position predicate out of the match attribute for the xsl:template tags, making them more generic and therefore more powerful. Nice catch ;)

Thanks, Craig!

took me hours to find this post. couldn’t find anything to limit the output to 1. [1]. Any chance you guys know how to offset the next display of the DS so the “1” that I just limited will not be seen in the next section?

@dallasbpeters

Not sure I entirely understand what you’re going for, but DS pagination might do the trick. If you want your DS to only output 1 record, you can limit your DS output to 1 record per page, then use a {$param} (that you get from the page’s URL schema or the param pool) to say what page you want to output. These setting are below the filters on the DS editing page.

For instance, lets say your page is called ‘entries’ you can do

example.com/entries?page=2

then in your DS say limit to 1 entry per page, and show page {$url-page}.

or if your ‘entries’ page has a url schema of ‘the-page’:

example.com/entries/2

with a DS that says show page {$the-page}

@ashooner

I was hoping to loop through a single data set and for the first entry I would just show one large image and the title and some tags. Then right below that large image I was hoping to show the next 5 or six entries from the same section and show a thumbnail and title and then an excerpt from the entry.

Then I was hoping to offset the second loop so the first entry is not seen.

Maybe this screenshot would help. (I’m just started rollin’ with Symphony. Wordpress. So sorry if I use some WordPressie language. (wordpressie???) :)

Attachments:

loop.png

dallasbpeters: Thats actually quite easy. All you need are

<xsl:apply-templates select="xpath/to/entry[position() &lt; 7]" />

<xsl:template match="xpath/to/entry[1]" priority="1">
   Large image
</xsl:template>

<xsl:template match="xpath/to/entry">
   Small image
</xsl:template>

The apply-templates line goes where you want your images to appear in the markup. It will then apply the two templates on the first 6 entries you get from your DS. Because the first template has a higher priority it will override the second one, but only for the first image. All subsequent entries will be matched by the second template.

Edit: Does anybody know why [1] isn’t sufficient to increase the priority?

Or, because in case of equal priorities the processor will always use the last template you could put the <xsl:template match="xpath/to/entry[1]" /> below the <xsl:template match="xpath/to/entry" /> and leave out priority="1". But that could be harder to read once you’ll have to change something.

I suppose if you wanted to keep the [1] template above the other template in the source code you could add [position() > 1] to the second template?

I suppose if you wanted to keep the [1] template above the other template in the source code you could add [position() > 1] to the second template?

Of course but that way you’d end up having two lines for one rule wich isn’t exactly good programming style. :-)

Hmm. I was using modes. but now in the second template its still pulling the first. Have a look at this and tell me how jacked up it is.

home.xsl: <xsl:template match=&quot;data&quot;> <div id=&quot;content&quot; class=&quot;grid_20&quot;> <xsl:apply-templates select=&quot;projects/entry[1]&quot; mode=&quot;article&quot;/> <div id=&quot;projects&quot;> <xsl:apply-templates select=&quot;projects/entry&quot; mode=&quot;short&quot;/> </div> <h3 class=&quot;grid_20&quot;>From the Archives</h3> </div>

    <div id="sidebar" class="grid_4">
        <xsl:call-template name="welcome"/>
    </div>
</xsl:template>

And then the templates:

<xsl:template match="entry" mode="article">
    <div class="main_project">
        <div>
            <div id="main_image">
            <xsl:if test="(project-images) and (manage-images = 'Yes')">
                <xsl:call-template name="get-images">
                    <xsl:with-param name="image-entry" select="project-images/item"/>                 
                </xsl:call-template>
            </xsl:if>
            </div>
            <h3 class="recent"><span>Most Recent:</span><a href="{$root}/projects/{project-title/@handle}"><xsl:value-of select="project-title"/></a></h3>
            <p>
                <xsl:text>In this project: </xsl:text>
                <xsl:for-each select="discipline/item">
                    <a href="{$root}/discipline/{@handle}"><xsl:value-of select="."/></a>
                    <xsl:if test="position() != last()">, </xsl:if>
                </xsl:for-each>
            </p>
        </div>

    </div>
</xsl:template>

<xsl:template match="entry" mode="short">
    <div class="project">   

        <xsl:call-template name="get-thumbnail">
            <xsl:with-param name="thumbnail-entry" select="thumbnail/item"/>                  
        </xsl:call-template>

        <h3><a href="{$root}/projects/{project-title/@handle}"><xsl:value-of select="project-title"/></a></h3>


        <xsl:apply-templates match="body" mode="truncate">
            <xsl:param name="limit" select="50"/>
            <xsl:param name="suffix" select="'→'"/>
        </xsl:apply-templates>

        <p>
            <span><xsl:call-template name="format-date">
                <xsl:with-param name="date" select="date"/>
                <xsl:with-param name="format" select="'d m'"/>
            </xsl:call-template></span>
        </p>
        <p>
            <xsl:for-each select="discipline/item">
                <a href="{$root}/discipline/{@handle}"><xsl:value-of select="."/></a>
                <xsl:if test="position() != last()">, </xsl:if>
            </xsl:for-each>
        </p>
    </div>
</xsl:template>

By the way, thanks a million for the help. Don’t soak up too much of your time. ;)

well that didn’t work. http://pastie.org/788661

or that. http://pastie.org/788661

You have to do it like this: http://pastie.org/788673

By the way, entry[x] is just a shorthand for entry[position() = x].

Cool. Thanks a ton!