- πΊπΈUnited States EthanT Sarasota, Florida
Hey @huzooka. What about using the uuid instead of the nid for mapping? Chances of a collision would be far less likely.
Currently when importing nodes (and all other content) it will get the id as specified in the json. It would be better if the imported nodes/paragraphs/files/... will have a new id based on the auto increment. It will prevent nodes from being overwritten by the import or errors raised by the import.
Do not 'migrate' the nid from nodes, fid from files etc. but let Drupal give them a new id.
Fields that are referencing other entities (like paragraph or media fields) should do a lookup of the id in the migration mapping tables to find the destination id based on the source id from the json. Something like;
field_paragraphs:
plugin: sub_process
source: paragraphs
process:
target_id:
plugin: migration_lookup
migration:
- paragraph_image
- paragraph_text
source: id
target_revision_id: '@target_id'
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Hey @huzooka. What about using the uuid instead of the nid for mapping? Chances of a collision would be far less likely.