https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42870
--- Comment #1 from David Cook <[email protected]> --- When I first wrote this (10 minutes ago), I was thinking plugin hook, but... we could actually use Module::Pluggable for this like we do in Koha/SuggestionEngine.pm and Koha/RecordProcess.pm, but taken a step further. Instead of just using a "Koha::<Functionality>" search_path, we can use "Koha::<Functionality>,Koha::Plugin::<Functionality>". We just need to ensure that we have Koha::Plugin::* within our @INC. We can honour existing Koha::Plugin functionality by handling the Koha plugin logic (around installed, enabled, methods, etc) within a helper function within the "hook". But then that being said... it would be up to the plugin author to implement that, and that's messy. Really we could just couple Module::Pluggable "Koha::Email::Transport" AND Koha Plugins with the email_transport hook. Put them in a hash, and then use configuration in the smtp_servers table to choose which one to go with. It does mean a database change, but a very light one... and one which can lead to a lot of possibility -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
