Project

General

Profile

Actions

Feature #1834

closed

Recycler: Integrate Lost+Found possibilites

Added by Oliver Hader over 15 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Recycler
Start date:
2008-10-26
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Imagine a record is still available in the database and not marked as deleted (deleted=0). However the accordant parent element was deleted (removed completely or marked as deleted). These parent elements could be:
  • a page (direct parent or any other page ancestor) that was deleted
  • a default language record that was deleted (translated records, e.g. spanish, are not marked as deleted)

All these records with no correct reference to an existing resource should be displayed as "Lost+Found" with the possibilites to delete them as well or to move the to another page.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #1835: Recycler: Integrate recursive recoveringClosedOliver Hader2008-10-26

Actions
Related to TYPO3 Core - Bug #3004: Recycler: Versioned records are not handled by recyclerClosed2009-03-30

Actions
Actions #1

Updated by Francois Suter over 15 years ago

Actually the thing with the translations getting "lost" when the parent record is deleted should be considered a bug. I actually reported 4 years ago:

http://bugs.typo3.org/view.php?id=539

At that time I didn't have the necessary knowledge of TYPO3 to propose a patch. In the meantime I forgot about it, but I plan to try and make it in time for 4.3 if the implications are not too complicated.

That being said I agree with the general idea of lost+found listing.

Actions #2

Updated by Oliver Hader about 15 years ago

  • Target version set to TYPO3 4.3 alpha2
Actions #3

Updated by Julian Kleinhans about 15 years ago

  • Target version changed from TYPO3 4.3 alpha2 to TYPO3 4.3 beta
Actions #4

Updated by Chris topher almost 13 years ago

  • Project changed from 147 to TYPO3 Core
  • Target version deleted (TYPO3 4.3 beta)
Actions #5

Updated by Chris topher almost 13 years ago

  • Subject changed from Integrate Lost+Found possibilites to Recycler: Integrate Lost+Found possibilites
  • TYPO3 Version set to 4.3
Actions #6

Updated by Alexander Opitz almost 11 years ago

  • Category set to Recycler
  • TYPO3 Version changed from 4.3 to 6.2
Actions #7

Updated by Philipp Gampe over 10 years ago

I guess this can be retrieved via the reference index.

Actions #8

Updated by Mathias Schreiber about 9 years ago

  • Target version set to 8 LTS
Actions #9

Updated by Andreas Fernandez over 8 years ago

Lost+Found sound like a good idea. As Philipp mentioned, I guess we can use the reference index for this. However, I think we need to rebuild and declutter the GUI, I don't see such elements in the list of deleted records.

Actions #10

Updated by Oliver Hader over 8 years ago

  • Status changed from New to Accepted
Actions #11

Updated by Riccardo De Contardi about 7 years ago

  • Target version changed from 8 LTS to 9.0
Actions #12

Updated by Susanne Moog about 6 years ago

  • Target version changed from 9.0 to 9 LTS
Actions #13

Updated by Susanne Moog over 5 years ago

  • Target version changed from 9 LTS to Candidate for Major Version
Actions #14

Updated by Christian Kuhn about 2 years ago

  • Status changed from Accepted to Closed

Hey.
I hope it's ok to close this ancient issue for now: Usually, if records are set to deleted via DataHandler, the DH takes care that child pages and child records are deleted, too. In case that fails, this of course leads to a data inconsistency. However, I don't think it's the task of the recycler to manage this kind of stuff - the recycler should assume DB consistency is given and should not be a tool to "repair" broken a DB. This could instead happen on a different level .. see https://github.com/lolli42/dbdoctor for such an approach.

Actions

Also available in: Atom PDF