Callback method registering but not being called for plugin based on StaticPages plugin

[ja2d1o4]

Hi,

Based closely on the static pages plugin, I wrote a blog plugin that adds a small amount of blog functionality (multiple posts, keywords, paging). We’ve been running this plugin under OJS 3.3.0-4

Now I’m in the process of upgrading the plugin to 3.5.0-3 and I’m encountering an issue that I haven’t been able to debug so far.

I followed the example of the 3.5 version of the static pages plugin to upgrade my plugin and I think I’ve covered all the basic changes that are required - the plugin installs without error; the callbacks register with the Hook registry; the front end displays correctly - but the tab at the top of the admin Website Setting page, which normally appears to the right, for example, of the static pages admin tab (when both plugins are enabled), does not appear.

Unfortunately, there are no errors to guide my investigation. Additionally, though I’ve confirmed through debug logging that the callback method callbackShowWebsiteSettingsTabs is registered with the Template::Settings::website Hook, debug logging at the top of the callbackShowWebsiteSettingsTabs method is never called. It is successfully called for the static pages plugin but not my blog plugin, which leads me to suspect that something is failing silently but there is no indication in the logs.

Would it be possible for someone familiar with the 3.5 version of the static pages plugin or with the Hooks section of the codebase to look over my plugin to see if anything jumps out as wrong?

This is the branch in question: GitHub - cul/ojs-blog at ojs35-upgrade · GitHub

Any help would be greatly appreciated.

Thanks,

Jack

[asmecher]

Hi @ja2d1o4,

Try this thread:

[OJS 3.1.2] [Resolved!] Custom Generic Plugin - Triggering Hook Functions

Hi @wangra, This is a bit of gotcha: when you introduce a plugin to the filesystem, some parts of it will work, but because it hasn’t been registered in the database, other parts won’t. The plugin installation process (e.g. plugin gallery) takes care of this, but when you’re coding up a plugin yourself (or avoiding the plugin installation process) you have to register the plugin with the database yourself. To do this, use the lib/pkp/tools/installPluginVersion.php tool. Regards, Alec Smecher …

Make sure your version.xml is accurate, and check afterwards for an entry in the versions table corresponding to your plugin.

Regards,
Alec Smecher
Public Knowledge Project Team

[ja2d1o4]

Thanks for your response. Directing me to look closely at version.xml helped me see that I was providing a fully-qualified class name for the class element. Changing it to the short name fixed the problem.