[geeklog-devel] Plugin upgrade failure (was: More automation)
Joe Mucchiello
jmucchiello at yahoo.com
Sat May 21 16:54:24 EDT 2011
> The problem was that while we replaced the plugin's functions.inc, we were
>still
> calling the upgrade function from the old copy, which was still in memory at
>this
> point.
This has always bothered me. Why is plugin_upgrade_foo in functions.inc? It
should
be in the autoinstall.php file that only gets loaded by the installer code.
There
are lots of ways this could be done in the future to avoid the COM_refresh. Not
that any of those methods are useful days before 1.8 goes live. Maybe the
location
of functions within the plugins can be targeted for 1.9 (also needed for my
comments
a few months ago about reducing Geeklog's memory footprint).
More information about the geeklog-devel
mailing list