https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29672 --- Comment #40 from David Cook <dcook@prosentient.com.au> --- (In reply to Julian Maurice from comment #39)
(In reply to David Cook from comment #38)
By iterating through all the enabled plugins, loading them, and using $_->can($method), we've created the scenario which causes the problem described in bug 36736
Loading plugins in Koha::Plugins::call is not perfect, but we don't have a "bootstrap" stage that's common to the web app and CLI programs (which would be the perfect time to load plugins IMO), so I believe it's the best we can do at the moment. Of course plugins can break Koha if they do things they're not supposed to :)
What I mean is that Koha::Plugins->call() could use the plugin_methods table to find only the plugins that it needs to load, rather than iterating through all of them. Although thinking about bug 36736 again... you're right. Having a bootstrap stage that loads all plugins is needed, because you never know what plugin is doing something funny deep down in the call stack. Fun! Haha -- You are receiving this mail because: You are watching all bug changes.