Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I've got a custom entity (with revisions). Entity API generates a key schema for the migration that includes the revision id. This works until I migrate content in a key map, as the entity reference destination handler is passed both the id and the revision id and tries to reference both as target_id.
I created this patch to fix it, but it feels like a hack, and I've not been able to track down exactly what is going on.
Comment | File | Size | Author |
---|---|---|---|
#2 | entityreference_migrate_fix_multi_key-1904612-2.patch | 1000 bytes | darrenmothersele |
#1 | entityreference_migrate_fix_multi_key-1904612-1.patch | 959 bytes | darrenmothersele |
entityreference_migrate_fix_multi_key.patch | 990 bytes | darrenmothersele | |
Comments
Comment #1
darrenmothersele CreditAttribution: darrenmothersele commentedthat didn't always work. this does, but still not tracked down how best to solve this.
Comment #2
darrenmothersele CreditAttribution: darrenmothersele commentedupdated patch
Comment #3
yannickooThank you so so much! This patch saved my day, I can still apply the patch even if it's 2 years old :)
I spent hours and it was hard to understand but now the migrations can run successfully again, thank you!
Comment #4
ultrabob CreditAttribution: ultrabob commentedThis has worked great for me too, what is the next step to move it forward to actually being committed?