U4-10986 - Multinodetreepicker on members returns nothing.

Created by Jesper Mayntzhusen 19 Feb 2018, 15:02:54 Updated by Sebastiaan Janssen 27 Feb 2018, 09:29:39

Tags: Gold partner

Relates to: U4-10958

Your report will have a greater chance of being addressed if you can give us clear steps to reproduce the issue, please answer the following questions in as much detail as possible: What did you do? Our Gold Partner Embrace, reported an issue with the multinode tree picker when you select members no content is rendered on frontend. It worked perfectly fine when you selected content instead or media(with the workaround).

I did the following steps to verify this issue:

  1. Created a document type called homepage
  2. Added a property to document type homepage called userPicker using the multinode tree picker data type.
  3. Set the multinode tree picker to pick from members.
  4. Added the following razor script to the homepage template: @{ var users = Model.Content.GetPropertyValue<IEnumerable>("userPicker"); foreach (var user in users) {


    } }

We did the following to test the multinode tree picker set to members: 5. Created a content page based on the homepage doc type called homepage. 6. Set the homepage content page to pick a member 7. Frontend returned nothing!

1 Attachments

Download WorkaroundMultiNodeTreePickerPropertyConverter.cs


Sebastiaan Janssen 21 Feb 2018, 11:15:27

Well, this is embarrassing! Unfortunately, the fix for this exact issue was meant to go into 7.7.12 but unfortunately the build of 7.7.12 was created from the commit BEFORE this updated code was put in. My sincere apologies for the inconvenience.

I've attached a workaround that can be dropped into the App_Code folder, it's similar to the one in http://issues.umbraco.org/issue/U4-10958 but it's updated a little bit to fix the issue with picked members. Content and Media work fine in 7.7.12 at the moment. Of course 7.7.13 will include the actual fix in Umbraco core and when it's out and you've upgraded to it, this App_Code file can be removed again.

Once again, apologies for the inconvenience!

Priority: Normal

Type: Bug

State: Fixed


Difficulty: Normal


Backwards Compatible: True

Fix Submitted:

Affected versions: 7.7.10, 7.7.11, 7.7.12

Due in version: 7.7.13


Story Points: