From 9f5f920c813342eb4c0a038f9c8656201b1ee841 Mon Sep 17 00:00:00 2001 From: leekelleher Date: Mon, 28 Jan 2013 17:18:20 +0000 Subject: [PATCH] MNTP: Corrected a typo in the example XPath (additional apostrophe) --- .../MultiNodeTreePicker/MNTPResources.resx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/umbraco.editorControls/MultiNodeTreePicker/MNTPResources.resx b/src/umbraco.editorControls/MultiNodeTreePicker/MNTPResources.resx index e3e9167bc1..0224ee5734 100644 --- a/src/umbraco.editorControls/MultiNodeTreePicker/MNTPResources.resx +++ b/src/umbraco.editorControls/MultiNodeTreePicker/MNTPResources.resx @@ -145,7 +145,7 @@ The XPath expression that is evaluated to match a start node can be evaluated at a global tree level, or matched from the current node being edited. - An xpath filter to match nodes that will be either enabled or disabled from being clicked (depending on what is selected for the XPath filter type). This XPath filter is for one node only so it should be formatted to select only one node. The XML to XPath against is the same as the Umbraco XML for one node.<br/><br/>Example: <code>/*[self::'myNodeType or self::yourNodeType]</code><br/><br/>The above would make all nodes of types: myNodeType or yourNodeType not selectable in the tree + An xpath filter to match nodes that will be either enabled or disabled from being clicked (depending on what is selected for the XPath filter type). This XPath filter is for one node only so it should be formatted to select only one node. The XML to XPath against is the same as the Umbraco XML for one node.<br/><br/>Example: <code>/*[self::myNodeType or self::yourNodeType]</code><br/><br/>The above would make all nodes of types: myNodeType or yourNodeType not selectable in the tree Should the XPath filter match nodes to enable nodes or disable nodes. If Enable is selected, this means that only nodes that match the XPath filter will be allowed to be selected in the tree picker and vise versa for Disabled