Bug #3004

Recycler: Versioned records are not handled by recycler

Added by Steffen Müller almost 10 years ago. Updated about 3 years ago.

Status:
Accepted
Priority:
Must have
Assignee:
-
Category:
Recycler
Target version:
-
Start date:
2009-03-30
Due date:
% Done:

0%

TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Records which have been created with versioning are not handled by the recycler.

Steps to reproduce:
- create page
- create a new version of the page
- delete page
- go to recycler module and delete page.
- go to phpmyadmin (or similar) and find the versioned records

The same with pagecontent.


Related issues

Related to TYPO3 Core - Feature #1834: Recycler: Integrate Lost+Found possibilites Accepted 2008-10-26
Related to TYPO3 Core - Feature #27682: Recycler - Workspace Support including deleted pages in workspace New 2011-06-24

History

#1 Updated by Chris topher over 7 years ago

  • Project changed from TYPO3 Recycler to TYPO3 Core

#2 Updated by Chris topher over 7 years ago

  • Subject changed from Versioned records are not handled by recycler to Recycler: Versioned records are not handled by recycler
  • TYPO3 Version set to 4.3

#3 Updated by Alexander Opitz almost 6 years ago

  • Status changed from New to Needs Feedback

Can you reproduce this problem with a more recent TYPO3 Version (4.5, 4.7 or 6.0)?

#4 Updated by Steffen Müller almost 6 years ago

ATM I don't have a system with versioning at hand. Long time ago :)
I started a new instance from typo3_src-master, but it does not show versioning although sysexts are installed.
Is there anything I have to do to activate versioning in backend?

#5 Updated by Alexander Opitz almost 6 years ago

There are two ways:

- Disabling Workspace Extension
- Add a Workspace to get Versions of records.

#6 Updated by Steffen Müller almost 6 years ago

I can reproduce with current master rev. 932f1dd

Steps to reproduce:
  • Disable Workspace Extension
  • Create page
  • Create content element on page
  • Create a second version of content element
  • Delete content element in recycler
Result:
  • The second version of content element can be found in the DB
Expected result:
  • Second version is deleted in DB.
OT Sidenote: Versioning without workspaces seems to be broken:
  • Creating versions of pages leads to Fatal PHP Error
  • Switching between versioned content elements denied because of relation problems
    But these issues are not related here and will go into separate issues. It's just a notice to have that in mind when reproducing the original issue.

#7 Updated by Alexander Opitz over 5 years ago

  • Status changed from Needs Feedback to Accepted
  • TYPO3 Version changed from 4.3 to 6.1

Ok, thanks for helping.

#8 Updated by Alexander Opitz over 5 years ago

  • Category set to Recycler
  • TYPO3 Version changed from 6.1 to 6.2

#9 Updated by Mathias Schreiber about 4 years ago

  • Target version set to 7 LTS
  • Is Regression set to No

#10 Updated by Riccardo De Contardi over 3 years ago

It is still present.
I tested it on both 6.2.15 and 7.5-dev (latest master), using a page as record to version and delete.

what about a task (in db check?) that cleans up the DB removing the records whose "t3ver_oid" does not match any "uid" ?

#11 Updated by Mathias Schreiber about 3 years ago

  • Target version deleted (7 LTS)

#12 Updated by Riccardo De Contardi about 1 year ago

  • Related to Feature #27682: Recycler - Workspace Support including deleted pages in workspace added

Also available in: Atom PDF