Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Multi Node Tree Picker not allowing selection

See original GitHub issue

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

11.4.0

Bug summary

Multi Node Tree Picker is not working, after selections, clicking submit shows an error on the console

It’s trying to split the property value, when it should be splitting the content data

Specifics

angular.js:15697 TypeError: $scope.model.value.split is not a function
    at $scope.add (umbraco.controllers.min.js?d=622eef5fd13567437e5b670d48f0a57e622aa980:1:108431)
    at umbraco.controllers.min.js?d=622eef5fd13567437e5b670d48f0a57e622aa980:1:107333
    at Function.mr (underscore-min.js?d=622eef5fd13567437e5b670d48f0a57e622aa980:6:9283)
    at $scope.currentPicker.submit (umbraco.controllers.min.js?d=622eef5fd13567437e5b670d48f0a57e622aa980:1:107288)
    at Object.submit (umbraco.controllers.min.js?d=622eef5fd13567437e5b670d48f0a57e622aa980:1:254201)
    at fn (eval at compile (angular.js:16548:15), <anonymous>:4:232)
    at d.<computed> [as action] (angular.js:11517:22)
    at UmbButtonController.clickButton (umbraco.directives.min.js?d=622eef5fd13567437e5b670d48f0a57e622aa980:1:67547)
    at fn (eval at compile (angular.js:16548:15), <anonymous>:4:245)
    at e (angular.js:29123:13)

Steps to reproduce

use a multi node tree picker and select any node

Expected result / actual result

No response

Issue Analytics

State:
Created 4 months ago
Comments:10 (3 by maintainers)

Top GitHub Comments

1reaction

ccasalicchiocommented, Jun 7, 2023

You are totally right, I feel dumb! It was bad data from the previous property editor, messing up the MultiNode TreePicker. After deleting the bad data, the editor worked just fine 😦

0reactions

nul800sebastiaancommented, Jun 7, 2023

@ccasalicchio I think you’ll find that the code between the v11/dev (left in the image) branch and the contrib (right in the image) branch is the same.

So I don’t think this is just a problem on v11, but more a problem with something in your current solution. If you can reproduce this problem on a clean install of v11.4 then please detail the steps so we can have a look. My MNTP works fine in a 11.4 website.

https://github.com/umbraco/Umbraco-CMS/assets/304656/735cf85d-0abe-46fc-9f1b-05b0c266d13b