https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21073
--- Comment #98 from Kyle M Hall <[email protected]> --- Yes, this is expected behavior and is a compromise to keep existing plugins from breaking. If we had whitelisted methods then any plugin using 'non-standard' plugin methods would have broken. The next step in plugins evolution is to allow each plugin to specify which methods it wants to declare ( on top of the 'official' ones ) and add those to the database instead. Then we can use this manual scanning method as a fallback for plugins that don't specify their available methods in the metadata. (In reply to Andrew Isherwood from comment #96) > I pulled latest master today and received this bug, looks great, nice job! > > I spotted something though and am not sure if it's expected behaviour or a > bug. > > The database update that adds the plugin_methods table and then calls > Koha::Plugins::InstallPlugins to populate it. However, upon looking at the > plugin_methods table, I'm seeing far more methods than are exposed by my > single installed plugin (CLA Permissions Check) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
