U4-5247 - Tab sort order seems to be ignored

Created by Damian Green 19 Jul 2014, 15:18:10 Updated by Shannon Deminick 26 Jun 2017, 07:15:14

Is duplicated by: U4-5382

Relates to: U4-5769

Relates to: U4-5845

I have some inherited tabs and the sort order is ignored and the tabs seem to be displayed in the order of the hierarchy when adding content.

Seems similar to U4-2980 but this is the latest version with a clean database and new doc types created from scratch.

Nav Tab on base node type - set to 40 Content tab on ContentPages (inherits from Base) node set to 1

Homepage inherits from ContentPages

Navigation tab is coming first

if i set content tab to 0 it goes infront of the navigation If i set it back to 1 navigation comes the front again

Something amiss.

1 Attachments

Comments

Markus Johansson 31 Jul 2014, 09:58:25

Could not be so hard to fix @sebastiaan will we see this included in upcomming patches?


Chris Evans 10 Oct 2014, 17:54:40

I'm noticing a similar type of problem in 7.2.0 build 162 -- seems to be totally ignoring the changes I make to tab sort order on a document. I change the values either manually or by dragging the tab items, and when I hit save on the document type they just bounce back to the original created-order values.


Nicholas Westby 11 Nov 2014, 22:37:22

I can confirm this is still an issue in Umbraco 7.1.8. I have a parent document type with a tab that has a sort value of 10. And I have a child document type with a tab that has a sort value of 0. The tab with sort 10 appears before the tab with sort 0.


Nicholas Westby 11 Nov 2014, 22:42:25

To add some more info, the tab order is wrong on one node, but correct on another node (each node uses a different doctype). The node with the incorrect order has an intermediate doctype that adds some properties to the tab on the parent doctype. Also, that tab used to exist on that intermediate doctype, but I moved it up to a parent at one point (which also caused some errors, though that may have had more to do with the fact that the intermediate doctype had properties that also existed on the parent doctype).


Nicholas Westby 05 Jan 2015, 22:41:49

I added a comment to another issue, but it's a duplicate of this issue, so I'm adding the comment here too...

FYI, I'm thinking this may be because tabs aren't fully deleted from the database when they are deleted from the UI. At some point, I moved the tab "SEO" from "Public Page" to the parent document type, "Page". When I view "Public Page" in the "Settings" section of Umbraco, I don't see the SEO tab (as I'd expect). However, when I run a database query, it seems that tab still exists in the database:

!tabs.png!


Sebastiaan Janssen 06 Jan 2015, 14:59:46

Just as a warning: It is dangerous to edit this in the database directly, please please please make backups before you do anything directly in the database.


Nicholas Westby 06 Jan 2015, 15:11:39

Yeah, I figured properties may still be linked to the cmsPropertyTypeGroup table, so I opted to change the "sortorder" field rather than delete any rows (still a database modification, but I would think a relatively innocuous one).


Dennis Öhman 13 Apr 2015, 08:55:47

We are experiencing the same thing. Properties have a similiar problem, shouldn't inherited properties always come first?

Example:

-'''Root''' (''DOCTYPE'') -* '''SEO''' (''TAB'') -# '''Title''' (''PROP'') -# '''Description''' (''PROP'') -* '''CONTENT''' (''TAB'') -*# '''Headline''' (''PROP'')

-'''Page''' (''DOCTYPE'') (inherits Root) -'''CONTENT''' (''TAB'') -#'''Modules''' (''PROP'')

Will render:

  • '''CONTENT''' *# '''Modules''' *# '''Headline'''
  • '''SEO''' *# '''Title''' *# '''Description'''

Should render:

  • '''SEO''' *# '''Title''' *# '''Description'''
  • '''CONTENT''' *# '''Headline''' *# '''Modules'''


Heather L Floyd 07 Oct 2015, 17:13:40

I encountered a similar issue, but figured out a solution. Info here: https://our.umbraco.org/forum/umbraco-7/using-umbraco-7/58018-We-need-to-talk-about-Compositions#comment-231168

I have also included a theory as to why this happens.


Shannon Deminick 26 Jun 2017, 07:15:15

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Major

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.1.4, 7.1.8

Due in version:

Sprint:

Story Points:

Cycle: