Task #45151
closed
Epic #55070: Workpackages
Epic #54851: WP: Workspaces IRRE & MM bugfixes
Story #54853: As a user I want to correctly create, modify, preview and publish IRRE & MM related workspace changes
Task #56376: Invalid relations of IRRE records in workspaces
IRRE 1n:csv parent records point to workspace placeholder
Added by Oliver Hader about 11 years ago.
Updated almost 10 years ago.
Category:
FormEngine aka TCEforms
Description
IRRE 1n:csv parent records point to workspace placeholder instead of using the specific versioned record on copying.
If records are copied or newly created on a workspace, a version placeholder is created and overlayed by the specific version of the record.
The fix is to resolve the specific version uid of the record.
- Status changed from New to Under Review
- Parent task set to #54853
- Is Regression set to No
- Assignee deleted (
Oliver Hader)
- Status changed from Under Review to Needs Feedback
- Status changed from Needs Feedback to On Hold
- Parent task changed from #54853 to #56376
- Status changed from On Hold to Rejected
- Assignee set to Oliver Hader
- % Done changed from 0 to 100
Not required anymore since record shall point to default-live record.
Hi Oliver,
it seems to me that the problem still exists in TYPO3 6.2.4.
I have some sort of tt_content (custom CTYPE) with IRRE 1n:csv relations. On changing/adding an new inline child in a workspace and publishing the changes, the parent (tt_content) element has wrong uids connected. The updated tt_content element has the child uids from the workspace version.
It gets even worse: child records created in the workspace are copied into the "INITIAL PLACEHOLDER" record and than deleted. So after publishing I have an tt_content record with not only wrong uids, but also uids that doesn't even exist anymore.
Can you provide me with some information on this issue?
Thanks,
diego
Hi Oliver,
it's me again. I found out, that for me your reason "Not required anymore since record shall point to default-live record." does not apply. After saving the parent within the workspace, the parent record gets updated through the DataHandler and puts the uids of the newly created Workspace-child-records into the relation field. So at this moment I have an parent Live-parent-record that has different uids in the relation field to the workspace-parent-record. On publishing these changes, the wrong uids get copied over to the Live-parent-record.
It would be nice to get some help on this issue, maybe someone has experienced something similar?
Thanks,
diego
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by