Bug #24882
closed
pagetree->expand branch does not work as expected
Added by Rupert Germann almost 14 years ago.
Updated about 6 years ago.
Description
When I click "expand branch" in the new pagetree once it simply expands the next level und the page where I opened the context menu.
When I click the same context menu link (at the same page) a second time it expands all pages on all levels below the page where I clicked.
I'd expect the tree either doing the first OR the second action but not 2 different actions on the same useraction.
I suggest to remove this option completely (or make it removable by configuration) because expanding ALL pages in a huge pagetree does not make much sense in real live and it puts a VERY HIGH LOAD on the server.
Additionally it leads to other errors - see linked bug.
(issue imported from #M17394)
Files
Strange... ExtJS handles the expansion of the node with all subnodes. Sounds like digging again into the library code. :-/
About performance: Sure, but if then you would need to remove the filter feature for huge trees too. The removal of this actions is not that difficult and can be done by some user/group typoscript.
hi Stefan,
thanks for diggin' ;-)
hiding the filter can be done with:
options.pageTree.hideFilter
but can you give me a hint how to hide the expand/collapse branch buttons?
the pagetree wikipage doesn't mention them (http://wiki.typo3.org/Pagetree):
options.contextMenu.table.pages.disableItems
* [String] Comma-separated list of items that should be disabled from the contextmenu
It's straight forward, because you just need to use the action names configured in the config_default.php. Unfortunatly the documentation list the old context menu action names. Sorry!
options.contextMenu.table.pages.disableItems = expandBranch, collapseBranch
I am not able to reproduce this bug, so its difficult to review. I click on "Expand branch" and it expands all pages in the subtree recursively, which is what I expected. Does it also affect current master or only 4.5?
Hi Ernesto,
See my comment @gerrit
This bug is very clear if you look into the code and should be work for 4.5 and master.
- Target version deleted (
4.5.3)
- Status changed from Resolved to Closed
Also available in: Atom
PDF