https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28173 --- Comment #17 from David Cook <dcook@prosentient.com.au> --- (In reply to Olivier Hubert from comment #16)
In my (limited) experience, there is no such thing as a "typical" Koha request. Some requests might trigger several (10-20+ store calls), whereas others will only trigger a few. Even with the performance improvement, I'm not sure this could work in all environments. For example, we have installations with 7-8+ plugins.
I have this same fear.
Would system-wide option to enable / disable the hooks make sense?
As I was reading your comment, I was thinking this same thing! I think this is a really interesting idea actually.
If this is accepted as it stands, I would also prefer the hooks to be named "before_object_store" and "after_object_store", in order to be more consistent.
Makes sense to me too. (Although the wiki is down right now, so I'm not able to do a good review of the existent hooks. A bit telling that we need to rely on the wiki to know what hooks there are too. If we did have a system-wide configuration of hook availability, it would be a nice way of easily seeing what hooks a system implements...) -- You are receiving this mail because: You are watching all bug changes.