Hi. First off, thanks for this module...I use it extensively.

I'm using the Drupal migrate module to migrate data from a non-Drupal dB to a Drupal one and I've set up a content type person with child of person role in Drupal. The parent people will be migrated in first, then the children.

The migrate module provides functions that allow manipulation of data right before it's saved as a node or the $node object right after it's saved.

I have the parent/child nid/$node object available for either of those functions.

My question: what API calls from nodehierarchy.module can I use to update the child with the hierarchy info? Also, do I need to re-save the parent after the child is updated?

Thanks in advanced!

Dan

Comments

jbylsma’s picture

jbylsma commented

You should be able to use nodeapi implementations, which will eventually lead you to the private function _nodehierarchy_save_node(). All that stuff is contained with nodehierarchy.module and is pretty well commented, so it would probably be beneficial to take a look there before pulling any triggers.

#621662-13: Programmically assign parent when creating a node from script and previous comments have some information about programmatically adding nodes. That might help you out.

Please report back your findings! I'm unfamiliar with Migrate, so I'm not sure whether supporting it natively Node Hierarchy is warranted or even feasible. I'd be curious to hear about your experience.

webdrips’s picture

webdrips commented

Hi Jonny.

Thank you so much for point me in the right direction! I'm happy to report it is working with a few slight modifications from the above link.

Typically Migrate module support for other modules has been handled either natively if it's a popular enough request (e.g. date) or somebody adds it to the Migrate Extras module typically as a field handler method that extends MigrateFieldHandler.

I'm guessing this would not a trivial task, but if an argument was coded to handle the parent nid, seems as if the rest could be handled via similar code. This is actually considered the more correct way to do it than what I did below.

First, we need to add the desired field to the $query object (migration coders will recognize this part):

$query->leftJoin('people', 'p', 'p.id = pr.people_id');
$query->addField('p', 'full_name'); // full_name is now available in the $source_row below

Next we add the complete() function outside the constructor, which is the last function called for a given row being migrated (and thankfully where the $node object has already been saved to the dB).

  public function complete($node, stdClass $source_row) {
    // Load the full child node object
    $cid = $node->nid;
    $child = node_load($cid);
    
    // Grab the name of the parent to be used in our query below.
    $full_name = $source_row->full_name;
        
    // Now find the parent in the dB
    $result = db_select('node', 'n')
              ->fields('n', array('title', 'nid'))
              ->condition('n.title', $full_name, '=')
              ->execute();
            
    foreach ($result as $row) {
      $parent_person_nid = $row->nid;
    }
    
    // Get the menu link id of the parent
    $plid = _nodehierarchy_get_node_mlid($parent_person_nid, TRUE);

    $nodehierarchy_menu_links = _nodehierarchy_default_menu_link($parent_person_nid, $plid);
    $nodehierarchy_menu_links['pnid']= $parent_person_nid;
    $nodehierarchy_menu_links['hidden'] = FALSE;
    $nodehierarchy_menu_links['enabled'] = TRUE;
    $nodehierarchy_old_menu_links = $nodehierarchy_menu_links;
    $nodehierarchy_old_menu_links['enabled'] = TRUE;
    unset($nodehierarchy_old_menu_links['hidden']);
    unset($nodehierarchy_old_menu_links['link_path']);
    $nodehierarchy_old_menu_links['link_title'] = '';
    $nodehierarchy_old_menu_links['expanded'] = '';
    $nodehierarchy_old_menu_links['description'] = '';
    $nodehierarchy_old_menu_links['customized'] = '';
    $child->nodehierarchy_menu_links[] = $nodehierarchy_menu_links;
    $child->nodehierarchy_old_menu_links[] = $nodehierarchy_old_menu_links;
    _nodehierarchy_save_node($child);	
  }

That's it...be sure the import specifies the parents are required to import first and it works.

Thanks again...this saved me a lot of time!

Dan