You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing the latest versions 3.3.0.5 and 3.3.0.4 after checking out a detached head at the tags with git switch -d 3.3.0.5, which includes support for the updated Crossref API, an error is thrown:
PHP Fatal error: Uncaught Error: Class "PKP\\db\\DAORegistry" not found in /var/www/html/ojs/plugins/generic/funding/FundingPlugin.inc.php:59
Stack trace:
#0 /var/www/html/ojs/lib/pkp/classes/plugins/PluginRegistry.inc.php(69): FundingPlugin->register()#1 /var/www/html/ojs/lib/pkp/classes/plugins/PluginRegistry.inc.php(142): PluginRegistry::register()#2 /var/www/html/ojs/lib/pkp/classes/core/Dispatcher.inc.php(133): PluginRegistry::loadCategory()#3 /var/www/html/ojs/lib/pkp/classes/core/PKPApplication.inc.php(362): Dispatcher->dispatch()#4 /var/www/html/ojs/index.php(68): PKPApplication->execute()#5 {main}
thrown in /var/www/html/ojs/plugins/generic/funding/FundingPlugin.inc.php on line 59, referer: https://labs.tib.eu/ojs/index.php/index/admin/settings
An update of pkp-lib from pkp/pkp-lib@abb7a9c to 3_3_0-20 did not resolve the issue.
When installing the latest versions 3.3.0.5 and 3.3.0.4 after checking out a detached head at the tags with
git switch -d 3.3.0.5
, which includes support for the updated Crossref API, an error is thrown:An update of pkp-lib from pkp/pkp-lib@abb7a9c to 3_3_0-20 did not resolve the issue.
The behaviour is similar to what is described in Upgrade failed due to Most Read block plugin [OJS-3.3.0-14 to OJS-3.4.0-1] (HTTP ERROR 500) - Software Support - PKP Community Forum. The plugin had been deleted from the versions table, which reactivated the test instance from white screen of death.
The error appears in the logs when trying to open the routes
index/admin/settings#plugins
Checking out
stable-3_3_0
works.This might be a duplicate of #57.
The text was updated successfully, but these errors were encountered: