Consistency checks - Registered hooks are executable

[Beeta]

Hello,

I just updated to 1.4, after that I run Consistency check and I got this message:

 

These non-executable hooks do not (or at least they shouldn't) hurt your system much. But they contribute to performance degradation, because your system have to unnecessarily load and instantiate the module on every hook execution.

List of errors
Error description	Actions

Module blockcategories registered hook actionAdminLanguagesControllerStatusBefore but does not implement hook handler	
Module custompayments registered hook advancedPaymentOptions but does not implement hook handler	
Module paypal registered hook displayBeforePayment but does not implement hook handler	
Module genzo_krona registered hook actionAdminGenzoKronaPlayersListingResultsModifier but does not implement hook handler	
Module stripe registered hook Header but does not implement hook handler	
Module stripe registered hook displayPaymentRequestButton but does not implement hook handler	
Module stmegamenu registered hook actionProductDelete but does not implement hook handler	
Module stmegamenu registered hook hookActionObjectProductDeleteAfter but does not implement hook handler	
Module stiosslider registered hook displayLeftColumn but does not implement hook handler	
Module stbanner registered hook displayFooter but does not implement hook handler	
Module stfeaturedcategories registered hook displayHomeSecondaryLeft but does not implement hook handler	
Module stblog registered hook displayAnywhere but does not implement hook handler

What I soppose to do now? Contact modules developer? Some module are core one's. p.s. maybe the results was equal with 1.3...

Edited January 18, 2023 by Beeta

[nickz]

3 minutes ago, Beeta said:

p.s. maybe the results was equal with 1.3...

it was or it wasn't? Updated to 1.4 from?

[e-com]

This is not a bug just sloppiness in making of modules. Modules registered hooks for which they do not support these hooks.
In Modules -> Positions, you can safely unhook these modules from these hooks.

[datakick]

It may or may not be bug in module. Usually, it's just some copy'n'paste issue, or forgotten piece of code. But I have seen modules that had spelling mistake in handler function, and therefore didn't work as designed. Fixing those spelling mistakes actually fixed some bug in the module (in this particular case, it was cache invalidation)

In any case, module author should look at it. 

For core modules, we have already fixed most of these issues. For example, blockcategories is fixed in version 3.0.3

https://github.com/thirtybees/blockcategories/commit/f242b651ff078c1b69474f4a028fa2fe336fe695

 

[Beeta]

On 1/18/2023 at 8:30 PM, datakick said:

For core modules, we have already fixed most of these issues. For example, blockcategories is fixed in version 3.0.3

https://github.com/thirtybees/blockcategories/commit/f242b651ff078c1b69474f4a028fa2fe336fe695

I already updated to 3.0.3 blockcategories, I can proceed to fix or it should be already fixed and I stumble upon another little bug?