U4-4427 - Exception with selecting content start node in Multi-node tree picker 6.2.0

Created by Simon Steed 13 Mar 2014, 16:44:13 Updated by Shannon Deminick 17 Mar 2014, 02:10:50

Taken a V4.11.10 site today and upgraded it to 6.2.0 to see how it fares - all good apart from the datatypes using Multi-Node Tree Picker are no longer rendering any items in the content section

In dev/data types, trying to select a start node results in the popup window displaying the following YSOD. Not sure if it's specific to 6.2.0 but was working fine in 4.x

Cant tag this issue against 6.2 as it's not in the affected versions list.

Server Error in '/' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.] umbraco.dialogs.treePicker.OnLoad(EventArgs e) +206 System.Web.UI.Control.LoadRecursive() +54 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +772

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18446

Comments

Simon Steed 13 Mar 2014, 17:34:00

Just tried the site rolling back to 6.1.6 and the tree works fine so does appear to be a bug in 6.2.0


Sebastiaan Janssen 16 Mar 2014, 09:28:27

Confirmed. Possibly related to U4-4373 / U4-4374?


Shannon Deminick 17 Mar 2014, 02:09:32

Fixed, due to PR: https://github.com/umbraco/Umbraco-CMS/commit/e65a71a05a265bda0cccfda129377cbe73602299#commitcomment-5692839

have fixed up, really just needed a null check.


Priority: Critical

Type: Bug

State: Fixed

Assignee: Shannon Deminick

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.2.0

Due in version: 6.2.0

Sprint:

Story Points:

Cycle: