Bug #81718
closed
Workspace - TYPO3 MM relations are defect
100%
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
Updated by Mnh Thien Nhan over 7 years ago
- TYPO3 Version changed from 7 to 9
- PHP Version changed from 5.5 to 7.0
Updated by Mnh Thien Nhan over 7 years ago
- Related to Bug #77375: MM references are not transformed to versioned entities added
Updated by Gerrit Code Review over 7 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
Updated by Oliver Hader over 7 years ago
It might be, that this is rather a view issue than some persistence issue. Did you check that in FormEngine already?
Updated by Mnh Thien Nhan over 7 years ago
- File formCategoriesSelected.png formCategoriesSelected.png added
- File newCategoriesInWS.png newCategoriesInWS.png added
I have checked that in FormEngine and it has the same result. (see screenshots below)
Updated by Anja Leichsenring over 6 years ago
- Status changed from Under Review to New
Updated by Franz Koch over 6 years 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.
Updated by Benni Mack over 5 years ago
- Target version changed from next-patchlevel to Candidate for patchlevel
Updated by Gerrit Code Review about 3 years ago
- Status changed from New to Under Review
Patch set 11 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/+/71097
Updated by Gerrit Code Review about 3 years ago
Patch set 12 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/+/71097
Updated by Gerrit Code Review about 3 years ago
Patch set 13 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/+/71097
Updated by Gerrit Code Review about 3 years ago
Patch set 14 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/+/71097
Updated by Gerrit Code Review about 3 years ago
Patch set 15 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/+/71097
Updated by Christian Kuhn about 3 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset e90691287ea887beba4514fad46f637270fe77c8.