U4-1786 - After Upgrade V6 Document Types displayed as flat structure. Tree hierarchy no longer displayed

Created by Adrian Donnelly 26 Feb 2013, 16:47:45 Updated by Sebastiaan Janssen 31 Oct 2013, 08:18:15

Is the document types tree hierarchy now maintained the path field of umbraco Node table? The reason I as is outlined below.

After upgrading to V6 my document Types are no longer displayed in a tree hierarchy. I've migrated from 4.9 to 6.

Document Type Tree in 4.9, nodeId in brackets Base Document (id = 123) ----> Base Article (124) --------->Reviews (125) --------->News (126)

Document Type Tree after upgrade to V 6.0 Base Document (id = 123) Base Article (124) Reviews (125) News (126)

The hierarchy is not maintained in the control panel, however in the content it is eg all News and Reviews inherit properties from Base Article and Base Doc Type.

Further examinations on the review nodes suggests it set up correctly. In the DB table cmsContentType2ContentType has review as a child and base article as the parentContentType, and ditto for base article being the child of base document. In umbracoNode the parent of both is -1 and the path is -1,126 for review and -1,124 for base Article which is same as 4.09.

Next I created a new 3 tier tree Doc Type under Base Document to see if this worked and to compare differences in the data. I ended up with Base Document (123) --->Child Type (130) -------> Grand Child Type (131) Base Article (124) Reviews (125) News (126)

So the hierarchy was created. The only difference in the DB was the field Path in UmbracoNode had the id's of all the nodes on its path so the path for Grandchild is -1,123,130,131

So is this a change in V6? Or has my upgrade been messed up?

Comments

Adrian Donnelly 26 Feb 2013, 18:23:15

ok the path field in UmbracoNode is a red herring. The reason why the tree was not maintained was because the parentid field was set to -1 for all document types. Running this script fixed it for me.

UPDATE dbo.umbracoNode SET parentID = parentContentTypeId FROM cmsContentType2ContentType ct2 INNER JOIN dbo.umbracoNode un ON un.id = ct2.childContentTypeId


Adrian Donnelly 26 Feb 2013, 18:27:30

Just to add I manually updated the DB schema with the script located U4-1353 as I could not get the install upgrade from 4.7 --> 6.0 to run smoothly.


Sebastiaan Janssen 26 Feb 2013, 18:49:47

Okay, this is in fact due to that script not being complete. :-) Closing this issue as it's fixed.


Joost Wassink 29 Oct 2013, 13:18:53

Hi Sebastian,

i have the same problem with the media section do you have de source of the fix for me?


Sebastiaan Janssen 29 Oct 2013, 20:41:28

@Joost Use the fixup tool here: http://our.umbraco.org/projects/developer-tools/path-fixup


Joost Wassink 31 Oct 2013, 08:14:36

@Sebastiaan

Thanks for your comment ,but the fix has not helped. We also did not updates from 4.7 but started with a clean instalation from 6.1. The problem is in the third level of the hierarchy. the top work correctly. You might have a different idea what it could be?


Sebastiaan Janssen 31 Oct 2013, 08:18:15

@Joost No idea, please create a new issue with steps to reproduce because I am unsure what the actual problem is.


Priority: Normal

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: