Menu support

Woah, extremely useful.

If I understand it correctly, you deduce the menu from $node->path. This means the user needs to assign a column from the CSV file to path (see supported/path.inc). I think it is better to make a seperate field for it:

/**
 * Implementation of hook_node_import_fields().
 */
function menu_node_import_fields() {
  return array(
    'node_import_menu' => t('Menu: menu path'),
  );
}

Then in menu_node_import_postprocess() use $node->node_import_menu instead of $node->path. This way one can disable the feature (by not mapping the "Menu: menu path" field to any column) and it becomes possible to have a different menu path and normal path.

Your other problem is how to specify the menu the stuff is built under. You would need to implement some menu_node_import_global() for that which returns a form. If you need some help with that, tell me.

The code itself looks good, except for the messages. Eg:

      drupal_set_message("No parent menu '$parent_system_path' - '$parent_path' - cannot make a menu entry for the page $node->path");

should be:

      drupal_set_message(t('No parent menu %parent_system_path - %parent_path - cannot make a menu entry for the page %node_path', array('%parent_system_path' => $parent_system_path, '%parent_path' => $parent_path, '%node_path' => $node->path)));

this way strings can be translated AND you avoid injecting stuff into the messages.

Also:

  $node->menu = array(
    'path' => 'node/' . $node->nid,
    'title' => $node->title,
    'pid' => $pid,
    'weight' => $menu_weight,
    'type' => 118,
  );

This 118 should be some combination of constants instead of a number.

I did not test it fully, but if you can work on it a bit more, it's likely to get included.

If you can't work on it anymore, please tell me.

Understood. I'll look into it later myself. Menu == path makes sense.

5.x-1.x is no longer supported. Menu support has been added to 6.x-1.x.