[Koha-bugs] [Bug 31074] Cached plugin code is used in Koha even after changes to plugin (install/upgrade/uninstall)

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31074

Victor Grousset/tuxayo <victor at tuxayo.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |normal

--- Comment #42 from Victor Grousset/tuxayo <victor at tuxayo.net> ---
(In reply to David Cook from comment #41)
> Overall, if folk want to keep going down this path, then by all means they
> should. All I would ask is that they have a configuration option for it in
> koha-conf.xml which defaults to off.

No correctness by default when managing plugins from the UI? (and oops, I
created the ticket as enhancement when it's in fact about fixing bugs)

And before the default value, why needing a way to disable it? What's the
remaining issues? If an instance has plugins UI enabled, then in which case is
that a problem that on plugin install/upgrade/uninstall, a reload is triggered?
It seems and in every case, even in unsupported ones, there will be always a
reasonable number of workers linked to an intance vs the number of threads so
reload time shouldn't be too high.

Should the plugin UI warn that install/upgrade/uninstall operation shouldn't be
done on peak load. Because yes, that's the times even reasonable request stalls
are not a good idea.

-- 
You are receiving this mail because:
You are watching all bug changes.