Reworked to support multiple hierarchy imports, work with Feeds 7.x-2.0-alpha8

@manarth: Thanks for a great module! I was working on a fork of a Feeds Tamper plugin with similar functionality (#1319278: Support automatic importing of the term hierarchy for nested taxonomy terms), but using your custom mapping is the way to go!

@anschultz: Great fork, but it seems you removed functionality to automatically create new terms, is this on purpose hadn't read the README file! Also I think it might be wise to not replicate Feeds Tamper's functionality to separate multiple field values from each other.

Before I saw anschultz's module I also forked Feeds hierarchical taxonomy and combined it with original mapping from feeds/mappers/taxonomy.inc, see attached. My fork:

1. Also works with the latest Feeds and Feeds Tamper;
2. Also allows the admin to set the hierarchical separator;
3. Uses caching methods from the original Feeds taxonomy mapping (could be improved by storing query results in a static array);
4. Works with term names only and not with term id's. The original module interprets numerical term names as term id's and thus does not allow numerical term names. I removed this functionality since for hierarchical term id's (ie. "123>>456") one can use Feeds Tamper to remove all parent term id's.

With help of Feeds Tamper's explode plugin to separate multiple field values, I successfully tested attached fork on an import file similar to:

id;tags;title
"ABC001","Product 1","Category 1>>Sub-category 1|Category 3>>Sub-category 1"
"ABC002","Product 2","Category 1>>Sub-category 2"

I altered our module to:

1. Clean things up;
2. Add better caching: all queries for terms are temporarily being stored in a static object;
3. Add optional linear support: in case of "Colors>>Red" the admin can choose to only save the deepest term "Red" or both "Colors" and "Red" terms;
4. Add better cardinality support: if a field is only allowed to have 2 values, only 2 terms are being created and added as field values. Also if a node is being updated by Feeds (opposed to being replaced), the module respects earlier added terms.

Attached newer version with cleaner code and made automatic term creation optional.

Hi, I've installed the #3 version, but I can't find the module's configuration form and I don't understand how to make this module work... I imported an XML file using XPath XML parser, using feeds tamper I obtained a string like "Category>>Subcategory" and now I'm trying to add these terms to my vocabulary but all I get is a single term which contains a string like "Category>>Subcategory".
Could someone explain me how can I make this module work? Thank you!

@Andrea Gobetti: I have not used XML imports through Feeds yet, so do not know whether it works for non CSV imports.

The module does not have a settings page. At the mapping settings of your feed you should select the target field with a suffix like "Hierarchical", after that you can alter some settings at field level.

Thank you lmeurs, all I can see in the mapping settings on my field is a select box called "Search taxonomy terms by" and a checkbox called "Auto create", I don't think this module works also for XPath XML parser, for now.

Hi~ I installed feeds_taxonomy_hierarchy_3.zip. But when I try to start importing, It shown error in the report page:

Recoverable fatal error：Argument 4 passed to feeds_taxonomy_hierarchy_feeds_set_target() must be an array, string given, called in /www/sites/all/modules/feeds/plugins/FeedsProcessor.inc on line 509 and defined at feeds_taxonomy_hierarchy_feeds_set_target() (/www/sites/all/modules/feeds_taxonomy_hierarchy/feeds_taxonomy_hierarchy.module line 104 )。

please help~

Thank you.

@ethanLee: Did you use the Feeds Tamper module to explode the bare string value first? Your feed probably provides a string value like Parent term|Child term, but this string value needs to be turned into an array value like array('Parent term', 'Child term') before it can be mapped correctly.

Dear Imeurs,
Thank you for your answer. But I still don't know how to set the feeds tamper and feeds_taxonomy_hierarchy module. Could you give me an example?
Thank you again.

My csv file :
id,title,brand
12,product1,brand>brandA>brand123
13,product2,brand>brandB>brand123

@ethanLee: You already mapped the fields for your node processor and have the Feeds Tamper module enabled, right? Go to admin/structure/feeds, look up your feed and click it's Tamper link. Search for the Brand field and click Add plugin. Now under The plugin to add select List > Explode and set the String separator in your case to >.

Also see the Feeds Tamper documentation, it's a great versatile module!

Thank you lmeurs~It works well~

Hi Imeurs, i have mapped several xpath expression to my fields. I have created one field (Location: hierarchical by term name -Hierarchy separator: >>) where with the tamper pluggin i make a rewrite to get a hierarchy path stiched together by other field values ([xpathparser:11]>>[xpathparser:7]>>[xpathparser:8]>>[xpathparser:9]) . Then I added another plugin to explode the stiched string with ">>" as separator.
When i do the feed import only the first expath expression is created in my taxonomy vocabulary ([xpathparser:11]). The rest is simply ignored.
Can you image why this is so? Thanks in advance.

@sampaka: I am not familiar with the Feeds XPath Parser module, but since at least 1 term reference is created, something is working well.

Do you happen to use "Save term lineage"? If so, make sure the node's field that is referencing to this taxonomy vocabulary allows more than 1 value.

@Inmeurs - thanks a lot for your answer. Indeed the taxonomy vocabulary was limited to 1 value, so I changed it! Now every term is imported but without any hierarchy. Could this be a problem of my term reference field as it is set to Autocomplete term widget (tagging). Update: changing to a select list unfortunately did not change anything

@sampaka: Your question puzzled me for a while, but I might have a solution. At #12 you say:

Then I added another plugin to explode the stitched string with ">>" as separator.

This causes Feeds tamper to flatten your hierarchy, while handling hierarchies is supposed to be done by Feeds hierarchical taxonomy.

Feeds tamper is only needed here to optionally explode multiple hierarchical terms that remain in a single value. Say your CSV looks like:

Title,Categories
"My article","Parent term A >> Child term A|Parent term B >> Child term B"

In this case a Feeds tamper plugin can be used to explode the hierarchies from each other using "|" as separator, Feeds hierarchical taxonomy is used to handle single hierarchies using ">>" as hierarchy separator.

@Imeurs - its working! so great - you made my day! You were absolutely right that feeds tamper with ">>" as separator flattened my hierarchy. But when I removed it i got the error: "An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. ResponseText: Recoverable fatal error: Argument 4 passed to feeds_taxonomy_hierarchy_feeds_set_target() must be an array, string given, called in ".

So I simply added the Feed temper plugin to explode but instead of ">>" i established "|" as separator. Now the array gets created and I can pass the stitched xpath expression results into the taxonomy term with the corresponding hierarchies.

Thanks you so much for pointing out the things you noted that were wrong with my approach. I hope this can help people who try to map xpath expressions to taxonomy!

@sampaka: I am happy to hear it's working for you! I understand where the confusion came from. Though the original module expects an array (as stated at the project page), it makes more sense to accept strings as well. I changed this in the forked module and attached it to this issue.

Best of luck!

I just want to say thanks! This module - especially with the last change - is just what I needed to create a lot of nodes with reams of hierarchical taxonomic terms from csv files. I'm not yet up to the level where I can contribute much back in the way of code, and offering to bake cookies doesn't seem appropriate, but you've saved me hours and days of head-banging.

Hello Imeurs, thank you very much for writing this module, Fixed my life. I could use your module to import 5000 products and their views on a new Drupal system and worked perfectly. thank you very much.

I added this line after line:202 to remove empty values
$hierarchical_term_names = array_filter($hierarchical_term_names);

@Inmeurs Thanks for the module. It works perfectly.
Since I had not paid heed to your statement "Feeds tamper is only needed here to optionally explode multiple hierarchical terms that remain in a single value." and lost some hours, I am recording the steps required to import data like
Media>Graphics>Banner & Sign.

In Feeds setup for the field "Category: hierarchical by term name" it should be like
Hierarchy separator: >
Automatically create terms: No
Save term lineage: Yes

No other setup is required in Feeds Tamper for this field.

@Inmeurs First of all, thanks for the module!
I can't seem to get it to work the way I need it to, though.
My CSV file contains a taxonomy field named 'list', which has its values exported in the format "Parent Term>>Child Term".
This taxonomy has only 2 levels (if that makes any difference).
I installed the latest version of the module (4), and mapped the 'list' field from the CSV file to the 'field_category' taxonomy field I have in my data type. I've used '>>' as separator, checked the option to add new terms, and tried with and without term lineage.
Both options yielded the same result - only parent terms have been imported and set.
What I want to achieve is to have the taxonomy filled with parent and children terms, and the node field value to be set to the child term.
What am I doing wrong?

Thanks again,
Nir

@nir.arazi: I have not worked with the module for a while now, but from the top of my head: do you happen to use Save term lineage and does the node's field allow just 1 value? If this is the case, the module iterates through all taxonomy terms, tries to create terms and stores term ID's as field values, but since only 1 field value is allowed the module stops after the first term (the parent). By turning off Save term lineage all terms are being created, but only the ID of the deepest term (child term) is being stored as the field's value.

Does this make any sense?

@casper83: Thank you for your input, I added support for empty terms as in "Term A >> Term B >> >> ": The last terms have no name and will be ignored.

Hi,

Just wanted to say thank you so much for this patch, it worked perfectly for me and is essential for my current project which involves importing hundreds of terms that are listed in a hierachy and which are used to organise sections of the website and populate navigational menus.

Many Thanks
Richard

I had a similar situation as @tadesign and agree 100%!

My CSV hierarchy looked like this:
Parent > Child > Grandchild

So being able to easily specify in the settings that my delimiter had a space on either side was a big help. After some careful setup, it worked flawlessly on the first try! Great job @lmeurs!

For me right now it is working for Commerce product but not for Product Displays.

@vivdrupal: a Commerce product display is a node, so it should work. Did it suddenly stop working (maybe after you updated to Drupal 7.33 like you said before you edited your comment) or is this a new install you're talking about?

Today I successfully implemented a feed for product displays using this module, so could you tell me about your setup and settings?

Hello,

Thank you for the module.

I used the version in #24, I am able to explode the terms with feed tamper, but the relationship between parent and child is not set.
Did I miss something? any ideas?

@JadH: At the field mapping page, did you select "VOCABULARY_NAME: hierarchical by term name"?

If so, can you determine the following settings for this field:

• Hierarchy separator
• Automatically create terms
• Save term lineage

What are the values of these settings and can you provide one line from your CSV file?

NB: You should only use Feeds Tamper for this field if a node can contain multiple hierarchies, see comment #15 for more info.

@lmeurs it is working now, I was not using the field with "hierarchical by term name"
great module, thank you.

Having issues with Drupal v. 7.34. Worked fine on 7.32. We are uploading a csv file to a node using feeds v. 7.x-2.0-alpha8. Now it only imports the parent term with v. #24. The other one does not import any terms.

Figured out the issue. We had changed the input widget to simple hierarchy select on the content type. Once we changed it back to the regular hierarchy select, the import feeds worked.

I attached a new version of the module which fixes a bug that on entity update prevented possible existing values from being overwritten, instead new values were being appended.

Take for example updating an entity with a taxonomy term reference field with a cardinality of 1: only one value is allowed, the old value would not be overwritten and a new value could not be added, so nothing seemed to have happened after the update had finished.

Would this module also work for entity reference to taxonomy ? instead of basic taxonomy term reference?

Right now it does not, but it might after a few small modifications.

The implementation of the hook_feeds_processor_targets_alter() hook only adds a custom Feeds target for fields of type taxonomy_term_reference, of course another field type could be easily added.

Also, on import the module sets the entity's field value as an array with associative subarrays with solely term ID's, I do not know if this structure applies to entity reference fields as well. Example:

$entity->{$field_name}[LANGUAGE_NONE] = array(
  array('tid' => 123),
  array('tid' => 456),
  array('tid' => 789),
);

https://www.drupal.org/project/entityreference_feeds
This module does feeds entity import
I m looking to merge your hierarchical solution with there entity solution.

In feeds_taxonomy_hierarchy_feeds_processor_targets_alter the folowing is needed to let it show up

    ## kept seperate to allow for different callbacks validations and so on
    if ($field_info['type'] == 'entityreference') {
      $targets[$name . '_hierarchical'] = array(
        'name' => t('@name: hierarchical by term name(Entity_reference)', array('@name' => check_plain($instance['label']))),
        'callback' => 'feeds_taxonomy_hierarchy_feeds_set_target',
        'description' => t('The @label field of the entity.', array('@label' => $instance['label'])),
        'form_callback' => 'feeds_taxonomy_hierarchy_form_callback',
        'validate_callback' => 'feeds_taxonomy_hierarchy_validate_callback',
        'summary_callback' => 'feeds_taxonomy_hierarchy_summary_callback',
      );
    }

I think i get close with the other code but
$shared->cache->{$field_name}->vocabulary_ids[0];
apears to never be filled in and gives Null so look up also gives nothing.

For lookup i also tried in
feeds_taxonomy_hierarchy_get_term_id

    // Build and execute query to find term
    $query = new EntityFieldQuery;
    $result = $query
      ->entityCondition('entity_type', 'taxonomy_term')
      ->propertyCondition('vid', $vocabulary_id)
      //->condition('parent', $parent_id)
      ->propertyCondition('name', $term_name)
      ->propertyOrderBy('weight')
      ->execute();

     $result_tid = array_shift($result['taxonomy_term'])->tid;

just to keep you posted

i created a sepperate issue for the entity reference support
https://www.drupal.org/node/2484727#comment-9899953

It appears to be working for our use case

Great, will try to take a look at your adaptions soon!

I just have tried #33 and I was unable to make it work. It only saves the parent term and the child under that parent term is being ignored.

I've added Vocabulary name: hierarchical by term name (field_name_hierarchical) and set the settings below:

Hierarchy separator: |
Automatically create terms: Yes
Save term lineage: Yes

Here's my CSV's structure:

title,code,category
title 1,123,parent
title 2,345,parent|child1
title 3,678,parent|child1|child2

I've also added a tamper plugin, which is [Explode] and used vertical bar in string operator.

I noticed that only parent term is being created.

Is there something wrong with my setup? Please advice.

@madelyncruz: Does the node's taxonomy reference field allow multiple values?

@madelyncruz: BTW, you should only use Tamper Explode if the column contains multiple hierarchies as in:

title 2,345,parent >> child1|parent >> child2

(I prefer to use "|" to separate muliple values from each other and ">>" as a hierarchy separator)

@lmeurs No. I've set it to 1. Is it needed to be unlimited?

@madelyncruz: Well, since you selected Save term lineage you want to save multiple terms, so the fields cardinality needs to be at least 2.

@lmeurs OK. I did not know that. Thank you for telling me that :)

