We have moved to GitHub Issues
Created by Andy Butland 28 Sep 2013, 20:56:24 Updated by Nik 26 May 2015, 09:44:37
It looks like the tabs are being displayed in the order they have been created, and not based on the sort order field provided on the document type.
This is marked as fixed but is still an issue in the release 7.0 release. In my scenario I tested in Chrome and IE where parent document type had tab set to Sort Order: 3 and sub document type had tab added with Sort Order: 2. The tab of the parent appeared first, sort orders were ignored. I'm new to reporting bugs, not sure if I'm supposed to mark this as "open" again or just leave a comment. I took a guess and reopened, correct me if this is not correct protocol.
Hi Phill, I've just tried reproducing this on our current build, and I cannot make it do it. Have a type, inhertiting tabs from another type, I change the sort order or the tabs on both types to mix them, and it does exactly that, first tab is from child, next is from parent type, and so on, looking at the raw data, this also looks as it should.
On build 192 I still have this issue, I'll try with the latest build 199 and let you know. Master Doctype with "content" tab, sort order set to "2" Section Doctype with "section" tab, sort order set to "1" Create a page based on Section and tabs are ordered "content" then "section"
Hi Per, I tested a bit more using build 199 (although this probably applies to previous post 7.0.0 builds). You are correct in that this issue can't be reproduced if you're creating new document types using the current build. However if you have document types that were created with the final release, v7.0.0, editing the tab orders does nothing. Since it's a royal pain to try and copy and then change a doctype (basically impossible) it means that for this site I'm forever stuck with tabs in the incorrect order. Let me know if you need any more info, sample files etc as this would be a nice one to resolve.
that sounds super odd, since we store the data the same way in these builds, they you should be able to clear the content type cache by restarting the app pool, then sorting the tabs, saving, and perhabs reset the app pool again
@Per.Ploug also having this issue in 7.2.4
@Per.Ploug I think I've found some information that may help you identify this bug. I was having the same issue where child document types were displaying tabs in the wrong order. When I looked at the cmsPropertyTypeGroup table in the database there were entries representing the inherited tabs which had the wrong sort order on them. As you cannot change the sort order within the back-office on the child document types this leads me to believe that the inheritance code is not looking up the tree fully when creating new entries.
State: Can't Reproduce
Assignee: Per Ploug
Backwards Compatible: True
Affected versions: 7.0.0
Due in version: 7.0.1