The plugin isn’t maintained any more, I am afraid, and the version that is available is not compatible with OJS 3.3.
What you probably want to do is update the _parseHtmlContents method with how this now works in 3.3 using the Services API. For instance, the regular HTML Galley plugin:
Unfortunately the parameters passed to a hook are dependant on the hook and the context in which it is used. It’s probably best if you search through the code looking for the name of the hook you want to learn more about, e.g. “ArticleHandler::download” in that case.
okay! I will do so. I only hoped that there is an easier way. But probably the backend is changing quite fast currently and documentation would be old quite fast.
Still, could the PKP-team think about writing documentation for Plugin development? This would be super helpful, I would think!
Thank you for mentioning this documentation. I knew this. It is really basic.
I was talking more towards the possibility to really develop a plugin. How can I setup my development environment to use the PKP lib and OJS classes. How do I mock articles in the database? How can I mock a Smarty object? This would be the stuff I want from the documentation.
The “Release Notebook” for each release covers the main things that have changed between releases from a development perspective; one of the goals of those documents is to help plugin maintainers understand what areas of the code need to be changed in order to add support for the new release.
For 3.3.0, the Release Notebook is available here:
There’s a section called “Submission files” that covers the issue you’re encountering in your first post.
It looks like you’re also interested in automated testing; we’re starting to rely more and more on that ourselves, though there is still room for improvement. Currently we rely on integration testing much more than unit testing. Internally we use Cypress (for browser automation) and Travis (for the VM environment); here are some examples: