Tree not sorting

I’m on 0.9.6 and the document tree is "stuck" in docid sort order. What’s more, is that this is somehow affecting Wayfinder...the menus are sorted now by docid and not menuindex. I’ve used DocManager to sort the items, and in fact, the menuindex of each document is correct, but the docs are still sorted by docid. When I’ve tried to resort the doc tree, it’s not budging. Any ideas?

This is a result of a nasty bug in MySQL 5.0.51, which is apparently making into a large number of production hosting environments recently. Do a Google search on "site:modxcms.com/forums MySQL 5.0.51" and you will see a number of posts covering this problem.

hmmm, I don’t think that’s my problem. I’ve got 5.0.22 in production, but 5.0.41 on my local dev, where everything works fine. Any other ideas?

Not that I have a solution, but I had a similar experience I posted here. It was unsorted for about 1/2 a day but ever since then it’s sorted perfectly fine. Very strange. I’m not sure which version of MySQL I’m running on.

Hope you can figure out what’s causing it.

Quote from: MacLonghorn at Jun 23, 2008, 01:10 PM

hmmm, I don’t think that’s my problem. I’ve got 5.0.22 in production, but 5.0.41 on my local dev, where everything works fine. Any other ideas?

Is that the MySQL client or server version? The client version could be 5.0.22 and the server could still be 5.0.51.

It’s the server:

[root@cp ~]# mysql -V
mysql Ver 14.12 Distrib 5.0.22, for redhat-linux-gnu (i686) using readline 5.0

Also, phpMyAdmin says ’5.0.22’ I’m a bit worried as the site is in production already and this just showed up.

I’ve never seen anything like that other than when 5.0.51 was involved...anyone else have an idea?

Maybe check the tables in phpmyadmin...all I can think of.

Can you point me in the right direction so I can put in a temporary fix? ie, I need to get Wayfinder to display the menu items in the proper order, by menuindex. What file and/or lines of code should I be looking at?

Thanks.

Like I said, never seen anything like this, so not sure how I can recommend a fix. We need to identify what changed on your server; did you add a component or did any other incident occur? You’re going to have to help us identify what is different from when it was working...

I manage the box, so nothing changed with the environment, software, services, or code. The last change made that was a little abnormal was this:

We duplicated a doc to test some changes. I have auto-alias turned on, duplicates allowed (we’re using paths in URLs) so it created the alias. When we made the changes, instead of deleting the original doc, we just renamed the doc’s alias. So at one time we duplicate aliases but I immediately changed that. The old page was still coming up, so I had to delete the original doc and refresh the cache. It was still fine at that point though. The client made a few more changes afterward but everything was still fine. Sometime over the weekend it just started screwing up. Maybe there’s still a duplicate alias in there that’s causing problems?