How do I import terms into CCK Taxonomy or Content Taxonomy
Vic96 - July 7, 2008 - 08:13
| Project: | Node import |
| Version: | 5.x-1.6 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
I'm using Node Import to import csv content. I'm able to import taxonomy terms into the core taxonomy module of drupal. However when I try to import taxonomy terms into CCK Taxonomy fields or Content Taxonomy fields, the terms don't get imported. They have a drop down option and Node Import doesn't import terms in them. I'd appreciate any help from the experts here. Thank you.
#1
same problem here, interested in a fix
#2
Same problem, subscribing...
#3
Also a big problem for me, but only when using the hierarchical select widget. And for some reason my vocabularies weren't saving my setting for "multiple select" through the UI so I had to set it directly in the database. Now those vocabs accept multiple terms from node import, but again no luck with the HS widget vocab.
#4
Did anyone get this to work?
#5
subscribing.
#6
subscribe
#7
Subscribing...
#8
@matthew_ellis24
Mind qualifying that statement? Do you mean that you got it importing when you turned it off for that field, or when you uninstalled HS, or what?
For me, I was using Hierarchical Select (HS) for a content taxonomy field, but then got stuck at step 4 in the node import process (Map file columns) when the content taxonomy field wasn't recognized for me to import into (see attached). I've since disabled HS for that field, and even deactivated the "Hierarchical Select Content Taxonomy" sub-module (haven't uninstalled), but I still don't see the option to import anything to that content taxonomy field.
I've tried playing around with the HS setting for saving to the node_term table, but both ways failed to allow me to import.
I guess I'm just unclear on whether you succeeded in importing to a CCK or content taxonomy field at all. Any chance you'd elaborate on your small success? :)
#9
Found solution: #434572-11: Add support for content_taxonomy