Once the parent issue is in and we want field handling, we can replace entity.php with this to add field handling. Rolling a patch was too complicated.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | migrate_entity-3.patch | 1.88 KB | andypost |
| entity.php_.txt | 4.23 KB | chx |
Once the parent issue is in and we want field handling, we can replace entity.php with this to add field handling. Rolling a patch was too complicated.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | migrate_entity-3.patch | 1.88 KB | andypost |
| entity.php_.txt | 4.23 KB | chx |
Comments
Comment #1
chx commentedComment #2
andypostIs there a way to determine the need to create or update entity?
Comment #3
andypostInitial working code, taxonomy terms are imported fine
Comment #4
chx commentedComment #5
chx commentedThis patch is off topic for this issue. There is #2169999: Allow for entity updates during migrations and it begins to explore a real lot of difficulties.
Comment #6
benjy commentedI believe this has been added and most of the code found its way into EntityContentBase.