<div>
That is likely because you are doing the paging first and after that order the page<br />
(which is not an uncommon problem)<br />
<br />
Note that if you would be using the preceding-sibling axis or following-sibling axis,<br />
those operate on the elements in document order, not in sorted order<br />
<br />
I suggested in this project that you would do the filtering and sorting in a first XSLT<br />
and you would deal with the paging after that.<br />
This suggestion had a reason... exactly this problem<br />
Doing so would dramatically take down the amount of code you would need and would lessen the risk for errors<br />
<br />
Are you still doing this in two steps? or did you abandon that approach.<br />
I recommend still to make it two steps
</div>


<div>
Hi Gertone,<br />
<br />
Thanks, i'll try replacing that code.<br />
Will I also need to replace the pagination links that are created in the navigation template?<br />
<br />
Thanks
</div>


<div>
Hi Gertone,<br />
<br />
Im just asking the server guys now to see if any of them know for me, thanks.<br />
<br />
Will I need to amend the way I build the previous and next pagination buttons also?<br />
<br />
Thanks
</div>


<div>
previous and next only depend on the start point, so that would be OK, I guess<br />
<br />
<br />
<br />
In case the server guys don't know<br />
<br />
sneak this in your XSLT<br />
&lt;xsl:value-of select=&quot;system-property('x<wbr />sl:version<wbr />')&quot; /&gt;//<br />
&lt;xsl:value-of select=&quot;system-property('x<wbr />sl:vendor'<wbr />)&quot; /&gt;//<br />
&lt;xsl:value-of select=&quot;system-property('x<wbr />sl:vendor-<wbr />url')&quot; /&gt;<br />
<br />
and you will find the information in the result
</div>


<div>
Ok, i'll pop that in there today and upload it and let you know what comes back.<br />
<br />
My final pagination questions is, how do I stop the next &gt;&nbsp;link appearing if there are no more pages to scroll through.<br />
<br />
I have it working for &lt;&nbsp;prev as I have done a choose statement that checks to see if $first = 1, but not sure how to do it when it gets to the last record.<br />
<br />
I'll open a new thread with the xsl version so you can get these points for the help you have already provided.<br />
<br />
Thanks
</div>


<div>
for last record you need to count the <b>filtered </b> records, not all records
</div>


<div>
Thanks, got it.<br />
Also, here is what I got back from the XSLT processor code:<br />
1 // James Clark // <a href="http://www.jclark.com/" rel="ugc">http://www.jclark.com/</a><br />
<br />
Open source processor by James Clark.
</div>


<div>
well, that is a very old processor (&quot;XT&quot; it is)<br />
I have never seen it used in production before.<br />
<br />
It is the old processor James Clark wrote to test the XSLT specification (he is the author of version 1)<br />
I never realised that people would use it in production<br />
<br />
But I just checked, it supports xt:node-set, so you will get away with a two step<br />
I have to go now.<br />
I will download XT later (it must be the single one processor I don't have on my machine :-) and make a test example<br />
for an XSLT twostep<br />
that will likely be after the weekend
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I've created an XSL that reads in XML data and transforms it successfully. I have introduced sorting which is working perfectly, then I added pagination which works but when they are both used together the results aren't exactly what I want.<br />
<br />
Say I have 12 records that match the criteria of the xsl, If I limit the page size to 5 records and sort by price descending then it sorts the first page of results but doesn't necessarily put the most expensive of the 12 at the top, just the most expensive on that page of results. On the other 2 pages there could be more expensive ones.<br />
<br />
How do I make this so that if I sort by price descending it sorts the records then paginates. so that the order is correct, and then the order is maintained as they scroll through the pages.<br />
<br />
I can add my XSL if you would like to see what I am doing currently.<br />
<br />
Thanks
</div>
</div>


Hi,

I've created an XSL that reads in XML data and transforms it successfully. I have introduced sorting which is working perfectly, then I added pagination which works but when they are both used together the results aren't exactly what I want.

Say I have 12 records that match the criteria of the xsl, If I limit the page size to 5 records and sort by price descending then it sorts the first page of results but doesn't necessarily put the most expensive of the 12 at the top, just the most expensive on that page of results. On the other 2 pages there could be more expensive ones.

How do I make this so that if I sort by price descending it sorts the records then paginates. so that the order is correct, and then the order is maintained as they scroll through the pages.

I can add my XSL if you would like to see what I am doing currently.

Thanks

correctly sorting and pagination XSL

Extensible Markup Language (XML) refers to the encoding of documents such that they can be read by both machines and humans. XML documents use tags to show the beginning and end of a set of data. XML is used extensively on websites to show volumes of data, and is the default for a number of office productivity suites. This topic includes discussions of XML-related technologies, such as XQuery (the XML Query language), XPath (the XML Path language), XSLT (eXtensible Stylesheet Language Transformations), XLink (the XML Linking language) and XPointer (the XML Pointer language).