U4-10299 - Legacy trees are causing errors in the backoffice after upgrading to v. 7.7

Created by Claus Jensen 16 Aug 2017, 09:28:15 Updated by Shannon Deminick 18 Aug 2017, 04:11:48

Tags: Unscheduled

Subtask of: UAASSCRUM-964

When using a legacy tree, we tried to inject an instance of userResource - this has been renamed in 7.7 so it was causing JS errors in the backoffice.

There's also an issue with legacy trees if there's no querystring formCollection data - due to a missing null check. Since this can be called by https://github.com/umbraco/Umbraco-CMS/blob/dev-v7.7/src/Umbraco.Web/Editors/SectionController.cs#L51 with null for the querystring data - this will fail. This was causing (local) Courier to fail initializing its tree for security for some reason - most likely would also affect other things using legacy trees.

Comments

Claus Jensen 16 Aug 2017, 11:50:21

PR: https://github.com/umbraco/Umbraco-CMS/pull/2133


Shannon Deminick 18 Aug 2017, 04:06:16

haha, yup also fixed this one ;)


Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.7.0

Due in version: 7.7.0

Sprint: Sprint 65

Story Points:

Cycle: