Plugin can't find version.xml during upgrade about sword

[asmecher]

@jnugent, is the plugins/generic/sword directory present/populated in the ojs-stable-3_1_1 codebase for that install? It shouldn't be -- see https://github.com/pkp/ojs/tree/ojs-stable-3_1_1/plugins/generic. Or was it installed from this repo separately?

[jnugent]

@asmecher - it had been previously installed from the repository. Looking at the journal now, there's a .gitmodules file in the directory pointing to https://github.com/swordapp/swordappv2-php-library. The upgrade procedure would have been to bring the rest of the repository up to ojs-stable-3_1_1, update the sub modules, and then run the regular upgrade CLI command.

[asmecher]

Can you try to narrow down why getPluginPath would be returning a blank? I can't think of a good reason that would be happening.

[kaitlinnewson]

Hey @asmecher, wanted to let you know that we've also been running into this issue, and removing the sword plugin has allowed us to run the upgrade script successfully.

[jnugent]

Hey @kaitlinnewson - I'm trying to find some time to investigate this further, also.

[nils-stefan-weiher]

@jnugent
@asmecher
I still have this issue with OJS 3.1.2-1 upgrading from 3.1.1
The problem is the child SwordImportExportPlugin class, which the SwordPlugin registers through a callback triggered by PluginRegistry::loadCategory.
The installer tries to load a version file for the SwordImportExportPlugin, because it was loaded by PluginRegistry::loadCategory.

The SwordImportExportPlugin class is missing the method for getPluginPath(), and so no path is returned, it should return the path of the parent method.

Will try to fix this and test locally and then open a PR.

[asmecher]

@isgrim, sounds like you've tracked down a tricky one!