TYPO3 Core

I know this Bug and propose to adapt the treeview from the new tt_news extension to the core-treeview.
Furthermore the default value for open/closed has to be open, so that faults in treeview don't hide necessary options.

I could not reproduce in Firefox 3.5. Do you get any JavaScript errors? What does the AJAX response tell (this can be debugged using the Firebug extension for Firefox)?

I just solved this:
I was using a symbolic link to my typo3 folder so I could easily upgrade versions. This seems to have made ajax unhappy.
The function in the ext-all.js file that was complaining was this:
from the function: Ext.util.JSON
in the function doDecode():
the line: return eval("(" + json + ")")
was returning only () because the json variable wasn't being populated.

So I moved the typo3 folder back to the root and killed the symbolic link and blam! it works.

Is there a good way to do the symbolic link thing? I find it way nicer for upgrading. Thanks for your help guys.

I have just experienced the same problem with 4.3.0.

I'm on Mac OS X and I use MAMP. My browser is Chrome. Normally MAMP is installed in the dir /Applications/MAMP. However I have multiple MAMP installations, so I have named them /Applications/MAMP_mysite and the second installation /Applications/MAMP_othersite. Then I have a symlink /Applications/MAMP that points at the active site that I'm working on, e.g. /Applications/MAMP_othersite.

The symlink somehow affects the page-tree within the TYPO3 backend, so that it cannot expand pages.

If I remove the symlink and rename /Applications/MAMP_othersite to /Applications/MAMP then I can expand pages again.

Would be nice if the page-tree wasn't sensitive to symlinks.