Upgrading ojs from 3.4.0.10 to 3.5.0.2 ERROR: PHP Fatal error: Uncaught ValueError: Path cannot be empty

Describe the issue or problem
I’m conducting an upgrade test, migrating the system from version 3.3.0-10 to 3.5.0-2. The upgrades from 3.3.0-10 to 3.3.0-22 and then to 3.4.0-10 were successful; however, an error occurred when upgrading from 3.4.0-10 to 3.5.0-2.

Steps I took leading up to the issue
Execute the upgrade command: php -d memory_limit=2048M tools/upgrade.php upgrade | tee -a upgrade.log

What application are you using?
3.4.0-10

Additional information
PHP Fatal error: Uncaught ValueError: Path cannot be empty in /www/ojs3.5/lib/pkp/classes/task/UpdateRorRegistryDataset.php:250
Stack trace:
#0 /www/ojs3.5/lib/pkp/classes/task/UpdateRorRegistryDataset.php(250): fopen()
#1 /www/ojs3.5/lib/pkp/classes/task/UpdateRorRegistryDataset.php(142): PKP\task\UpdateRorRegistryDataset->processCsv()
#2 /www/ojs3.5/lib/pkp/classes/scheduledTask/ScheduledTask.php(151): PKP\task\UpdateRorRegistryDataset->executeActions()
#3 /www/ojs3.5/lib/pkp/classes/migration/upgrade/v3_5_0/I7135_CreateNewRorRegistryCacheTables.php(60): PKP\scheduledTask\ScheduledTask->execute()
#4 /www/ojs3.5/lib/pkp/classes/install/Installer.php(445): PKP\migration\upgrade\v3_5_0\I7135_CreateNewRorRegistryCacheTables->up()
#5 /www/ojs3.5/lib/pkp/classes/install/Installer.php(298): PKP\install\Installer->executeAction()
#6 /www/ojs3.5/lib/pkp/classes/install/Installer.php(207): PKP\install\Installer->executeInstaller()
#7 /www/ojs3.5/lib/pkp/classes/cliTool/UpgradeTool.php(97): PKP\install\Installer->execute()
#8 /www/ojs3.5/lib/pkp/classes/cliTool/UpgradeTool.php(70): PKP\cliTool\UpgradeTool->upgrade()
#9 /www/ojs3.5/tools/upgrade.php(22): PKP\cliTool\UpgradeTool->execute()
#10 {main}
thrown in /www/ojs3.5/lib/pkp/classes/task/UpdateRorRegistryDataset.php on line 250

Hi @LiFan,

This is caused by an upstream change at RoR; we’ve already filed and fixed it here. You can resolve it by applying this patch in the lib/pkp subdirectory, but we’ll also be releasing OJS/OMP/OPS 3.5.0-3 within a couple days, and it’ll include a fix for this.

Regards,
Alec Smecher
Public Knowledge Project Team

1 Like

I appreciate your prompt response. I’ll attempt to upgrade using a patch, and I’m also looking forward to the 3.5.0-3 release. Thank you again.

1 Like

This topic was automatically closed after 11 days. New replies are no longer allowed.