Update logic for checking for groups to be more robust (as we could still have one named group)
This commit is contained in:
@@ -92,7 +92,8 @@ namespace Umbraco.Web.Trees
|
||||
}
|
||||
|
||||
//Don't apply fancy grouping logic futher down, if we only have one group of items
|
||||
if (CoreTrees.Value.Count() == 1)
|
||||
var hasGroups = CoreTrees.Value.Any(x => x.Key != null);
|
||||
if (hasGroups == false)
|
||||
{
|
||||
var multiTree = SectionRootNode.CreateMultiTreeSectionRoot(rootId, collection);
|
||||
multiTree.Name = Services.TextService.Localize("sections/" + application);
|
||||
|
||||
Reference in New Issue
Block a user