i just enabled importexportapi. i get these errors (note: i am on php5, though i think thats moot):

EXPORT
Warning: Invalid argument supplied for foreach() in /Library/WebServer/contributions/modules/importexportapi/importexportapi.module on line 778

Warning: Invalid argument supplied for foreach() in /Library/WebServer/contributions/modules/importexportapi/engines/importexportapi_xml_put.inc on line 19

IMPORT
Warning: Unknown column 'title' in 'where clause' query: SELECT uid FROM users WHERE title = 'Fish' in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

Warning: Unknown column 'title' in 'where clause' query: SELECT uid FROM users WHERE title = 'Erggg' in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

Warning: Unknown column 'title' in 'where clause' query: SELECT uid FROM users WHERE title = 'Sail away' in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

Warning: Unknown column 'title' in 'where clause' query: SELECT uid FROM users WHERE title = 'jdfgrg' in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

Warning: Unknown column 'title' in 'where clause' query: SELECT uid FROM users WHERE title = 'utyfufu' in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

Warning: Unknown column 'name' in 'field list' query: SELECT name FROM node WHERE uid = 1 in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

Warning: Unknown column 'mail' in 'field list' query: SELECT mail FROM node WHERE uid = 1 in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

Warning: Unknown column 'name' in 'field list' query: SELECT name FROM node_revisions WHERE uid = 1 in /Library/WebServer/htdocs/dr47/includes/database.mysql.inc on line 120

[Moshe: many more warning like this]

Comments

Jaza’s picture

Jaza commented
Assigned: Unassigned » Jaza
Status: Active » Needs review

Thanks for the report, moshe. I myself experienced similar errors a few days ago, but I thought that I'd squashed them. Clearly I had not - I was easily able to reproduce the errors that you encountered.

I have committed a number of fixes to HEAD - mainly to the 'db' 'put' engine - that get rid of all the database errors that I encountered in my latest round of testing. However, I am leaving this issue at 'needs review', because I don't think we've seen the last of these errors yet. Further testing is definitely needed.

Leaving priority at 'normal', because although the errors are numerous and look very ugly when they appear, the import still seems to work fine despite them.

Also, I was unable to reproduce the PHP 'foreach ' errors that you encountered. This may have been a PHP5-specific bug. Anyway, I have committed a change that wraps the foreach in question in an empty() check, so hopefully this problem is now gone. If problem persists, please report back with further details on how to reproduce.

Jaza’s picture

Jaza commented
Status: Needs review » Fixed

I've just committed a large number of bug fixes for the 'db' 'put' engine, that make the import system much more reliable. I'm going to think positive, act positive, and set this issue to 'fixed'. Hopefully, we've seen the last of the ugly SQL errors during import. However, there are most likely other, more subtle bugs that are still lurking in the import system (if you find them, please file them as new issues).

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)