@lmeurs Got it! I've set the values to unlimited and it's working OK now, but why it creates 2 separate terms

eg.
Term 1: best sellers
Term 2: best sellers > aus

What I only need is the Term 2 and I don't want a redundant terms.

Thank you so much for your quick response.

If you provide Parent > Child > Child's child, all terms will be created, hence the name Feeds Taxonomy Hierarchy. If you only want the top level term, the easiest way is to only provide that term as in Child's child, but that can be done with Feeds out of the box.

If you do not have control over the input feed, you might want to look for a Feeds Tamper way to explode your values and only pass the top level value to Feeds. But I do not know how to... Or you can alter the module to only process this top level value.

Turn:

$hierarchical_term_names = array_filter(preg_split('#\s*' . $preg_hierarchy_separator . '\s*#', trim($term_name));

into something like:

$hierarchical_term_names = array_splice(array_filter(preg_split('#\s*' . $preg_hierarchy_separator . '\s*#', trim($term_name))), -1);

I have not tested it, so at your own risk! :-)

@lmeurs

Thanks for module. I am trying to use it as I am a bit new to drupal finding it hard to use .
Do you have any step by step doc anywhere ?
This module is different from other modules, once I download all I can see is .info and .module only ?

Thanks

Can someone help me with the taxonomy hierarchy set up .
ON website I have category HOME & Garden > Sofas

