Shared publicly  - 
 
72.4 Million Blogs/Websites Powered by WordPress. 36.2 Million on Their Own Hosting. 12 Million+ Downloads of the Latest Version of WordPress 3.3. Pretty Amazing Stats! #WordPress

http://wpcommunity.com/members/tom-ford/activity/501/
2
1
Tom Ford's profile photoChris Davies (cd34)'s profile photoLorenzo Winfrey's profile photo
9 comments
 
We upgraded over 5000 blogs after 3.3.1 was released that clients were using, fewer than 8% were running 3.3.x.

I did find a 1.5.1 and a few 1.5.2's that were in production.
 
I saw your posting on that...in Matt's San Diego WordCamp video, he touched on the fact that there are a lot of multi-users...but the numbers are still awesome...I started on 1.5! (the upgrade process is so much smoother now than in the olden days once things are in the newer distros)...
 
I think the problem is, no matter how easy you make it, it is a fire and forget thing. We have one client that continues to install 3.2.x because that is the 'package' they zipped up with their templates, plugins, etc. and they install 4-5 WordPress sites for their clients each week.

One client we upgraded, his FTP client noticed something was different, and remirrored the older files over top. He has since changed his FTP to not overwrite newer.

Our monthly scan looks for WordPress versions on a number of machines and lets us know who's running older versions. After getting most of the machines up to 3.3.1, the number of exploits and spam emails we've seen has dropped tremendously.
 
Ya...I've run tech all these years and a large part of it has been fixing sites after people bombed them out on updating...but since the 3's...the backwards compatibility has gotten a lot better...still some plugin issues...but even those are way less...

The last BuddyPress jump though...not so smooth with plugins...but most of the devs that do BP are pretty active and have updates...
 
One thing I've started doing is changing the default wp_ in the MySQL...I see a ton of logic there...

Ya, I read your original post...I do them one by one...obviously that's harder with thousands...but with the database changes from the early versions...back in the day when I had someone on a way back version, I'd actually jump through a couple versions in a sequence, depending on what it was, to be sure to pick up all the table upgrades...it always seemed to work well...
 
The script does call /upgrade.php?step=1 which confirms the upgrade. After upgrading about 1100 of them manually, I got a little braver and we started upgrading using scripts. Generally, taking a chunk of them out of the wpversions file and automating that.

Of the sites we upgraded, we received eight trouble tickets, only one of them was a real problem as the system didn't realize they had installed the Russian version of WordPress. Template breakage was the only real side effect, and I think two plugins that had to be upgraded.

We did the same with timthumb.php upgrades a while back, though, that was a much easier upgrade.
 
I could see how it could get monotonous after 1100! 8 of 5000 isn't so bad...
 
It really wasn't that bad, the wpversions file has a line that has the full path to versions.php:$version=

so, I had the file open on one side, double click, command-right arrow, ./wpu (paste)

and then it displays the constructed url which I would visit and make sure it looked right. The 1100 weren't in one sitting and it was a few of us doing it - I know I did close to 200 on one machine one evening. The 'monster' machine had 585 sites which we did manually, and I thin the other machine we did which was the oldest machine which had the oldest wordpresses had 315 or so. After that, a little awk magic resulted in the blog post that upgraded the machine with 285.
Add a comment...