Project

General

Profile

Actions

Bug #50416

closed

Epic #53915: Usability and timing issues in Pagetree

Deleting a page from the pagetree context menu should reload the pagetree.

Added by Tobias Klepp almost 11 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Pagetree
Target version:
Start date:
2013-07-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

The following actions happen (recursive deletion is disabled in the user settings):
1. Create a parent page.
2. Create a child page.
3. Enter content element on the pages.
4. Delete the child page using the context menu.
5. Try to delete the parent page, but the delete action is not available.
6. Reload the page tree: The delete action is available.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #25068: New page tree: delete page is not visibleClosed2011-02-17

Actions
Actions #1

Updated by Philipp Gampe almost 11 years ago

  • Status changed from New to Accepted
  • Target version changed from 6.2.0 to next-patchlevel
Actions #2

Updated by Ernesto Baschny over 10 years ago

  • Parent task set to #53915
  • Is Regression set to No
Actions #3

Updated by Mathias Schreiber over 9 years ago

  • Subject changed from Delete page in context menu only after page tree reload to Deleting a page from the pagetree context menu should reload the pagetree.
  • Target version changed from next-patchlevel to 7.4 (Backend)
Actions #4

Updated by Susanne Moog almost 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #5

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 8 LTS
Actions #6

Updated by Riccardo De Contardi over 8 years ago

  • Status changed from Accepted to Closed

Both I and G. Martino were not able to reproduce the problem with the given instructions in both 6.2.17 and the latest master (8.0-dev), so I close this for now.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
You could also join the #typo3-cms channel in Slack if you still need support.
Thank you

Actions

Also available in: Atom PDF