I'm using this in combination with the Multi-Node Tree Picker, but it seems as the results are not parsed in the same way I send them. Anyone know how to deal with this? Is it a bug or am I missing something? When using the following XPath:
$currentPage/ancestor-or-self::* [@isDoc and @level = 1]/descendant-or-self::* [@isDoc and contains(concat(',', concat($csv, ',')), concat(',', concat(@id, ',')))]
I actually end up with the same result, so that's not doing the trick either! I also assume GetXmlNodeByCsv is faster so I prefer using that instead!
Come to think about it, I assume the same problem goes for GetXmlMediaByCsv, but I have not experienced this problem yet (probably due to I have not tried sorting images yet).
Yes, there's an issue with the original "GetXmlNodeByCsv" method - it returned the nodes in the order as they are found in XML cache (usually by @sortOrder).
For v2.1 (stable - due for release any day now), has an overload method that will persist the corrent order of the CSV ids:
GetXmlNodeByCsv(string csv, bool persistOrder)
The latest code is already up on CodePlex, so if you want it... go grab & compile the latest source code.
GetXmlNodeByCsv sorting
I'm using this in combination with the Multi-Node Tree Picker, but it seems as the results are not parsed in the same way I send them. Anyone know how to deal with this? Is it a bug or am I missing something? When using the following XPath:
$currentPage/ancestor-or-self::* [@isDoc and @level = 1]/descendant-or-self::* [@isDoc and contains(concat(',', concat($csv, ',')), concat(',', concat(@id, ',')))]I actually end up with the same result, so that's not doing the trick either! I also assume GetXmlNodeByCsv is faster so I prefer using that instead!
Come to think about it, I assume the same problem goes for GetXmlMediaByCsv, but I have not experienced this problem yet (probably due to I have not tried sorting images yet).
Hi Nikolas,
Yes, there's an issue with the original "GetXmlNodeByCsv" method - it returned the nodes in the order as they are found in XML cache (usually by @sortOrder).
For v2.1 (stable - due for release any day now), has an overload method that will persist the corrent order of the CSV ids:
The latest code is already up on CodePlex, so if you want it... go grab & compile the latest source code.
Cheers, Lee.
is working on a reply...