CiviCRM Community Forums (archive)

this is weird.  I successfully imported contributions earlier today.  One time.  But the second time, and all other times after, after the "Import Now" button, I get this:

"Fatal error: Call to undefined method CRM_Core_Error::fields() in /home/soncnv/webapps/v2/sites/all/modules/civicrm/api/v2/utils.v2.php on line 162"

How could I have imported once, and then, using the same import mapping (and even tried a new one after that to be sure), I now get THIS error?

The only thing that changed is that I added a new payment instrument.  Also, of course, the file is different....  but it passed the initial error check, and is in the exact same format as the first one!

Any ideas?  Any help appreciated.  Thanks in advance.

Civi version is actually 3.4.3 not 3.4.1- I need to update that...

PS:  I've also gotten this error sometimes today:

"warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/soncnv/webapps/v2/sites/all/modules/civicrm/CRM/Core/Error.php on line 575.
warning: array_merge() [function.array-merge]: Argument #2 is not an array in /home/soncnv/webapps/v2/sites/all/modules/civicrm/CRM/Core/Error.php on line 575."

have you confirmed that no data at all was imported? I would be trying a sample file to import based on your original successful one as i would be suspecting something in the data, therefore would want to rule that out as the culprit

Is there any way I can get the import process to ONLY use api v2?  Could this be a problem with api v2?

Hi, Eileen, and others- I'm not sure how to add that patch?  I get confused when I go to that link-.  I actually DID implement the workaround at the top- copying the Contribute file to v3 api- but that doesn't even sound like the right thing to do if everything for contributions imports needs to be done in the v2 api... so then I look through that log and see you wrote "CRM-8398 - revert back to calling API v2 function directly - NB - I don't expect format_create to become part of apiv3 as an external function"- but then I don't see how to install a patch to keep everything in v2?  So first, how do I install the patch?  I'm at 3.4.4 now in my CiviCRM version.

My other concern also is that this isn't a v3-to-v2 issue completely.  My initial error occurred AFTER ONE SUCCESSFUL import:

"Fatal error: Call to undefined method CRM_Core_Error::fields() in /home/soncnv/webapps/v2/sites/all/modules/civicrm/api/v2/utils.v2.php on line 162"

** So it leaves me wondering in there's a temp file causing this?  I keep emptying the Drupal cache and templates_c directory- where is the folder where files get up.loaded?  Could THAT be the problem?  Who WROTE the "fields()" function call/method?  Someone must know who wrote that function call and that person should be able to recognize why the method might be seen as undefined?

Also, ever since upgrading to 3.4.3, and now also with 3.4.4, I KEEP getting these errors, constantly:

"warning: Invalid argument supplied for foreach() in {homedir}/sites/all/modules/civicrm/api/v3/utils.php on line 1521.
warning: array_merge() [function.array-merge]: Argument #2 is not an array in {homedir}/sites/all/modules/civicrm/CRM/Core/Error.php on line 575."

I have no idea what they mean. 

I feel like jumping off a bridge because we need contributions to be imported, and it worked once, then just plain stopped.

HELP!  Please help!  Someone who knows this code, please help!  I will be your humble servant forever. 

Our PHP version is currently 5.2.11.

OK, so I applied that patch and it didn't help. 

Well so I discover that part of the file had imported.  Also I learned from reading online that CiviCRM import does not like files with blank final columns and it doesn't like files saved as CSV from Excel using Windows format.  You have to save in MS-DOS CSV format if using Excel.  And you should at a final column of zeroes to your file if you otherwise end with blank final column fields.

I deleted all contributions, period, and started reimporting from scratch.  The importer started worked again, on the first file.  It was the second file where I had the problem originally, though, so I'm going to make the changes noted above- MS-DOS and zeroes, and will re-post here if the importer repeats the error that I was getting before.

can you post an anonymised sample here - just the header row and a single row of data?

OK. I'll post some aononymized data in the next few days, thanks.