Import using node_import fails to populate all but first Address field.
RAMilewski - April 18, 2008 - 20:46
| Project: | Address field for CCK |
| Version: | 5.x-2.1 |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
I'm a total newcomer to Drupal and CCK, so I'm probably missing something obvious, but....
I'm trying to load about 1000 address records into a CCK Address field set using the node_import (5.x-1.5) module.
There are four fields mapped to the CCK Address subfields. (screenshot of import spec attached).
The first field (Address street1) is populated but other 3 fields are always blank.
I've also attached a screenshot of the CCK address settings.
| Attachment | Size |
|---|---|
| Picture 2.png | 20.65 KB |
| Picture 3.png | 43.68 KB |

#1
I'm not sure what the import thingy tries to do, but the cck_address module doesn't support the 'multiple' checkbox that other cck modules does - that's a complex situation and a pain to code; and I haven't needed it, and nobody has patched it. So, the current way to have multiple addresses on a single content type is to add the field multiple time. I don't know if that's what the import will work with or if I totally am in the dark about what you are trying to do.
If I were you, I'd look at your database tables on both ends of the import and then check the import code to see if it is addressing both ends correctly. Perhaps post your DB info over at the import issue queue as those folks will know whether their code can work in that situation or not.
#2
Had the same problem. Did some digging and stumbled across this patch to node_import. It worked for me.
See comment #15 at http://drupal.org/node/105982
Here's a couple of links on how to install patches -something I had to track down.
http://drupal.org/node/32875
And here
http://drupal.org/node/60108
#3
If you having problems importing address_cck content with node_import, please see patch #15 (http://drupal.org/node/105982) and read this comment (http://drupal.org/node/105982#comment-1014619).