[geeklog-devel] Upgrade bug in 1.8.0
websitemaster at cogeco.net
Sat May 28 12:01:58 EDT 2011
I have been on Geeklog.net and the bug tracker a few times throughout today
without any problems.
>> I guess if we decouple the upgrade process for the core plugins at that
point and let it run at the end of the upgrade / migrate process - just like
for non-core plugins - it should work.
Sounds like the best solution to me (since that is also how the Plugin admin
The only other solution I thought of and quickly discarded was keeping track
of the Geeklog versions that each plugin upgrade supports.
Well, back to working on the forum plugin...
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: May-28-11 11:51 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] Upgrade bug in 1.8.0
> (I haven't looked at the code yet) Doesn't migrate check the min
> Geeklog version required for the Calendar plugin in the autoinstall.php?
There's a hard-coded upgrade_CalendarPlugin() call in lib-upgrade.php for
the upgrade from 1.4.1 to 1.5.0 which triggers this. I guess if we decouple
the upgrade process for the core plugins at that point and let it run at the
end of the upgrade / migrate process - just like for non-core plugins - it
should work. >though, since I'm not sure what else may lurk between 1.5.0
and 1.8.0 regarding plugin upgrades ...
P.S. Anyone else having DNS problems with geeklog.net (all subdomains)
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel