I'm importing nodes with feeds, manipulating the xml-file with rules, all a bit complicated, but working.
There is a little issue with a hierarchical taxonomy term (category). After the import process the category (child term) is rendered, I can see it with devel (Load and Render). But on the edit-form it is missing, the taxonomy reference field is empty. And after saving it, the imported term is gone. The hierarchical select module works great for flat taxonomy lists, but not on the hierarchical one.
This is my configuration for that vocabulary:

$config = array(
  'config_id'       => 'taxonomy-3',
  'save_lineage'    => 1,
  'enforce_deepest' => 1,
  'entity_count'    => 0,
  'require_entity'  => 0,
  'resizable'       => 1,
  'level_labels' => array(
    'status' => 0,
    'labels' => array(
      0 => '',
      1 => '',
      2 => '',
    ),
  ),
  'dropbox' => array(
    'status'    => 1,
    'title'     => 'Ausgewählte Kategorien',
    'limit'     => 0,
    'reset_hs'  => 1,
  ),
  'editability' => array(
    'status' => 1,
    'item_types' => array(
      0 => 'Kategorie',
      1 => '',
      2 => '',
    ),
    'allowed_levels' => array(
      0 => 1,
      1 => 1,
      2 => 1,
    ),
    'allow_new_levels' => 1,
    'max_levels'       => 3,
  ),
);

I really like the module and hope someone can help me to solve this issue.

Comments

Summit’s picture

Hi,
Could it be a language problem with importing them as "UND", but having a language in your website. Or the other way around?
Just trying to help..
greetings, Martijn

mErilainen’s picture

I have the same problem, not sure if it's about the language. Because I have und also after importing and after saving the terms with the HS widget.

There are other possible configuration related issues, like should I have the save only the deepest term or the whole lineage. I'm trying to save the lineage from the imported XML files, but it seems to only save the deepest term at the moment. I will investigate further and try to import without the HS widget on, and also with the deepest term selection.

d.chatry’s picture

Hi, I'm having the same issue and I think it has to do with the "Save lineage" configuration, you can try and disable it (if you don't need it) and you'll see it works.
It's weird the module can't find its way back to the parent(s) term(s) when given the deepest term, with the "Save lineage" option on.

EDIT : I managed to find a workaround thanks to this comment on a related issue, just install the module, enable it for your taxonomy and try re-importing your content. It worked for me :)