OJS 3 Native XML Plugin, Export Issues not working [SOLVED]

Hi, after successful upgrade I have tried to export issues of one journal that we have to migrate to separate domain (idea was to upgrade current system with 15 journals to OJS 3.0.0 and then export issue by issue of specific journal to fresh install of OJS 3.0.0 which will host only that journal).
Export plugin take some time to process command but then it redirect to blank page, with error 500:

“NetworkError: 500 Internal Server Error - http://migracija.ff.uns.ac.rs/index.php/gff/management/importexport/plugin/NativeImportExportPlugin/exportIssues

Error log:

[Wed Sep 21 10:07:14.753605 2016] [fcgid:warn] [pid 28443] [client] mod_fcgid: stderr: PHP Warning:  assert(): Assertion failed in /var/www/clients/client0/web6/web/lib/pkp/plugins/importexport/native/filter/SubmissionFileNativeXmlFilter.inc.php on line 110, referer: http://migracija.ff.uns.ac.rs/index.php/gff/management/importexport/plugin/NativeImportExportPlugin
[Wed Sep 21 10:07:14.753607 2016] [fcgid:warn] [pid 28443] [client] mod_fcgid: stderr: PHP Fatal error:  Call to a member function getUsername() on a non-object in /var/www/clients/client0/web6/web/lib/pkp/plugins/importexport/native/filter/SubmissionFileNativeXmlFilter.inc.php on line 111, referer: http://migracija.ff.uns.ac.rs/index.php/gff/management/importexport/plugin/NativeImportExportPlugin

Looking at the code, it appears that the code is assuming it will find a user matching the submission’s user by id.

From your statement, I’m assuming you are exporting issues from the upgraded OJS 3.0.

This probably means that either the exported issues aren’t including the users, the issue import isn’t preprocessing the users, or the lookup of user by id is a bad strategy.

I think this should probably be reported as a bug in our Git Issues for the PKP library.

Hi @knjigor

The error is due to missing some file information after the migration. S. this GitHub Issue: Can't Export Issues · Issue #1805 · pkp/pkp-lib · GitHub i.e. this PR pkp/pkp-lib#1805 fix file upgrade by bozana · Pull Request #1018 · pkp/ojs · GitHub. You could apply that patch and execute php tools/upgrade.php upgrade again (on your current, upgraded DB). This would probably/hopefully solve the problem.


Thanx for help, but I decided that I will migrate whole system and simply delete journals that I don’t need. This of course doesn’t resolve issue with migration plugin.

I will try next days patch and report if it is working.

I have applied provided patch and it has fixed error.
Thanx for help