Exclusive eBooks, Software Solutions, Quality Guaranteed
Web NukeBiz
Welcome to NukeBiz · Members
of 6

 #34 » No upgrade to WeatherHarvest 9.1.0?
 Date Open: May 14, 2008 at 01:39:18    Last Update: May 15, 2008 at 22:11:12 Bugger Off: May 15, 2008 at 22:11:12 
 Description: Installed WH 9.1.0 over 9.0.0 and had this link in Admin > Modules: Version9.0.0.0 Upgrade to 9.1.0

Clicked on Upgrade and got:
Fatal error: Call to undefined method WeatherHarvest::upgrade() in /home/mark/public_html_wp/admin/modules/modules.php on line 159

And sure enough I can't find a upgrade path ...

Do I have to uninstall/re-install (and fight the Admin i/f again) or should it just run - i.e. are there no db changes?
 Request: Bug
 Application: Module
 Module: weatherharvest
 Solution: Foolish error on my part - failed to commit the updated version of cpg_inst.php to cvs, so when I checked out the module it didn't get the updated file. Now fixed.
 Bugger From: Layingback
 Debugger: Phoenix
 Group Access: All Visitors
 DiscussIt Forum: Weather Harvest
 DiscussIt Topic: No upgrade to WeatherHarvest 9.1.0?
 Status: Done
 Priority: High
 Topic Replies:
 May 14, 2008
There are no db changes - the upgrade section is present in cpg_inst.php, albeit empty, so it should have simply continued since it contains "return true;".

Odd that you should encounter such a problem, as I didn't. The same applies to all modules Confused
 May 15, 2008
There are only 3 functions in the 9.1.0 release of WH - I checked the zip again just in case:

function WeatherHarvest()
function install()
function uninstall()

But if there are no db changes then I good to go Wink

For grins I added:

    function upgrade() {

    	return true;


And re-did the upgrade to clear the upload link in Admin > Modules.

 May 15, 2008
hmm, that is odd - I just checked the download and realize that the cpg_inst.php file there is not the one I have in my cvs, which means I've uploaded a zip with the incorrect file.

In fact, what I have done is checked out the module without previously committing the updated file - foolish error.
 May 15, 2008
No problem! Easily done - voice of experience Wink

TortoiseCVS on Windoze is fairly good at bringing that to your attention, but now I'm on Linux (Ubuntu) it's a real problem. Still Meld is a much better file compare, so I end up doing directory-level compares and then commit - from inside Meld!
 May 15, 2008
Well, not the first time I've done that, which is what makes it such a foolish error.

Local cvs is the best thing I ever did - I integrated it within a local DF copy so it presents me with cvs info just the same as on the DF site, saving a lot of command line time.
150 buggers listed, 109 buggered off, 31 declined, 8 on hold.