In the XML the category structure is Root > Category> Sofas.

What setting do i have to change to get this imported.
I tried default setting none of products were uploaded to right category .

Thanks

@aus007: If you have created feeds before, using this module is easy. When mapping a Feeds column to a taxonomy reference field you have to select a hierarchical by term name mapper and A) select whether you want to create new terms or only use existing ones and B) whether you want to save term lineage (also save the term's parents).

I have not tested the module with XML files yet and I am not sure whether it works, also see #4. So far it does work with CSV, if you can switch to CSV, please do so.

@lmeurs
Thanks for your reply.

Ok will try with CSV , got a small question . Inorder for this Module to work correctly, should the hierarchical structure be same in Source and destination.what's the work around if my source CSV has category hierarchy HOME& Garden > LIVINGROOM> Sofas
while destination has just HOME > Sofa .
How to work around with this specially when you dealing with many different suppliers with different hierarchical structure.

Thanks

@aus007: That is beyond the scope of this module. You might want to take a look at Feeds Tamper to alter values before they are processed by any Feeds processor. If you create a custom tamper plugin you could easily define source + destinations pairs (maybe in a separate text file) and map source > destination accordingly.

To be honest, if things get complicated I often use a custom parser outside of Drupal which prepares a CSV file before importing it into Drupal: Feeds requests the CSV over HTTP through the custom PHP parser.

Hi Imeurs,

First off thank you for such a great module. I had it working perfectly until we determined the client couldn't combine all possible Taxonomy terms on one line give Access DB export restrictions based on character counts.

We are creating individual products in Commerce, and using Brand+Model heirarchical taxonomy terms to associate the products with other products. In an effort to reduce the size of the combined taxonomy field in the DB export, I imported the entire Taxonomy tree, and then used the Term ID as part of my import CSV.

Having just read through the comments above I notice that you mention we can't use Term ID's in the import, only actual term names. I'm not sure I understood exactly the reason why, over my head I'm guessing, but is there anyway I can use the taxonomy term ID's in my import?

thanks in advance for your advice/support.

Regards

Thanks for the module!

@droddis: The main goal of this module is to link entities to hierarchical taxonomy terms when processing a feed, this comes with extra features like automatically creating non existing terms and saving term lineage.

In your case you want to link to already existing terms using their ID's, so as long as you do not need to save the term lineage, can't you use Feeds' default taxonomy term importer providing the ID of the highest term?

Module works fine!
Please, contrib!

@Imeurs

I'm not sure that I can't. I just tried creating the import csv using the taxonomy terms. didn't work as of yet but I'll continue to play with it.

Maybe I'm going about it all wrong, I'll take another look at the setup. thanks for your help and suggestions though!

Thanks for that - please contribute.
Working with Feeds version: 7.x-2.0-beta1.

@olomouc: The module can be used with any type of entity which has a taxonomy term reference field, so unfortunately it will not work in your case.

@mristau: You hid the latest version of this module, I think by mistake, so I unhid it.

I have Feeds v.7.x-2.0-beta1
and I want import my csv with hierarchial taxonomy mode.

Industry (root)
-Country (parent1)
--Email (term)

How I can I do?

Thanks

Example:
Industry|Country|Email
Ferrari|Italy|ferra@f.it

but this template import only last term... I want hierarchial term.

Hi @lmeurs - is this module supporting for X-path while importing xml feed? Because for me in xml feed import it's not working.

@pradeepjha: As earlier discussed in this issue I have not tested this module with X-path and other users seem to be unsuccessful at it.

Bump for when using entity reference support
Patch and code here, aplies cleanly to latest version 6
https://www.drupal.org/node/2484727#comment-9900321

Improved version when using entity reference support that also handels the case when a view handler is being used on the field.
Patch and code here, applies cleanly to latest version 6
https://www.drupal.org/node/2484727#comment-11536381

First, thanks for the effort to have such wonderful module.

I'm using the #33 module. My setting are as follow:

using feeds_tamper: explode list - the result looks like "Bedding>mattress"

pre-process replace all the ">" to ";" - the result become "Bedding;mattress"

on the import site, I selected the mapping to Product Categories: hierarchical (field_taxonomy_terms_hierarchical)

Then I start to import, but it gave me so many warning/notice and error which I have simplified such as:

Notice: Trying to get property of non-object in feeds_taxonomy_hierarchy_set_target() (line 86 of /var/www/html/dev/flatastic/sites/all/modules/feeds_taxonomy_hierarchy/feeds_taxonomy_hierarchy.module).
Notice: Undefined property: stdClass::$field_taxonomy_terms in feeds_taxonomy_hierarchy_set_target() (line 119 of /var/www/html/dev/flatastic/sites/all/modules/feeds_taxonomy_hierarchy/feeds_taxonomy_hierarchy.module).
Warning: array_replace(): Argument #1 is not an array in feeds_taxonomy_hierarchy_set_target() (line 119 of /var/www/html/dev/flatastic/sites/all/modules/feeds_taxonomy_hierarchy/feeds_taxonomy_hierarchy.module).

Any thought?

Thanks & best regards,
Max.

@lmeurs

I use this module with a xml file & Feeds Tamper. For me it's ok and the importation seems to work.

This module is very very useful. Do you think create a stable/official version for this module?

Thanks.

P.S. This module seems to work but I get 1 warning after the process of importation :

Warning : Creating default object from empty value dans feeds_taxonomy_hierarchy_set_caches() (line 249 in /srv/data/web/vhosts/mysite.com/htdocs/sites/all/modules/feeds_taxonomy_hierarchy/feeds_taxonomy_hierarchy.module).

I wonder if this would be the right thread to post comment but anyway it is a issue, partly related to the module.

It works fine and thanks very much, for providing it. Anyway I am using i18n and have multilingual - hierarchical, taxonomy. My taxonomy terms have same meaning but translated names, as per a few languages.

When importing hierarchy of terms (or even flat) in English, everything is just fine.

A problem occurs, when importing translated terms on any other language. I couldn't do it so far using Feeds and/or this module. I have tested many taxonomy field types (select, autocomplete, hierarchical). None of them seems to import data from Feeds import, when the latter is in a different from English (default for site btw).

Did someone had a similar issue? Any help or advice would be appreciated.

Hi @lmeurs,

Amazing contribution, thank you!

I just want to report an issue with the current module. It does not seam to like taxonomy terms with a " - "

It seams ok with a letter-letter i.e. "User-Interface" but not "User - Interface"

Is it possible to import multiple values in one taxonomy field using this module?

When I am trying to do it, saving the category lineage, with two separate fields, the import takes the results from the second field.

Should I use one field for import, with a similar structure parent > child, parent > child 2 with FEED Tamper I didn't try this so far.

#33 worked great, however since it needs to be created as a patch, setting to Needs work. Thanks for everyone's work on this!