Multinodepicker2 ignores XPath and starting node settings
I've created two datatypes based on the Multinode TreePicker (MultiNodeTreePicker2). One is using the XPath setting (e.g. //homepage[1]) and the other has been set with a starting node. In the editor view, both these settings are being ignored and the root content tree is appearing unfiltered.
Oddly, the ContentPicker2 datatype is also ignoring the starting node.
Any ideas? All content is published; I've rolled the clientDependency version, and rebuilt the indexes.
Multinodepicker2 ignores XPath and starting node settings
I've created two datatypes based on the Multinode TreePicker (MultiNodeTreePicker2). One is using the XPath setting (e.g. //homepage[1]) and the other has been set with a starting node. In the editor view, both these settings are being ignored and the root content tree is appearing unfiltered.
Oddly, the ContentPicker2 datatype is also ignoring the starting node.
Any ideas? All content is published; I've rolled the clientDependency version, and rebuilt the indexes.
I'm using clean Umbraco 7.12.0 installation.
Oh, I can see that this has been reported already.
http://issues.umbraco.org/issue/U4-11579
Hi Kieron
You should be able to use this approach as a temporary workaround until 7.12.1 is released https://our.umbraco.com/forum/using-umbraco-and-getting-started/93276-umbraco-7120-multi-node-tree-picker-start-node-not-working-anymore#comment-294997
I think I've seen Sebastian mention that it will be out early the coming week to address a few bugs discovered in the 7.12 release.
Cheers, Jan
Hey Jan, yeah I've seen a couple of things but looks like they've been all picked up and reported already. You guys are totally on it! Thanks.
is working on a reply...