Project

General

Profile

Actions

Bug #105655

closed

"Collapse all tree items" doesn't persist all pages as closed

Added by Sebastian Michaelsen 4 months ago. Updated 3 months ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Pagetree
Target version:
-
Start date:
2024-11-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

How to reproduce

  • Expand a few nested pages
  • Use “Collapse all tree items” in the kebab menu above the page tree => everything is collapsed
  • Use “Reload the tree from server” => some pages are expanded again

Why is that?

The page tree sends individual Ajax requests to the server to save the collapsed state for each page. These run at the same time, the last request "wins", saves its one page as closed and overwrites everything the other requests have written. Instead there should be one request that resets the BackendComponents.States.Pagetree object.

Affected versions

I'm experiencing it with our TYPO3 v12 installation and I confirmed the behaviour with https://demo.typo3.org/typo3/ which also runs v12. At the moment I don't have a v13 installation at hand to test it there. If you can reproduce it with v13, feel free to update the TYPO3 version of this ticket.

Actions #1

Updated by Garvin Hicking 4 months ago

  • Status changed from New to Needs Feedback

While I could reproduce this in v12, I could not in v13. Which is good, because the pagetree has been redone there.

Due to the "old tree" being no longer actively maintained and v12 being in "priority bugfix"-mode, it is a bit unlikely this can get addressed.

Could you maybe see if you can also not reproduce this in v13 to be sure that the issue is fixed for current stable versions?

Actions #2

Updated by Christian Kuhn 3 months ago

  • Status changed from Needs Feedback to Rejected

Hey. I hope its ok to reject here: This seems to not happen in rewritten BE page tree in v13 anymore and its unlikely to be fixed in v12 as stated by Garvin already. We could reopen in case this is deemed important enough for v12 and if anyone picks it up, but I'll keep it closed in the more likely case this does not happen.

Actions

Also available in: Atom PDF