Project

General

Profile

Actions

Bug #27212

closed

Recycler: Pagetree not refreshed after undeleting a page/pagetree

Added by Stefan Neufeind over 13 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-06-04
Due date:
% Done:

0%

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

Description

How to reproduce:
Create a page, delete it, use recycler to undelete it.

Needs manual refresh of pagetree.

Tested against master (TYPO3_4-6)

Actions #1

Updated by Chris topher over 13 years ago

  • Project changed from 147 to TYPO3 Core
Actions #2

Updated by Chris topher over 13 years ago

  • Subject changed from pagetree not refreshed after undeleting a page/pagetree to Recycler: Pagetree not refreshed after undeleting a page/pagetree
  • TYPO3 Version set to 4.3
Actions #3

Updated by Chris topher over 13 years ago

  • TYPO3 Version changed from 4.3 to 4.6
Actions #4

Updated by Alexander Opitz over 10 years ago

  • Status changed from New to Needs Feedback
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.4)?

Actions #5

Updated by Stefan Neufeind over 10 years ago

  • Status changed from Needs Feedback to Accepted

Re-tested on current master (pre-6.3). Still an issue.

Actions #6

Updated by Michael Oehlhof almost 10 years ago

In current master (7.1.0-dev) this is fixed.
After recovering of a page with the recycler, the page tree is updated and the beforehand deleted page is shown at the place where it was before deleting.

Actions #7

Updated by Wouter Wolters almost 10 years ago

  • Status changed from Accepted to Closed
Actions #8

Updated by Stefan Neufeind almost 10 years ago

Looking at the sources this seems to have been fixed in master with: http://review.typo3.org/36109, commit 4e4180496d6ad7a5a5b9e83f312e3cc8a9e2c270
where EXT:recycler was "revamped". So the question is whether we want to fix this on 6.2 somehow (digging into the old sources) or maybe forget about it :-)
For me personally it's not too important, so I'd be fine to close the issue as "fixed in CMS 7".

Actions

Also available in: Atom PDF