Comments on: Guide to Disaster: How The Tech Team Handled WordPress Security Flaw http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/ Web Technology and Real Life Merge Sat, 06 Mar 2010 03:27:38 +0000 hourly 1 http://wordpress.org/?v=3.0-alpha By: HART (1-800-HART) http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91359 HART (1-800-HART) Thu, 24 May 2007 05:18:41 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91359 I've finally managed to use the <a href="http://www.zirona.com/software/wordpress-instant-upgrade">InstantUpgrade plugin</a> and that sure has made upgrading faster. Once comfortable with this auto-upgrading, I still intend to try one of these all-site-upgrade scripts! But I halted in the middle of upgrading, because I was quite disappointed with version 2.2. Firstly, because it makes my <a href="http://fredfred.net/skriker/index.php/iimage-browser">Iimage Browser Plugin</a> not work properly. Actually, there is no Secondly. I mean, I hate Wordpress's built-in image loading - and was quite fond of Iimage Browser. I’ve finally managed to use the InstantUpgrade plugin and that sure has made upgrading faster. Once comfortable with this auto-upgrading, I still intend to try one of these all-site-upgrade scripts!

But I halted in the middle of upgrading, because I was quite disappointed with version 2.2. Firstly, because it makes my Iimage Browser Plugin not work properly. Actually, there is no Secondly. I mean, I hate Wordpress’s built-in image loading – and was quite fond of Iimage Browser.

]]> By: Brian Layman http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91217 Brian Layman Wed, 23 May 2007 19:51:51 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91217 And a good many of us do agree that php5 would be a good addition and would allow us to do some very good things natively. BUT getting a concensus that the switch WILL happen would be next to impossible on that list this far in advance. The list just doesn't work that way. A more plausible goal would be to get group agreement that WP3 could potentially have a PHP5 requirement AND that enhancements implemented in a way that require PHP5 will not be thrown out but added to a WP3 tag. Then people might grudgingly agree... And a good many of us do agree that php5 would be a good addition and would allow us to do some very good things natively. BUT getting a concensus that the switch WILL happen would be next to impossible on that list this far in advance. The list just doesn’t work that way.

A more plausible goal would be to get group agreement that WP3 could potentially have a PHP5 requirement AND that enhancements implemented in a way that require PHP5 will not be thrown out but added to a WP3 tag.

Then people might grudgingly agree…

]]> By: Aaron Brazell http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91206 Aaron Brazell Wed, 23 May 2007 19:15:37 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91206 Kevin- My advice, don't get personally attached to that conversation. It happens every few months. Convincing the mass of developers that PHP5 is a worthy jump is a marathon, not a sprint. Kevin- My advice, don’t get personally attached to that conversation. It happens every few months. Convincing the mass of developers that PHP5 is a worthy jump is a marathon, not a sprint.

]]> By: Kevin http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91118 Kevin Wed, 23 May 2007 15:29:22 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91118 More of a "what is proper product support" than being scared. I'm also feeling a little grumpy after following the thread about WP-3/PHP5 on the mailing list ealier this week. The fact that many were not even willing to discuss it because "its so/to far away" and "lets just focus on the next release" just left a bad taste in my mouth. I completed the upgrade (to the release version, not the SVN) and it was relatively painless. This is inspite of my own wierd setup involving symlinks and such. Of course my site is also very "young" with few plugins and a very basic theme. -- Kevin http://technogeek.org/ More of a “what is proper product support” than being scared. I’m also feeling a little grumpy after following the thread about WP-3/PHP5 on the mailing list ealier this week. The fact that many were not even willing to discuss it because “its so/to far away” and “lets just focus on the next release” just left a bad taste in my mouth.
I completed the upgrade (to the release version, not the SVN) and it was relatively painless. This is inspite of my own wierd setup involving symlinks and such. Of course my site is also very “young” with few plugins and a very basic theme.

–
Kevin
http://technogeek.org/

]]> By: Dave Zatz http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91098 Dave Zatz Wed, 23 May 2007 14:39:31 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91098 I would have also preferred 2.1.4, though I hear Aaron in that 2.2 is more of an incremental upgrade with the new update timelines. Many kudos to Aaron and Brian -- I ran that upgrade script and in just a few minutes I made the move from 2.1.3 -> 2.2. Less stress and less work than what I typically do. Nice work, guys! I owe you both beer. I would have also preferred 2.1.4, though I hear Aaron in that 2.2 is more of an incremental upgrade with the new update timelines.

Many kudos to Aaron and Brian — I ran that upgrade script and in just a few minutes I made the move from 2.1.3 -> 2.2. Less stress and less work than what I typically do. Nice work, guys! I owe you both beer.

]]> By: Aaron Brazell http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91084 Aaron Brazell Wed, 23 May 2007 13:50:08 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91084 Kevin, moving to WP2.2 is nothing like previous major upgrades such as 1.5 -> 2.0 or 2.0 -> 2.1. Functionally, 2.2 is pretty similar to what 2.1.4 would look like. Don't let the versioning scare you. Kevin, moving to WP2.2 is nothing like previous major upgrades such as 1.5 -> 2.0 or 2.0 -> 2.1. Functionally, 2.2 is pretty similar to what 2.1.4 would look like. Don’t let the versioning scare you.

]]> By: Kevin http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91072 Kevin Wed, 23 May 2007 12:51:31 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91072 I still don't understand why Wordpress would rather force all wordpress users to upgrade to 2.2 (which is brand new, and really untested compared to "older" versions) rather than supply a patch for their existing user base. I didn't want to upgrade to 2.2, but they are in effect forcing me to by not supporting a "legacy" version of their product which is not even 2 MONTHS old. That is just horrible product support no matter how easy it is to upgrade to 2.2, or what new features it offers. -- Kevin http://technogeek.org/ I still don’t understand why Wordpress would rather force all wordpress users to upgrade to 2.2 (which is brand new, and really untested compared to “older” versions) rather than supply a patch for their existing user base. I didn’t want to upgrade to 2.2, but they are in effect forcing me to by not supporting a “legacy” version of their product which is not even 2 MONTHS old. That is just horrible product support no matter how easy it is to upgrade to 2.2, or what new features it offers.

–
Kevin
http://technogeek.org/

]]> By: Mark Evans http://technosailor.com/2007/05/23/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/comment-page-1/#comment-91053 Mark Evans Wed, 23 May 2007 11:49:03 +0000 http://technosailor.com/guide-to-disaster-how-the-tech-team-handled-wordpress-security-flaw/#comment-91053 Good to see the b5media tech team working so well. And it's nice to have a "team". :) Mark Good to see the b5media tech team working so well. And it’s nice to have a “team”. :)

Mark

]]>