Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When a term is imported to a hierarchical taxonomy term, the lineage is not stored.
Comments
Comment #1
relaxnow CreditAttribution: relaxnow commentedAttached is a patch that implements this.
Comment #2
relaxnow CreditAttribution: relaxnow commentedFixed ordering of terms, parents should be stored first so autopath can generate a proper URL.
Comment #3
relaxnow CreditAttribution: relaxnow commentedNow a patch that actually applies...
Comment #4
webjazznl CreditAttribution: webjazznl commentedThis patch is nice but the code will fail if you have hierarchic vocabulary like this one
that lists Motor Bike,Model and Manufacturing. Year
Honda,
750 Deluxe,
2004
2005
Yamaha,
1000 Low Rider,
2004
When feeds is offered a Yamaha 1000 Low Rider built in 2004, your code will find this term path: Honda, 750 Deluxe, 2004 because it looks from the child up and finds the 2004 term under Honda first. (I have some data that proves the failure). However you should look from the parent down.
Would you be able to write a patch that does this? I am more of a site builder than a developer.
The code would need a comma delimited string as input to do its magic such as: "Yamaha,1000 Low Rider,2004".
Taxonomy already has a function for it, which is explained here
http://drupalcontrib.org/api/drupal/drupal!modules!taxonomy!taxonomy.mod...
However I lack the experience to pull this off in Drupal. I would really appreciate your help!
Thanks for your time,
Henk
Comment #5
webjazznl CreditAttribution: webjazznl commentedOh, the indentation was stripped from my previous post (#4). So Make is on the 1st level, Model is on the 2nd level and, Year is on the 3rd. You 'll get it...
Comment #6
Summit CreditAttribution: Summit commentedHi setting back to needs work based on #4. Greetings, Martijn