U4-7298 - After Upgrade 7.3 Content Sort Orders are Changed

Created by Tim Payne 23 Oct 2015, 09:02:08 Updated by Tim Payne 23 Oct 2015, 10:08:11

After upgrading to 7.3 (from an older 4.7.2 site), I noticed that the sort order of the content nodes are all wrong. This is throughout the content tree. So for example, on the original site, three nodes have the order of 1, 2, 3, but after the upgrade, the nodes have been updated to 9, 6, 7.

We ended up having to go through and re-order all of the content nodes so that they matched the original ordering, which was a bit of a pain, as the site had 7000 nodes. I'm going to have a dig into the source at some point and see if I can work out what's going on, I presume this must be something that happens as part of the database migrations though.

I suspect this issue may be related to this one that I spotted as part of the same upgrade: http://issues.umbraco.org/issue/U4-7199

Comments

Sebastiaan Janssen 23 Oct 2015, 09:37:17

It could very well be due to our sorting always having been pretty buggy, were some or multiple items would get the same sort order as others. If you still have a db backup from before the upgrade you could check the sort orders. I don't think we really do anything with sorting in the migrations but I can't remember exactly.


Tim Payne 23 Oct 2015, 09:49:45

I've got the original backup, and as far as I can see, the sort order were correct before the upgrade. If I do a select of one of the affected levels, everything has the correct order. However, after the upgrader has been run the numbers have been bumped up, and they're in the wrong order. I might be able to get you a backup of the DB if you want to test it yourselves?

I've looked through the Migrations code, but I can't see anything that would update the content orders, which is odd.


Tim Payne 23 Oct 2015, 10:07:56

OK, having checked through some backups of the database, this issue wasn't caused by the upgrade, but by moving some content (I think)? Orders were OK after the update, but after some content was moved, the orders were broken for everything underneath the moved node. Will investigate further, and raise a separate bug.


Priority: Major

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 7.3.0

Due in version:

Sprint:

Story Points:

Cycle: