steps to reproduce:
step 1) limit the picker to min 1 / max 1
step 2) pick a related content node, confirm your choice
step 3) pick a SECOND content node, without removing the first
result: you have 2 selected nodes while the limit sais 1.
Min and max properties of the LeBlender Editor aren't related to the the property you've added itself, it's related to how many times all properties can exist.
You should limit the number of items that may be picked via the "News item" property's data editor AFAIK.
I think you should check if it's working correctly first via a normal property on a normal document type. If it's validating well that way, it's a LeBlender issue.
Is this a leblender issue or core bug? multi-node treepicker doesn't respect item limits
limitations on the multinodetreepicker are not enforced, could this be a leblender issue or is it core related?
i submitted a bug here assuming it's core: http://issues.umbraco.org/issue/OUR-192?query=multi-node+treepicker
steps to reproduce: step 1) limit the picker to min 1 / max 1 step 2) pick a related content node, confirm your choice step 3) pick a SECOND content node, without removing the first result: you have 2 selected nodes while the limit sais 1.
Min and max properties of the LeBlender Editor aren't related to the the property you've added itself, it's related to how many times all properties can exist.
You should limit the number of items that may be picked via the "News item" property's data editor AFAIK.
Thanks Kip :)
because the limit is defined on the datatype as wel, so that would make it a core bug then...
Thanks for your input!
I think you should check if it's working correctly first via a normal property on a normal document type. If it's validating well that way, it's a LeBlender issue.
Rik,
How were you able to get the items you picked to display in the grid? I'm stuck at that point! See my post at https://our.umbraco.org/projects/backoffice-extensions/leblender/general-discussion//70807-using-a-multinote-treepicker-within-leblender
Thanks!
is working on a reply...