Bug #81718

Workspace - TYPO3 MM relations are defect

Added by Mnh Thien Nhan about 2 years ago. Updated 5 months ago.

Status:
New
Priority:
Must have
Category:
Workspaces
Start date:
2017-06-27
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Scenario:

Using a workspace and create a new system category.

Problem:

  • In current workspace add categories for a content element
    • one already existing category (in the live workspace)
    • and the new created category above.
  • After save the change, only the already existing category is added, but the new category not.


Solution:

The Implementation for submitted relation uids to accordant version uids in workspace context doesn't work (see typo3/sysext/core/Classes/DataHandling/DataHandler.php) and it must be removed.

workspaceoverview.png View (76.6 KB) Mnh Thien Nhan, 2017-06-27 17:32

updatecontent.png View (61.8 KB) Mnh Thien Nhan, 2017-06-27 17:32

formCategoriesSelected.png View (83.7 KB) Mnh Thien Nhan, 2017-06-29 17:45

newCategoriesInWS.png View (106 KB) Mnh Thien Nhan, 2017-06-29 17:45


Related issues

Related to TYPO3 Core - Bug #77375: MM references are not transformed to versioned entities Closed 2016-08-03

History

#1 Updated by Mnh Thien Nhan about 2 years ago

  • TYPO3 Version changed from 7 to 9
  • PHP Version changed from 5.5 to 7.0

#2 Updated by Mnh Thien Nhan about 2 years ago

  • Related to Bug #77375: MM references are not transformed to versioned entities added

#3 Updated by Gerrit Code Review about 2 years 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/53340

#4 Updated by Oliver Hader about 2 years ago

It might be, that this is rather a view issue than some persistence issue. Did you check that in FormEngine already?

#5 Updated by Mnh Thien Nhan about 2 years ago

I have checked that in FormEngine and it has the same result. (see screenshots below)


#6 Updated by Anja Leichsenring over 1 year ago

  • Status changed from Under Review to New

#7 Updated by Franz Koch over 1 year ago

I'm having a similar issue. I created a new record in the workspace and referenced it in another record in a multi-select field via MM. While the relation is persisted in the MM table, it contains the wrong UID. The MM table contains the UID of the workspace version and not the one of the dummy record. Once I adjust the UID accordingly in the MM-table directly in the DB, the relation shows correctly in the backend. I suspect that the issue of the user is based on the same bug. My bug was tested with TYPO3 7.6.29 - can't tell if it's fixed in newer versions.

#8 Updated by Benni Mack 5 months ago

  • Target version changed from next-patchlevel to Candidate for patchlevel

Also available in: Atom PDF