Project

General

Profile

Actions

Bug #97220

closed

Extbase is not fully workspace aware in backend context

Added by Torben Hansen over 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2022-03-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Stabilization Sprint

Description

When data is fetched from an extbase repository in backend context, it is not respected that the query should also respect the current workspace the backend user is working on.

Prerequisites:

  • Extbase repository (ignore storage page) and a domain model

How to reproduce:

  • Create a new record for the domain model
  • Use the repository in FE context and use findAll()
  • One record will be returned -> this is correct
  • Switch to a workspace
  • Create another record for the domain model
  • Use the repository in FE context and use findAll()
  • Two record will be returned -> this is correct
  • Switch to live workspace
  • Use the repository in FE context and use findAll()
  • Two record will be returned -> this is not correct since the hew record created in the workspace is not published

The function getBackendConstraintStatement should add constraints for t3ver_state and t3ver_wsid constraints (see https://github.com/TYPO3/typo3/blob/main/typo3/sysext/extbase/Classes/Persistence/Generic/Storage/Typo3DbQueryParser.php#L738) depending on the workspace the user is working in.

Actions #1

Updated by Torben Hansen over 2 years ago

  • Description updated (diff)
Actions #2

Updated by Benni Mack over 1 year ago

  • Sprint Focus set to Stabilization Sprint
Actions #3

Updated by Tomek W over 1 year ago

I'm unable to reproduce issue on main branch

Actions #4

Updated by Benni Mack about 1 year ago

  • Status changed from New to Needs Feedback
Actions #5

Updated by Torben Hansen about 1 year ago

  • Status changed from Needs Feedback to Closed

Closing issue, since I'm also not able to reproduce the problem any more.

Actions

Also available in: Atom PDF