Manager: Resources missing in tree after changing menu index

Hi Community,

I got a strange behaviour in my MODX (v2.3.2). After changing the menuindex on several resources some of them suddenly disappeard. I opened the edit-view by entering the URL manually. Somehow some of them got visible again after saving. But one is still missing. I tried to change menuindex and also set the parent again (which is 0) and tried to find any hints in the database table - but everything seems ok.

Any ideas?!

It's getting weird when I edit all the menuindexes – suddenly some resources disappear and some show up again … not only the one I edited, it affects all resources in the tree. Can't figure out if there is any logic behind it, but it's very crazy. It all started after installing "Articles", I guess. I really need some help on this topic!

By default, Articles resources are set to not show in the Tree, and I believe that the Articles container resource is set to not show its children in the Tree. These are all fields in the database, in the site_content table, so you can look at them there if you have to. [ed. note: sottwell last edited this post 11 years, 10 months ago.]

Thanks for the reply. I know, Articles hide their resources. That is not the problem – instead all pages on the same level like the Articles container behave like I wrote. Example:



On this very first level in the tree, some of the pages get lost in the Manager tree after changing menuindexes. So, let's say I edit "News" and change menuindex to something different, then suddenly "Contact" disappears in the tree. This did not happen before I installed and used "Articles". Any ideas on that?

I've seen MODX mess up the parent field when you drag resources around in the tree. It renumbers the menu indexes every time you move something. Under some circumstances, objects can become parents of each other or a resource can end up as its own parent. Needless to say, this messes up the tree display. It's possible that having Articles, which are in the tree, but not visible, confuses the renumbering process, especially if you drag something from one side of the Articles container to the other.

This is one possible solution: http://bobsguides.com/sitecheck-promo.html. You can also go to the DB in PhpMyAdmin and check all the parent fields for validity, but it's not much fun.

Quote from: BobRay at Nov 26, 2014, 12:10 PM

I've seen MODX mess up the parent field when you drag resources around in the tree.

Actually I used the input field and typed it manually, I did not drag&drop any resources.

Quote from: BobRay at Nov 26, 2014, 12:10 PM

It's possible that having Articles, which are in the tree, but not visible, confuses the renumbering process, especially if you drag something from one side of the Articles container to the other.

I only touched resources in the very first level, I did not move children resources to other containers.

Quote from: BobRay at Nov 26, 2014, 12:10 PM

This is one possible solution: http://bobsguides.com/sitecheck-promo.html.

Thanks, I purched that extension but it does not find any problems (by the way when I perform all tests at once I get an time out error after a while).

Quote from: BobRay at Nov 26, 2014, 12:10 PM

You can also go to the DB in PhpMyAdmin and check all the parent fields for validity, but it's not much fun.

I tried this too on resources that got lost – can't find any abnormality. Parent is set correctly, menuindex is set correctly. That's really getting frustrating right now

Thanks for purchasing SiteCheck. I'm sorry it didn't solve your problem. The timeout is normal if you run it inside MODX and you have a large site. The default PHP time limit is 30 seconds, though your host may increase it if you ask. You can also run SiteCheck outside of MODX if you have shell access.

Try deleting all files in the core/cache directory. See if that has any effect.

Did you check the show_in_tree and show_children_in tree fields while you were in the DB?

Have you tried using a different browser?

Do you have any plugins that operate in the Manager? If so, you could try disabling them.

You could also try turning off the compress_js and compress_css system settings if you haven't already.