Feature #1834
closed
Recycler: Integrate Lost+Found possibilites
0%
Description
- 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.
Updated by Francois Suter almost 16 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.
Updated by Oliver Hader almost 16 years ago
- Target version set to TYPO3 4.3 alpha2
Updated by Julian Kleinhans almost 16 years ago
- Target version changed from TYPO3 4.3 alpha2 to TYPO3 4.3 beta
Updated by Chris topher over 13 years ago
- Project changed from 147 to TYPO3 Core
- Target version deleted (
TYPO3 4.3 beta)
Updated by Chris topher over 13 years ago
- Subject changed from Integrate Lost+Found possibilites to Recycler: Integrate Lost+Found possibilites
- TYPO3 Version set to 4.3
Updated by Alexander Opitz over 11 years ago
- Category set to Recycler
- TYPO3 Version changed from 4.3 to 6.2
Updated by Philipp Gampe over 11 years ago
I guess this can be retrieved via the reference index.
Updated by
Updated by Andreas Fernandez over 9 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.
Updated by Riccardo De Contardi over 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Susanne Moog almost 7 years ago
- Target version changed from 9.0 to 9 LTS
Updated by Susanne Moog about 6 years ago
- Target version changed from 9 LTS to Candidate for Major Version
Updated by Christian Kuhn over 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.