Import error with function getFilePath

[sasutton]

I have successfully loaded several XML batch files created manually of past issues from another system into an version 2.2.0.0. I just tried unsuccessfully importing a batch file exported directly from on version 2.1.1.0 into the 2.2 system. I am getting the following error message:

"Fatal error: Call to a member function getFilePath() on a non-object in /usr/local/apache2/htdocs/ojs/plugins/importexport/native/NativeImportExportPlugin.inc.php on line 138"

I found the following post here in the system for what appears to be the same problem at http://pkp.sfu.ca/support/forum/viewtopic.php?f=8&t=1224&p=3801&hilit=function+getFilePath#p3801:

"I'm using the web-based import. The error I was getting was "Call to member function getFilePath() on a non-object in /ojs/plugins/importexport/native/NativeImportExportPlugin.inc.php on line 137" but after I adjusted the file size upload limit that error went away. I then got a db error on the temporary_files type column being null, but Bugzilla #2251 (dropping the column) fixed that. So it now all appears to have worked and imported nicely. Thanks for all your help."

Can you please advise whether my problem might be the same or not and, if so, point me in the right direction to correct the problem. Thanks in advance.

Stuart

[jmacgreg]

Hi Stuart,

My first inclination is to believe that this is a filesize issue -- your first import attempt worked fine as the import tool would've grabbed each file separately from the locations you pointed to in the XML file; but with a dump from a previous OJS instance, the import tool may choke on the size of the XML file itself as all the galleys are Base64-encoded and embedded into it.

Take a look at Alec's advice here:

viewtopic.php?f=8&t=2174&p=7399#p7399

And please let me know if this fixes anything or not.

Cheers,
James

[sasutton]

James, the file size is also what I thought might be causing the problem. Unfortunately (at least for knowing the solution definitively), I solved the problem by relying on the export but substituting in URLs to the pdf files of the papers--something I knew would work (thanks to you).

Stuart