Ajax Error when importing nodes using content type association

When importing to nodes, and choosing a content type association in the "Basic" configuration in the Feeds UI, I am getting the following error message:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /drupal-7.9/batch?id=78&op=do StatusText: error ResponseText:

Additionally, only one nodes (the first query result) gets imported.
Also, I see warnings in the log (see first comment), and a couple of notices.

Proposed resolution

The messages goes away after changing to "standalone form" on the "Basic" configuration, and all nodes import as planned.

It is not clear, whether the option to select a content type association on the basic page is actually useful, for me, the association in the "Processing" area is sufficient. However, the option should either get removed, or the problem should get fixed.

Remaining tasks

Comments

ursula’s picture

Error messages for this issue in the error logs.

php
Date Tuesday, November 1, 2011 - 13:47
User root
Location http://example.com/batch?id=64&op=do
Referrer http://example.com/batch?op=start&id=64
Warning: array_merge() [function.array-merge]: Argument #2 is not an array in FeedsConfigurable->addConfig() (line 126 of all/modules/feeds/includes/FeedsConfigurable.inc).

php
Date Tuesday, November 1, 2011 - 13:47
User root
Location http://example.com/batch?id=64&op=do
Referrer http://example.com/batch?op=start&id=64
Warning: array_intersect_key() [function.array-intersect-key]: Argument #1 is not an array in FeedsConfigurable->addConfig() (line 128 of sites/all/modules/feeds/includes/FeedsConfigurable.inc).

page not found
Date Tuesday, November 1, 2011 - 13:48
User root
Location http://example.com/content/myimporttitle
Referrer
Message content/myimporttittle
Severity warning

ursula’s picture

Addendum: I get the same Ajax error, when attempting to import too many nodes (tried to import 3838 nodes).
Workaround: import in chunks using limit (limit 2000, limit 2001,2000, etc.).;
Importing 2000 nodes at a time seems to work (at least for me).

vkareh’s picture

These options (standalone form versus Basic/Article/etc. is part of Feeds itself, not Feeds SQL, so they should not be removed.

That said, I will try looking at it and see if there's any way of avoiding these errors when using a content-type specific form.

About the limits, I wonder if this has to do with a database timeout?

I'm also willing to accept patches that address this.

attisan’s picture

hi,

i encounter the same problem when trying to import a rather large set of nodes (about 30k). first i tried to do that by exporting the DB table to a cvs files and than re-import it by feeds (natively supports cvs import).

after realizing this addon module would directly do what i want, i tried to do the very same thing (but without the cvs inter-file) and can't get it to work.

strangely enough though, because the cvs import worked without problems on 128M and standard 30sec php setting ... completely showing the import status with proper status bar updates.

feeds sql refuses to work with 756M and 180sec php settings :-( eventually ending up in apache killing it (500 server error) and the drupal page still showing the "initializing" status, though some 100 nodes were already imported.

i would like to help out on this / or perhaps we could bundle our skills to optimize this module ;-)

greets