I just upgraded to the new 1.5.1 release by running svn up. Total upgrade time? 3 seconds. That’s hard to beat. Unfortunately updates like mine don’t bump the counter.
I just upgraded to the new 1.5.1 release by running svn up. Total upgrade time? 3 seconds. That’s hard to beat. Unfortunately updates like mine don’t bump the counter.
3 seconds? Sweet. Think I’ll give it a try right now.
w00t! I’m going to do it tonight.
From what I’ve seen, it’s almost a little humble to be calling this WordPress 1.5.1. Lots of the changes are substantial and refine WordPress in smart, elegant ways.
The upgrade went smooth however when attempting a clean, new, install for a new blog, using 1.5.1, I received the following error after creating wp-config.php:
Fatal error: Call to undefined function: get_bloginfo() in /home/.bambalona/jarkolicious/newsite/wp-includes/wp-db.php on line 304
The file wp-includes/template-functions-general.php exists and get_bloginfo() is a function within that so any idea why this error might be happening?
Matt: How about a short tutorial on upgrading to the latest WordPress via SVN? Your method. It would probably go a long way in the way people upgrade to WordPress and probably the closest to automating WordPress upgrades. 3 seconds? Wow!
I’m getting this:
Fatal error: Call to undefined function: get_bloginfo() in …/wp-includes/wp-db.php on line 304
Is there any other way to fix this without downgrading to MySQL 4.0.24? I’m doing a website for a friend, and I don’t have shell access. I uploaded everything (FTP), but I’m getting this error when I try to run the install. Please help!
Nevermind. All of my information was correct, but I didn’t realize that the database was hosted somewhere other than ‘localhost’. Hope my epiphany helps someone else!
Minor point of confusion for me: I downloaded the 1.5.1 tar file and installed it. However, my admin console told me I was still running 1.5 (in the footer). I was worried the upgrade had failed, but in turns out the version.php file still says “1.5” instead on “1.5.1”. Just a heads up.
“svn up” may not bump the counter – but “svn co” could, and “svn up” could still log something – all you need are svn’s post-commit hooks I believe.
Seems you’ve broke your “Times when I have posted during the last month” at the bottom. 😡 At least I can’t see it any longer, could see it before.
Just wrote this up for you ^_^
How to use SVN to Update WordPress