Timeline for Bidirectional entity relationships?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16, 2020 at 7:10 | comment | added | milkovsky | There are answers, that suggest to use 2 entity reference fields and sync them. But I do not find this solution robust. In my case I have 13 content types, that can be related to each other. I think a better solution would be to develop a new field type. There is Drupal 7 project Relation for this issue, but no Drupal 8 solution yet. | |
| Mar 25, 2019 at 9:00 | history | tweeted | twitter.com/StackDrupal/status/1110104178398031873 | ||
| Mar 25, 2019 at 1:46 | answer | added | No Sssweat | timeline score: 0 | |
| Mar 21, 2019 at 19:53 | history | edited | avpaderno♦ | CC BY-SA 4.0 |
edited tags
|
| Mar 21, 2019 at 18:21 | answer | added | Mike | timeline score: 2 | |
| Mar 21, 2019 at 17:44 | comment | added | seroton | Sounds like a thing the cer module could do but as you said it's not working.. If you don't mind a custom solution, some code to update the referenced node when the other was updated/created/deleted should do it. So after you migrate, a custom submit handler on the linked content types to manage creations/updates and then on hook_entity_delete to handle deletion of the referenced content relation. | |
| Mar 21, 2019 at 16:07 | history | asked | Kevin | CC BY-SA 4.0 |