Document Tree Not Fetching Children [FIXED!]

@BobRay - I’m identical EXCEPT for php. That’s version 5.2.9 for me.

I was under the impression that php5 was a requirement for Evo 1.x - but I can’t seem to locate modx install requirements - so I may be making that up.

EDIT:
I Tried downgrading to PHP 4.4.9 (my only option on that front) and things behaved the same way.

(Thanks for the Help by the way.)

Does that mean that you are on the Endor server there too? It is currently being moved to a new box, although I can’t imagine why that would cause this problem.

Sorry - not on Endor. No movement here. This problem is spread about on installations on 4 different servers.

Anybody suppose this is a javascript thing?

I thought it might be the permissions on some js file, but all folders are set to 755 and files to 644 as they should be.

There are no JS errors in Firebug. I think that repeating message you see in Safari is a little "keepAlive" function unrelated to our problem. I see something similar in Firebug but with no error.

I think the relevant code is pulled in with this line:

<frame name="tree" src="index.php?a=1&amp;f=tree" scrolling="no" frameborder="0" onresize="top.tree.resizeTree();">

The file is manager/frames/tree.php and it contains a toggleNode() function (a mixture of JS and PHP) that looks like the culprit but my JS is too feeble to investigate further.

BTW, I remembered that I have a copy of the site on localhost and, of course, the error doesn’t happen there.

Found the problem... actually a bug!

The javascript at work in manager/frames/tree.php is looking for a <div> in the node code - placed there by nodes.php

End of line 167 in nodes.php (v1.01)
End of line 169 in nodes.php(v1.0.2)


Replace with


(You’re adding <div style="display:none;"></div>)


At the Moment it’s a ’core hack’ but it does the trick.


Credit to ’kosh_003’ for the mad skills.

Cool. I’m not finding any code like that in the 0.9.6 version (though I should update anyway).

Thank you for the fix! I had an install on Lunarpages as well that was experiencing this same weird behavior. See: http://modxcms.com/forums/index.php/topic,46106.0.html

That is one weird bug. It occurs in 0.9.6 and in 1.0.2 and with both PHP4 and Php5. Why this should happen only at Lunarpages is beyond me since the JS is client-side.

BTW, anablepo, could you report this using the Jira link at the top of this page so it doesn’t fall through the cracks?

Thanks again.

Thanks for posting this fix; was driving me nuts as to why it was working fine on a different test server and not on Lunarpages. Was still having this problem with v1.0.3 and seems like the line to edit has moved to 178, for those keeping score.