Bug #81718
closed
Workspace - TYPO3 MM relations are defect
Added by Mnh Thien Nhan almost 7 years ago.
Updated over 2 years ago.
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.
Files
- TYPO3 Version changed from 7 to 9
- PHP Version changed from 5.5 to 7.0
- Related to Bug #77375: MM references are not transformed to versioned entities added
- Status changed from New to Under Review
It might be, that this is rather a view issue than some persistence issue. Did you check that in FormEngine already?
I have checked that in FormEngine and it has the same result. (see screenshots below)
- Status changed from Under Review to New
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.
- Target version changed from next-patchlevel to Candidate for patchlevel
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF