It was a lot of work upgrading 3.0.5!
I guess the programmers forgot it existed, and never having a clear upgrade path I was reluctant to give it a try. Maybe it was only out for a few days and so no one cared to support it.
In brief, I had to go back all the way to the 2.3.6 Perl version upgrade script and create a couple of new rows in tables to get myself from 3.0.5 to 3.0.6. Stuff like this (see quote below)
Eventually I did got there, and then just had to poke into phpmyadmin to reset the settings database to select vb3 instead of vb2. I sure wish that setting were in config-sys.
After that, it was just running through all the upgrade scripts. The last upgrade gave me some errors because it said none of the tables to be dropped were even there. I don't know about that, maybe the submit button bounced.
In any case, I am happy to be through with it!
Quote:
The 2.3.6 upgrade script has different columns in it, like (in red)
$query[] = "CREATE TABLE useralbums (id {$Style['small']}int(4) NOT NULL auto_increment,albumname varchar(255) NOT NULL default '',parent int(5) NOT NULL default '0',description varchar(255) default NULL,isprivate varchar(4) NOT NULL default 'no',PRIMARY KEY (id),KEY parent(parent)) TYPE=MyISAM;";
No I have to sit down with the code and hash out all the changes to get it up to 3.0.6
I really hate trying to upgrade this stuff. It's unfortunate that the programmers pretend that 3.0.5 never existed in the upgrade tree.
|
Linear Mode
