document disappears from context's resource tree, why??

What happens if you change its menuindex in the database to a low number?

I didn't see any JS errors anywhere, nothing in the logs either, but I don't think modx logs JS errors.

The other items I want in the menu are 9,30,41,50,60, 41 is for 'Files,' which is not visible...I need it in that position.

Are those menuindex values? Or do you mean you want 41 to be 2 in the menuindex.

Those are the existing menuindex values. modx configured 9, I set the other ones.

You probably tried this, but just in case -- did you manually delete all the files from the core/cache directory. And do you have compress_js and compress_css turned off in the System Settings?


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/modx.html

Tried both the above ideas, no good...Thank you, Tom [ed. note: TomMLS last edited this post 14 years, 8 months ago.]

Has any come up with a solution to this problem. I currently have this exact problem. To summarize: I have documents that are NOT showing in the Resource Tree however if you run a search the document is there.

Any Help would be great. These are the things I have already tried:

Flush All Sessions ->Manually Clear Core Cache -> Clear Browser Cache = No Change

Flush All Sessions -> Disabled Compress_JS & Compress_CSS -> Manually Clear Core Cache -> Clear Browser Cache = No Change

Flush All Sessions -> Disabled Compress_JS & Compress_CSS -> Manually Clear Core Cache -> Upgrade MODX 2.2.8-pl to MODX 2.2.8-pl -> Clear Browser Cache = No Change.

I am open to try other things as I have exhausted any idea I have.

Looking for a Solution.

Thanks, Ryan T. Kidd

So I was able to resolve this issue and here is how:

So after doing a search I pulled up the missing Document, and reviewed the document settings. I noticed that the parent for the document was the document. This of coursed cause error as a parent can not be a parent to it self. Once I correct this I simple refreshed the tree and "Bob's your Uncle"

Hope this is help for those in the future.

Ryan T. Kidd
Exceleron Designs

Hello everyone,

I'm answering to this post cause I've just had the same problem.
I started a new modx website, created new document pages ( example names: home,contact,projects,etc.) and container page with several blog containers categories ( illustration,design, etc.) with new articles in each blog category. Just for site testing, I tried to import an article from the blog container named "illustration" to another blog container named "design". Well it worked but I somehow imported not the blog articles but all the root documents pages from the document tree ! I could not see the simple documents from the document tree anymore. I discovered that the documents became articles.

So I clicked into the search above the document tree, found the document but could never move them to the root document tree. Here's how I solved the problem:

- search for the document in the search bar by entering the name of the document if you remember it
- right click on the desired document and click on " Quick Update Resource " then on the new window click on settingsand change the class key to document.
- right click again on the document and click on Edit resource and this time you will see the settings tab click on it and and change the parent resource to the one you want to by selecting a node in the tree in the left. I personally selected the root node. That's it.

Important: If you click on "Edit Resource" before doing "Quick Edit Resource" you will not see the Settings tab to change the resource class to document and you won't be able to edit the document and place it back to the tree.

Since the documents were changed to articles, their template changed too, so I had to re-change the template name and even edit the document because I am using the Flexibility theme and the slider on the homepage was not working anymore.

I am glad this happened just in the beginning! I lost some time but at least I didn't have to do that on more than ten documents ! I will not use the import articles tool again before watching some videos ( if theres any about it) or reading more about it.

I'm sure this will help someone !

Cheers!

Merry