Unfortunately, the XPath expression for filters isn't parsed using uQuery (which handles the $currentPage replacement) ... so not sure that you can do what you need.
We'll look at what is involved in making this work for a future release.
@Hendy: How's about this for a solution: In 'XmlTreeNodeExtensions.cs', the 'DetermineClickable' method the XPath expression is passed to an XElement extension method called 'XPathSelectElements' ... before this happens, we could handle the $currentPage (and other known params) in the XPath expression (string).
Very similar to what we do in 'uQuery.GetNodesByXPath', but we don't query the nodes, just handle/parse/replace the params in the XPath?
@Lee, yes, we could do the string replacement in the OnRenderNode event in FilteredContentTree.cs (wouldn't need to apply to the media tree) - It does mean the string replacement would occur for each node being rendered, but much easier to apply :)
Infact how about just checking for the existance of "$currentPage" in the string, if present, update the XPath and store in the cookie ? (I'm assuming it's easy to get hold of the current page id)
Disallowing selection of the current node in MTP was a nice to have - it's not critical to the picker - but when I've got a minute I'll see about making the relevant changes (unless someone beats me to it!).
Disallow Current Node Id
I've got a CaseStudy doctype, it has the option to choose related case studies (multinodetreepicker).
I'd like to stop the user from selecting the current node, so I've got my XPath Filter set up:
It doesn't like the use of $currentPage/@id
If I do something with a hardcoded value, such as:
it works fine.Any suggestions? I've tried a few things with no luck.
(I should really know this...too)
Cheers,
Drew
Oh and Xpath type is set to 'current' and not 'global' :)
Hi Drew,
I've not tested this, but does it work if you change the setting to 'Global' and use the following XPath expression:
/*[name() = 'CaseStudy' and @id != $currentPage]
HTH,
Hendy
Unfortunately, the XPath expression for filters isn't parsed using uQuery (which handles the $currentPage replacement) ... so not sure that you can do what you need.
We'll look at what is involved in making this work for a future release.
Cheers, Lee.
Arrh, I missed the bit about it being a filter expression - oops
@Hendy: How's about this for a solution: In 'XmlTreeNodeExtensions.cs', the 'DetermineClickable' method the XPath expression is passed to an XElement extension method called 'XPathSelectElements' ... before this happens, we could handle the $currentPage (and other known params) in the XPath expression (string).
Very similar to what we do in 'uQuery.GetNodesByXPath', but we don't query the nodes, just handle/parse/replace the params in the XPath?
Cheers, Lee.
@Lee, yes, we could do the string replacement in the OnRenderNode event in FilteredContentTree.cs (wouldn't need to apply to the media tree) - It does mean the string replacement would occur for each node being rendered, but much easier to apply :)
Infact how about just checking for the existance of "$currentPage" in the string, if present, update the XPath and store in the cookie ? (I'm assuming it's easy to get hold of the current page id)
Thanks for the response guys!
Disallowing selection of the current node in MTP was a nice to have - it's not critical to the picker - but when I've got a minute I'll see about making the relevant changes (unless someone beats me to it!).
Cheers!
@Hendy, Curious how the storing it in a cookie would work? The XPath would need $currentPage to be variable across pages right?
@Drew, I've started to write some code for this... haven't got too far with it yet though (e.g. not pushed anything back to the repo).
Cheers, Lee.
is working on a reply...