Hi All,
I'm working on a Revo 2.5.0 install and for some reason, the children resources under a parent change their sort order in the managerresource tree every time I refresh it (we have about 80 children under this parent, so it's getting quite confusing).
Anyone else ever seen this / have any ideas on how to fix? Let me know!
[ed. note: presson83 last edited this post 10 years, 2 months ago.]
Hi Nick,
we experienced the same behaviour on a Revo 2.5.0 installation. Never found the reason for this. Looking for a solution, too.
Hi all,
I've never see this trouble but i've you check context_tree_sortby and context_tree_sortdir settings ?
Try changing context_tree_sortby to "key" (without the quotes), "menuindex" or "pagetitle". One of those should give you something you can work with.
My 2.4.2 install has context_tree_sortby set to key. The order is consistent and I can drag them in the tree and they stay where I put them.
I think the issue may be that your resources don't have a value in their 'rank' field -- there's no 'rank' field for resources in 2.4. Or maybe old resources don't have a rank but new ones do. I don't have a local 2.5.x version to check, but if resources have a rank field, it's new, and existing resources wouldn't have it set.
We also had this problem back on a version of Revo 2.3. Never solved it but never had it before or since. We posted on the forums and tried all sorts of solutions - include rank and sort by. No joy for this particular site. But we've never had it since. Your site sounds biggish Future FOrward - but if Bob's solutions don't work & you have the time, reinstall Modx, replicate the resource tree, check it works, copy the content. Not a nice job, so for our site in question, we just had to live with it.
if you have many resources in the tree, collections might help to keep them organized and listed in your prefered order.
After having exactly the same problem with child resources getting shuffled on every page refresh tried the suggestion of setting context_tree_sortby from "rank" (which it was by default) to "key" and that seems to have put an end to the shuffling. A solution. Thanks to Steeve and Bob for suggesting it.