Bug #61719

Epic #58282: Workspaces Workpackage #2

Story #58284: Bug fixes & Behaviour

Warnings on flushing whole workspace with localizations

Added by Oliver Hader about 7 years ago. Updated 12 months ago.

Status:
Closed
Priority:
Could have
Assignee:
Category:
Workspaces
Target version:
-
Start date:
2014-09-18
Due date:
% Done:

100%

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

Description

Flushing a whole workspace in the workspace, which contains record localizations, shows warnings like this in the workspace module:
Attempt to reset workspace for record failed: No record

The reason for that is simple, the record already has been flushed since it's a localization.

Thus, either the warning can be omitted by tracking already processed elements or record localizations need to be processed before the default record.


Related issues

Related to TYPO3 Core - Bug #62155: IRRE at localized records not working properly with Extbase/Fluid Rejected2014-10-10

Actions
Related to TYPO3 Core - Bug #91881: Massive load when deleting sys_workspace record on pid 0Closed2020-07-28

Actions
Related to TYPO3 Core - Bug #69310: Attempt to reset workspace failedClosed2015-08-25

Actions
#1

Updated by Mathias Schreiber over 6 years ago

  • Target version set to 7.5
#2

Updated by Oliver Hader almost 6 years ago

  • Target version changed from 7.5 to 7 LTS
#3

Updated by Mathias Schreiber almost 6 years ago

  • Target version deleted (7 LTS)
#4

Updated by Christian Kuhn about 1 year ago

In master / v11, there are no warnings in the workspace module itself, only db logs. However, the issue itself is still reproducible and does not even need record translations:

  • Have a workspace set up on page 0
  • Switch to this workspace
  • Create a new page in this workspace
  • Add a content element on this page
  • Go to workspace module, select 'all' button or select both the page and the record
  • Second drop-down "Choose selection action" -> Discard (page and content element are thrown away)

-> This creates one log entry in the log table:

  • System -> Log module, filter action "Database" -> See "Attempt to reset workspace for record failed: No record"

Reason: Sending action 'clearWSID' (to throw away ws records) sends both the page and the content element. The page record is deleted first, which deletes the content element as well. The call to delete the content element then creates the log entry.

Note this not only happens if deleting a page that has a content element (or other record), but also if having a page with a sub page and discarding both through the workspace module.

#5

Updated by Gerrit Code Review about 1 year ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65132

#6

Updated by Gerrit Code Review about 1 year ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65132

#7

Updated by Christian Kuhn about 1 year ago

  • Related to Bug #91881: Massive load when deleting sys_workspace record on pid 0 added
#8

Updated by Christian Kuhn about 1 year ago

  • Related to Bug #69310: Attempt to reset workspace failed added
#9

Updated by Gerrit Code Review about 1 year ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65132

#10

Updated by Gerrit Code Review about 1 year ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65132

#11

Updated by Gerrit Code Review about 1 year ago

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65106

#12

Updated by Christian Kuhn about 1 year ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#13

Updated by Benni Mack 12 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF