Comments on: Wordpress 2.0.5 is out http://coreythompson.com/2006/10/wordpress-205-is-out/ ...but I'm right! Get yer historical hero clay figurines now! Thu, 04 Dec 2008 07:56:43 +0000 http://wordpress.org/?v=2.7-RC1-10026 hourly 1 By: Corey http://coreythompson.com/2006/10/wordpress-205-is-out/comment-page-1/#comment-1464 Corey Sat, 28 Oct 2006 23:43:46 +0000 http://coreythompson.com/?p=635#comment-1464 Thanks for fleshing out what I should have pointed to, Brian. Hear that everyone? Upgrade! If anyone's been to <a href="http://macbros.dnsalias.com/blog/" rel="nofollow">MacBros</a> before and after the upgrade, you can see what Brian is talking about. Way to go. This caused the pages to turn over several times as fast!<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('1464','Corey'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('1464','Corey','Thanks for fleshing out what I should have pointed to, Brian. Hear that everyone? Upgrade!\n\nIf anyone\'s been to <a href=\"http:\/\/macbros.dnsalias.com\/blog\/\" rel=\"nofollow\">MacBros<\/a> before and after the upgrade, you can see what Brian is talking about. Way to go. This caused the pages to turn over several times as fast!'); return false;">Quote</a></div> Thanks for fleshing out what I should have pointed to, Brian. Hear that everyone? Upgrade!

If anyone’s been to MacBros before and after the upgrade, you can see what Brian is talking about. Way to go. This caused the pages to turn over several times as fast!

Reply - Quote
]]> By: MacBros http://coreythompson.com/2006/10/wordpress-205-is-out/comment-page-1/#comment-1463 MacBros Sat, 28 Oct 2006 21:06:03 +0000 http://coreythompson.com/?p=635#comment-1463 Heh, to funny!<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('1463','MacBros'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('1463','MacBros','Heh, to funny!'); return false;">Quote</a></div> Heh, to funny!
Reply - Quote
]]> By: Brian Layman http://coreythompson.com/2006/10/wordpress-205-is-out/comment-page-1/#comment-1462 Brian Layman Sat, 28 Oct 2006 17:44:43 +0000 http://coreythompson.com/?p=635#comment-1462 Thanks for spreading the word about the update. With the number of people still running older releases, and the major security holes that continue to be closed in each 2.0.x release, it is very important to get everyone off of the older versions. The two biggest reasons to upgrade to 2.0.5, as I see it, are: 1. This is, again, major security release. There was a major hole plugged; 2. If you started your blog with version 2.0 or newer, you’re missing a DB index on the post table and that will slow down your site. I’ve provided more detail in a top 5 list <a href="http://www.thecodecave.com/article269" title="The Code Cave" rel="nofollow">on my own site</a>, but you can always look at the official list of all 60 tickets addressed. I use <a href="http://trac.wordpress.org/query?status=closed&milestone=2.0.5&order=priority&desc=1" rel="nofollow">this link</a> to look at it in order of priority. Please continue to convince your friends and everyone on your blog roll to upgrade, it is important. If any of them are worried about upgrading, I’ve included a 35 second upgrade script on my site. It’s been reviewed by the members of the WP-Hackers list. So, it is safe. I’d post the link here, but I’m releasing an updated version of it later today and don’t want the old links floating around. Just look at the Code Cave article link I posted above and follow it from there. 35 seconds for multiple blogs beats 20 minutes to do it by hand.<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('1462','Brian Layman'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('1462','Brian Layman','Thanks for spreading the word about the update. With the number of people still running older releases, and the major security holes that continue to be closed in each 2.0.x release, it is very important to get everyone off of the older versions. The two biggest reasons to upgrade to 2.0.5, as I see it, are:\n1. This is, again, major security release. There was a major hole plugged;\n2. If you started your blog with version 2.0 or newer, you’re missing a DB index on the post table and that will slow down your site.\n\nI’ve provided more detail in a top 5 list <a href=\"http:\/\/www.thecodecave.com\/article269\" title=\"The Code Cave\" rel=\"nofollow\">on my own site<\/a>, but you can always look at the official list of all 60 tickets addressed. I use <a href=\"http:\/\/trac.wordpress.org\/query?status=closed&amp;milestone=2.0.5&amp;order=priority&amp;desc=1\" rel=\"nofollow\">this link<\/a> to look at it in order of priority.\n\nPlease continue to convince your friends and everyone on your blog roll to upgrade, it is important. If any of them are worried about upgrading, I’ve included a 35 second upgrade script on my site. It’s been reviewed by the members of the WP-Hackers list. So, it is safe. I’d post the link here, but I’m releasing an updated version of it later today and don’t want the old links floating around. Just look at the Code Cave article link I posted above and follow it from there. 35 seconds for multiple blogs beats 20 minutes to do it by hand.'); return false;">Quote</a></div> Thanks for spreading the word about the update. With the number of people still running older releases, and the major security holes that continue to be closed in each 2.0.x release, it is very important to get everyone off of the older versions. The two biggest reasons to upgrade to 2.0.5, as I see it, are:
1. This is, again, major security release. There was a major hole plugged;
2. If you started your blog with version 2.0 or newer, you’re missing a DB index on the post table and that will slow down your site.

I’ve provided more detail in a top 5 list on my own site, but you can always look at the official list of all 60 tickets addressed. I use this link to look at it in order of priority.

Please continue to convince your friends and everyone on your blog roll to upgrade, it is important. If any of them are worried about upgrading, I’ve included a 35 second upgrade script on my site. It’s been reviewed by the members of the WP-Hackers list. So, it is safe. I’d post the link here, but I’m releasing an updated version of it later today and don’t want the old links floating around. Just look at the Code Cave article link I posted above and follow it from there. 35 seconds for multiple blogs beats 20 minutes to do it by hand.

Reply - Quote
]]> By: Corey http://coreythompson.com/2006/10/wordpress-205-is-out/comment-page-1/#comment-1461 Corey Sat, 28 Oct 2006 15:39:34 +0000 http://coreythompson.com/?p=635#comment-1461 Glad I could help out (and no mushrooms were involved!). I actually thought that I'd try and risk a spot in time where nobody was perhaps reading, as I wanted to see what a theme I've discovered would look like with a bit of content and a few sub-pages already established. My test blog on my computer is not quite as robust with content. Perhaps I should import this database to play with.<div class="comment-remix-meta"><a href="#" class="replyto" onclick="replyto('1461','Corey'); return false;">Reply</a> - <a href="#" class="quote" onclick="quote('1461','Corey','Glad I could help out (and no mushrooms were involved!). I actually thought that I\'d try and risk a spot in time where nobody was perhaps reading, as I wanted to see what a theme I\'ve discovered would look like with a bit of content and a few sub-pages already established. My test blog on my computer is not quite as robust with content. Perhaps I should import this database to play with.'); return false;">Quote</a></div> Glad I could help out (and no mushrooms were involved!). I actually thought that I’d try and risk a spot in time where nobody was perhaps reading, as I wanted to see what a theme I’ve discovered would look like with a bit of content and a few sub-pages already established. My test blog on my computer is not quite as robust with content. Perhaps I should import this database to play with.
Reply - Quote
]]>