March 25 CVS Upgrade Issue

  • I originally installed 1.0.1 and upgraded to March 9 nightly, running upgrade.php. Since then I’ve been using CVS, *not* running upgrade.php. Things have been working flawlessly. Tonight I downloaded March 25 CVS and couldn’t post, on account of new post_date_gmt field in table? Tried to run upgrade.php but it times out. Had the same time-out problem back on March 9 upgrade and the cure was to turn off firewall. This time that doesn’t work. This is test blog on PC localhost running Apache 1.3.27/PHP 4.2.3/MySQL 4.0.0. First question: any other suggestions to cure upgrade.php time-out? Second question: Could I just manually add the post_date_gmt field in mySql, or are there other changes requiring upgrade.php? BTW, I noticed there wasn’t a new upgrade.php file in the CVS. Should there be?

Viewing 4 replies - 1 through 4 (of 4 total)

  • When upgrade-functions.php is new it has everything needed for the upgrade…upgrade.php simply calls functions from that file. The March 25th and on CVS has some problems with the date structure. I’ve been using the previous CVS, which has been working, but every CVS I’ve installed since the 24th or 25th screwed up all of my post times (or at least the display of them) so I go back to one of my backups.

    Thread Starter harpshot

    (@harpshot)

    Well, during the 5 days that passed since I posted, I somehow managed to get past the time-out issue on my local PC test installation. Don’t know why, other than dumb luck. Even practiced doing a new install and everything went fine, including posting comments. Ready for host server. Uploaded everything and did an install. Comments wouldn’t work. The install failed to create the comment_date_gmt field in the comments table. So I ran upgrade.php. Same result. Debated whether to go back and start over with the earlier version of install.php (the present one is brand new CVS). Instead, I added comment_date_gmt manually. Now comments work.
    So, for whoever needs to know about these things, something in the CVS in the last couple of days results in failure to create comment_date_gmt field in the wp_comments table, using either install.php or upgrade.php.

    As usual, don’t use CVS on production servers. ??
    Usually if you want to test CVS, it’s better to install a 1.0.2 WP and then upgrade to CVS with upgrade.php, as sometimes the install.php script goes out of date.
    Upgrade.php never goes out of date.
    For those running CVS and running on date issues after the March 25th nightly, I’ll post instructions on how to clear the issues later.

    What’s the fun in not using the CVS? ?? I love being on the bleeding edge! Of course I learned my lesson once and now always backup my files and database right before upgrading to a CVS.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘March 25 CVS Upgrade Issue’ is closed to new replies.