CCK field mappings for custom content-types missing
garrettc - April 27, 2007 - 14:39
| Project: | Import / Export API |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I have a custom CCK type called 'supplier' consisting of the standard title and body fields, plus 7 extra fields (five text entry, one email and one URL) that I'm trying to import some CSV data into.
After selecting this content type and file format (CSV) at /admin/build/import I go to the field mapping screen, but I don't see any of my custom fields to map the CSV data onto, just the standard itmes like 'Node ID', 'Revision ID', 'Title', 'Body', 'Teaser', 'Created' etc.
I was under the impression that it would automatically pick up any custom fields in the content type, am I wrong?
If so, does that mean I need to create a 'importexportapi_supplier.inc' in contributions and explicitly tell importexportapi the fields that it contains?
#1
I have the same issue on the Export side... documentation is so sparse that I cannot figure out what *should* work and what *does* work.
I am not getting ANY CCK fields in ANY export for the "Import Export UI". I was hoping to use the the export format as an indication of how data must be structured for an import.
A little help would be very much appreciated.
#2
I can confirm that this is a problem. I believe that we need additional include files for every CCK content type (email, date, link, etc). We only have ones for nodereference and userreference. These go in the definitions/contrib/cck directory. If you create one that works, please attach it here and I'll test it and add it to the CVS repository. Thanks!
#3
After some digging I'm not sure that it is just a matter of needing extra include files. I have a different content type that makes use of nodereference, but if I select that content type for the import, no mapping for the nodereference field appears.
In any case, I would be happy to help build some include files for the other content types but the developer documentation for this is way over my head, it's like trying to read the FAPI specs. If there is a step by step guide somewhere to me to get over the initial learning hump that would be a great help.
#4