Bug #18284
closed
Page tree fails to reload properly if page was manipulated
Added by Andreas Beutel almost 17 years ago.
Updated over 14 years ago.
Description
The page tree fails to reload if a page is copied and pasted or moved (by cut and paste). Appears either in list-view or normal page-view.
Select List from the Web menu, select a page in the tree and choose »copy« from the contexual menu. Select another page and insert via the »Past in clipboard content« on the right. The tree frame is refreshed but empty. The same if you do this in »page« mode and insert via contextual menu (insert via »Paste into«): The tree frame will reload but show »Web>Page module
Please click the page title in the page tree to the left to edit page content.« instead of the tree.
Tested in Firefox 2.x and 3.x and Safari on a Mac.
(issue imported from #M7637)
Files
I can confirm this issue. The page tree is also broken, when new pages are created (see attached screenshot, I've created page "7634").
this happens also when you create a page and change the page type, after the reload.
Pagetree shows following url:
alt_db_navframe.php??currentSubScript=sysext%2Fcms%2Flayout%2Fdb_layout.php
Please test the attached patch. I just changed location.href to location.search which will only modify the query params.
Hm, here are some URLs of the page-tree frame:
Fresh logged in: /typo3/alt_db_navframe.php??currentSubScript=sysext%2Fcms%2Flayout%2Fdb_layout.php
After reload action: /typo3/alt_db_navframe.php?randNum=1203780428754
I don't exactly know in what cases currentSubScript is used but I guess it should also be there after the update event, e.g. like this:
/typo3/alt_db_navframe.php?currentSubScript=sysext%2Fcms%2Flayout%2Fdb_layout.php&randNum=1203780428754
The new patch preserves the query parameters and just modifies the "&randNum=" part. Furthermore the "??" was eleminated (it was there a long lime)... ;-)
For those asking themself what in rev. 3263 caused this behaviour:
before: top.content.nav_frame.refresh_nav();
after/current: top.content.nav_frame.Tree.refresh();
patch works excellent ;-)
Can confirm: With patch applied the tree (re)-loads as expected.
Committed to TYPO3_4-2 (rev. 3289)
Also available in: Atom
PDF