This module simply gives me an White screen of death during import (/admin/content/node_import), even when simply importing exactly one (!) field and one (!) record. The content type I'm trying to import to is "working" for hundreds of other nodes, but cosnsists of several CCK fields including a CCK "date" field. The error seems to apply only to content types with CCK fields; vanilla content types from Drupal core seem to work better (however, I don't want to import data to those simple content types).
On the "options" page, I'm adding three existing terms from Taxonomy. The node type I'm importing to has some CCK field which are not being used for imports.
No error or warning is given on the "preview" page, but the watchdog log is cluttered with errors like:
include_once(sites/all/modules/date/date/date.inc) [<a href='function.include-once'>function.include-once</a>]: failed to open stream: No such file or directory in /var/www/drupal/sites/all/modules/node_import/supported/cck/content.inc in Zeile 95.
...
include_once() [<a href='function.include'>function.include</a>]: Failed opening 'sites/all/modules/date/date/date.inc' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/fotonexus/sites/all/modules/node_import/supported/cck/content.inc in Zeile 95.
...
Invalid argument supplied for foreach() in /var/www/drupal/sites/all/modules/node_import/node_import.module in Zeile 299.
...
This module is a great idea, and the UI promises a lot; however, in the current state it is practically useless on node types utilizing CCK fields, even if the're not being used during import. Damn!
Greetings, asb
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | content.txt | 7.82 KB | Robrecht Jacques |
Comments
Comment #1
Robrecht Jacques commentedCould you install and enable the date module? http://drupal.org/project/date.
If it is installed & enabled, could you try to replace
modules/node_import/supported/cck/content.incwith the attached file (rename the old one first in case of trouble and rename that attachmentcontent.inc)?Thanks.
Comment #2
muhleder commentedI was getting similar error messages, but I think my problem was that I was using Date RC2. So the /modules/date/date/date.inc file wasn't there. If I switched the line95 in content.inc to reference the modules/date/date_api.module however it seems to be working so far, but only if I use the datestamp format instead of the date format when I set up my CCK fields.
Comment #3
asb commentedHi Robrecht Jacques,
thank you for the fast answer!
I'm running Content Construction Kit (CCK) 5.x-1.7 and Date 5.x-2.0-rc; yes, both modules are enabled (Content, Content Copy, Fieldgroup, Option Widgets, Text, Date, Date API, Date Popup, and Date Timezone are enabled; Date Copy, Date PHP4, and Date Repeat API are disabled).
> could you try to replace modules/node_import/supported/cck/content.inc with the attached file
Done. The WSOD still appears. Watchdog says:
The include_path parameter "/usr/share/pear" refers to my default input format, PEAR Wiki filter (which imho has nothing to do with the date module, also). Im *not* using datestamp format, but the format dd.mm.yyyy which was one of the reasons I upgraded to Date 5.x-2.0-rc. Most probably this is an incompatibility with the date module; however, imho it shouldn't affect node imports of *one* record into a non-date field.
Greetings, -asb
Comment #4
muhleder commentedDate 5.x-2.0-rc is a complete rewrite of Date v1, which I think is the version supported by Node Import. Content.inc is trying to include a file which doesn't exist in Date v2
As I said I got rid of the error messages by changing line 95 of content.inc to
That's a quick hack to reference the date_api module in my drupal installation, which contains the functions that content.inc tries to call.
I was still getting the WSOD but without the error messages after making this change, but when I removed my date fields and replaced them with datestamp fields it imports just fine. The only difference is the way the date is stored in the database. I converted the dates in my csv from 13/09/2008 format to unix timestamp format 1222387200 and I can now import into the cck datestamp field.
Comment #5
johnalbinSee #227681: Date 2 API breaks node imports with dates