Needs work
Project:
Relation
Version:
7.x-1.x-dev
Component:
Relation migrate
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Dec 2014 at 12:18 UTC
Updated:
17 Sep 2015 at 12:32 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mikran commentedComment #5
mikran commentedSomething weird is happening, I'm getting different results locally
Comment #6
mikran commentedI figured that out, for some reason testbots use outdated version of Migrate.
Comment #7
mikran commentedAs this is now blocking work on other issues here is a patch that disables relation_migrate tests completely. for now.
Comment #9
mikran commentedComment #10
mikran commentedComment #11
mikran commentedComment #12
osopolarWhat does it need to make relation_migrate compatible with Migrate 7.x-2.8? Where are the incompatibilities? I currently need to add relations (between two nodes and between a field-collection and a node) by a custom migration.
Comment #13
mikran commentedI don't know but let's see how the testbot behaves nowadays...
Comment #14
mikran commentedComment #16
osopolarI used this tutorial to get migration for relation to work. I copied the destination handler (relation_migrate.destination.inc) in a custom module, to don't conflict on relation upgrades and modified it. Basically I removed
'not null' => TRUE,from getKeySchema(), and added following to fields: fields().I added the patch for that, but currently I am to busy to test it. But let's see if it works.
I also added my Migration class (uses Drupal-to-Drupal data migration) to show how I have implemented the handler. In the child classes I only have to refine the the query and in hook_migrate_api() I added the relation like that:
That way different relation migrations could be defined without much coding.
Comment #17
osopolarAdded relation-base.inc.txt, as relation-base.inc was not uploaded in #16.