[Koha-bugs] [Bug 31074] Plugin metadata is kept in cache after uninstalling a plugin

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

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

--- Comment #14 from David Cook <dcook at prosentient.com.au> ---
(In reply to Fridolin Somers from comment #13)
> I must say we at Biblibre do not allow plugins install via UI so we install
> via script with a refresh of memcached then plack (this order is important).

For many years, I've wanted to disable the plugin install via UI and only
handle it via CLI script. Glad to know I'm not the only one!

I haven't disabled the UI, but in practice I typically manage plugins for
libraries, so I'll upload via the UI, refresh memcached, and then do a graceful
reload of Plack.

> I know PHP with persistence (PHP-FPM) manages that by knowing changes in
> sources, I dont know how.

PHP natively uses OpCache which re-validates cached scripts based on file
modification timestamps.  OpCache also has functions for dealing with its
cached scripts as well.

It looks like it uses shared memory for the cached code, which I suppose is how
it handles the child process scenario...

Perl doesn't have a mechanism like it.

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