# Wed Jan 16 16:51:56 2008
# Query_time: 1  Lock_time: 0  Rows_sent: 0  Rows_examined: 0
use theclari_clarionReport;
UPDATE wp_options SET option_value = 'O:9:\"MagpieRSS\":19:{s:6:\"parser\";i:0;s:12:\"current_item\";a:0:{}s:5:\"items\";a:50:{i:0;a:7:{s:5:\"title\";s:50:\"Weblog Tools Collection: Configuring WP Permalinks\";s:4:\"guid\";s:79:\"http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/\";s:4:\"link\";s:79:\"http://weblogtoolscollection.com/archives/2008/01/16/configuring-wp-permalinks/\";s:11:\"description\";s:5325:\"<p><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/permalinks.png\" alt=\"Pretty Permalinks\" /></p>
<p>Quite often, we hear of the terms (permalinks or pretty permalinks) which can also be called SEO-friendly URLs. These URLs are not only SEO friendly, but I believe they are human friendly as well. By default, WordPress uses URLs that look like a mishmash of letters and numbers with a few question marks mixed in for good measure. These types of links are frowned upon by search engine spiders and as a human being, they are also hard to read.</p>
<p>Fortunately, WordPress provides a way for us to change this linking structure to something understandable. WordPress calls these Permalinks. Permalink settings can be configured a number of different ways. One of the ways to quickly configure permalinks is by choosing one of the <strong>Common Options</strong>. These common options include:</p>
<p><strong>Default</strong> - http://www.domain.com/?p=123</p>
<p><strong>Date and name based</strong> - http://www.domain.com/2008/01/15/sample-post/</p>
<p><strong>Numeric</strong> - http://www.domain.com/archives/123</p>
<p>There is no sense in using the default option so choose either <strong>Date and name based</strong> or <strong>Numeric</strong> if you don&#8217;t feel like tinkering with the Custom Structure.</p>
<p>The custom structure of the permalinks settings area allows you to customize the way permalinks are displayed by using any combination of the following permalink tags.</p>
<blockquote><p><strong>%year%</strong> - 4-digit year (for example, 2008)</p>
<p><strong>%monthnum%</strong> - 2-digit month (for example, 01 for January)</p>
<p><strong>%day%</strong> - 2-digit day (for example, 15)</p>
<p><strong>%hour%</strong> - 2-digit hour of the day (for example, 20 for 10PM)</p>
<p><strong>%minute%</strong> - 2-digit minute (for example, 50)</p>
<p><strong>%second%</strong> - 2-digit second (for example, 24)</p>
<p><strong>%postname%</strong> - Text separated by dashes which usually ends up being the post name. (for example, configuring-wp-permalinks)</p>
<p><strong>%post_id%</strong> - The unique, numerical ID of the post (for example, 124)</p>
<p><strong>%category% </strong>- The text of the category name that the post is filed in (for example, how-to)</p>
<p><strong>%author%</strong> -  Text of the post author&#8217;s name (for example, ronald-huereca)</p>
<p><strong>Example of custom structure in use:</strong></p>
<p><strong>Custom Structure:</strong> /%year%/%monthnum%/%day%/</p>
<p><strong>Link Output:</strong> http://www.domain.com/2008/01/16/</p></blockquote>
<p>Make sure that you include the back slashes at the beginning of the custom structure, after each tag and at the end. This will ensure that WordPress writes the correct rules in the .htaccess file via mod_rewrite.</p>
<p><a href=\"http://www.jeffro2pt0.com\" title=\"http://www.jeffro2pt0.com\" target=\"_blank\">For my own blog</a>, I seem to have done fairly well in the search engines by using the Custom Structure method and using the %postname% tag. I can&#8217;t say for sure which combination would do better or worst for search engines. The only thing I can suggest is that you configure your permalinks to look whats best for you.</p>
<h2>*WARNING*</h2>
<p>Changing the structure of your permalinks affects all of the permalinks on your blog. This is important to know because search engines will have indexed posts on your site via their permalinks. If you change the permalink structure mid stream, you will end up invalidating all of those links.</p>
<h2>What to do if you don&#8217;t have a .htaccess file?</h2>
<p>If you notice that you don&#8217;t have a .htaccess file within the same directory as your WordPress installation, you can create one by first creating a blank .txt file and saving the file as htaccess.txt. Upload this file via  FTP to the same folder that houses your WordPress installation. Once the file is uploaded, set the permissions to the file as <strong>666</strong>. Next, rename the file to .htaccess. Now you should have a blank .htaccess file for which WordPress can write the proper permalink rules to.</p>
<h2>Servers That Don&#8217;t Use Apache Or mod_rewrite.</h2>
<p>If the webhosting server you are on does not have the apache module mod_rewrite enabled, you can still use the permalink settings in WordPress by placing <strong>index.php</strong> in front of any custom permalink tags.</p>
<p><strong>For example:</strong> /index.php/%year%/%monthnum%/%day%/</p>
<p><strong>Equals:</strong> http://www.domain.com/index.php/2008/01/16/</p>
<p>Using index.php in this way eliminates the need for a .htaccess file.</p>
<p>I hope this little primer on how to configure your permalinks within WordPress was helpful. I&#8217;ve seen too many blogs out on the net that have yet to take advantage of this awesome feature. As I&#8217;ve said before, using any sort of permalink structure is better than the WP default. Not only is it beneficial in terms of SEO, but it also makes it easier for human beings to see at a glance, what a particular link is pointing to without having to visit the page.</p>
<p>If you use the custom structure aspect of permalinks, I&#8217;d be very interested in knowing which configuration of permalink tags you have chosen to use and why.</p>\";s:7:\"pubdate\";s:31:\"Wed, 16 Jan 2008 22:15:06 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jeffro2pt0\";}s:7:\"summary\";s:5325:\"<p><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/permalinks.png\" alt=\"Pretty Permalinks\" /></p>
<p>Quite often, we hear of the terms (permalinks or pretty permalinks) which can also be called SEO-friendly URLs. These URLs are not only SEO friendly, but I believe they are human friendly as well. By default, WordPress uses URLs that look like a mishmash of letters and numbers with a few question marks mixed in for good measure. These types of links are frowned upon by search engine spiders and as a human being, they are also hard to read.</p>
<p>Fortunately, WordPress provides a way for us to change this linking structure to something understandable. WordPress calls these Permalinks. Permalink settings can be configured a number of different ways. One of the ways to quickly configure permalinks is by choosing one of the <strong>Common Options</strong>. These common options include:</p>
<p><strong>Default</strong> - http://www.domain.com/?p=123</p>
<p><strong>Date and name based</strong> - http://www.domain.com/2008/01/15/sample-post/</p>
<p><strong>Numeric</strong> - http://www.domain.com/archives/123</p>
<p>There is no sense in using the default option so choose either <strong>Date and name based</strong> or <strong>Numeric</strong> if you don&#8217;t feel like tinkering with the Custom Structure.</p>
<p>The custom structure of the permalinks settings area allows you to customize the way permalinks are displayed by using any combination of the following permalink tags.</p>
<blockquote><p><strong>%year%</strong> - 4-digit year (for example, 2008)</p>
<p><strong>%monthnum%</strong> - 2-digit month (for example, 01 for January)</p>
<p><strong>%day%</strong> - 2-digit day (for example, 15)</p>
<p><strong>%hour%</strong> - 2-digit hour of the day (for example, 20 for 10PM)</p>
<p><strong>%minute%</strong> - 2-digit minute (for example, 50)</p>
<p><strong>%second%</strong> - 2-digit second (for example, 24)</p>
<p><strong>%postname%</strong> - Text separated by dashes which usually ends up being the post name. (for example, configuring-wp-permalinks)</p>
<p><strong>%post_id%</strong> - The unique, numerical ID of the post (for example, 124)</p>
<p><strong>%category% </strong>- The text of the category name that the post is filed in (for example, how-to)</p>
<p><strong>%author%</strong> -  Text of the post author&#8217;s name (for example, ronald-huereca)</p>
<p><strong>Example of custom structure in use:</strong></p>
<p><strong>Custom Structure:</strong> /%year%/%monthnum%/%day%/</p>
<p><strong>Link Output:</strong> http://www.domain.com/2008/01/16/</p></blockquote>
<p>Make sure that you include the back slashes at the beginning of the custom structure, after each tag and at the end. This will ensure that WordPress writes the correct rules in the .htaccess file via mod_rewrite.</p>
<p><a href=\"http://www.jeffro2pt0.com\" title=\"http://www.jeffro2pt0.com\" target=\"_blank\">For my own blog</a>, I seem to have done fairly well in the search engines by using the Custom Structure method and using the %postname% tag. I can&#8217;t say for sure which combination would do better or worst for search engines. The only thing I can suggest is that you configure your permalinks to look whats best for you.</p>
<h2>*WARNING*</h2>
<p>Changing the structure of your permalinks affects all of the permalinks on your blog. This is important to know because search engines will have indexed posts on your site via their permalinks. If you change the permalink structure mid stream, you will end up invalidating all of those links.</p>
<h2>What to do if you don&#8217;t have a .htaccess file?</h2>
<p>If you notice that you don&#8217;t have a .htaccess file within the same directory as your WordPress installation, you can create one by first creating a blank .txt file and saving the file as htaccess.txt. Upload this file via  FTP to the same folder that houses your WordPress installation. Once the file is uploaded, set the permissions to the file as <strong>666</strong>. Next, rename the file to .htaccess. Now you should have a blank .htaccess file for which WordPress can write the proper permalink rules to.</p>
<h2>Servers That Don&#8217;t Use Apache Or mod_rewrite.</h2>
<p>If the webhosting server you are on does not have the apache module mod_rewrite enabled, you can still use the permalink settings in WordPress by placing <strong>index.php</strong> in front of any custom permalink tags.</p>
<p><strong>For example:</strong> /index.php/%year%/%monthnum%/%day%/</p>
<p><strong>Equals:</strong> http://www.domain.com/index.php/2008/01/16/</p>
<p>Using index.php in this way eliminates the need for a .htaccess file.</p>
<p>I hope this little primer on how to configure your permalinks within WordPress was helpful. I&#8217;ve seen too many blogs out on the net that have yet to take advantage of this awesome feature. As I&#8217;ve said before, using any sort of permalink structure is better than the WP default. Not only is it beneficial in terms of SEO, but it also makes it easier for human beings to see at a glance, what a particular link is pointing to without having to visit the page.</p>
<p>If you use the custom structure aspect of permalinks, I&#8217;d be very interested in knowing which configuration of permalink tags you have chosen to use and why.</p>\";}i:1;a:7:{s:5:\"title\";s:24:\"Matt: Sun Acquires MySQL\";s:4:\"guid\";s:28:\"http://photomatt.net/?p=3163\";s:4:\"link\";s:51:\"http://photomatt.net/2008/01/16/sun-acquires-mysql/\";s:11:\"description\";s:226:\"<p><a href=\"http://blogs.sun.com/jonathan/entry/winds_of_change_are_blowing\">Jonathan Schwartz&#8217;s Blog: Helping Dolphins Fly</a>, in which Sun buys MySQL for a billion dollars. A bargain! I think this is a good thing.</p>\";s:7:\"pubdate\";s:31:\"Wed, 16 Jan 2008 18:26:39 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:226:\"<p><a href=\"http://blogs.sun.com/jonathan/entry/winds_of_change_are_blowing\">Jonathan Schwartz&#8217;s Blog: Helping Dolphins Fly</a>, in which Sun buys MySQL for a billion dollars. A bargain! I think this is a good thing.</p>\";}i:2;a:7:{s:5:\"title\";s:31:\"Matt: MacWorld WordPress Meetup\";s:4:\"guid\";s:28:\"http://photomatt.net/?p=3162\";s:4:\"link\";s:58:\"http://photomatt.net/2008/01/15/macworld-wordpress-meetup/\";s:11:\"description\";s:141:\"<p>Tomorrow, Wednesday, <a href=\"http://upcoming.yahoo.com/event/350458/\">there&#8217;s going to be a WordPress meetup at Chaat Cafe</a>.</p>\";s:7:\"pubdate\";s:31:\"Wed, 16 Jan 2008 01:34:24 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:141:\"<p>Tomorrow, Wednesday, <a href=\"http://upcoming.yahoo.com/event/350458/\">there&#8217;s going to be a WordPress meetup at Chaat Cafe</a>.</p>\";}i:3;a:7:{s:5:\"title\";s:27:\"Matt: Macworld Liveblogging\";s:4:\"guid\";s:28:\"http://photomatt.net/?p=3161\";s:4:\"link\";s:54:\"http://photomatt.net/2008/01/15/macworld-liveblogging/\";s:11:\"description\";s:1033:\"<p><a href=\"http://glencampbell.name/2008/01/15/rating-the-livebloggers/\">Rating the Livebloggers</a> talks about three of the blogs that were covering Steve Jobs keynote where he announced the <a href=\"http://gizmodo.com/345115/macbook-air-hands+on\">Macbook Air</a>. The one with the highest rating, <a href=\"http://live.gizmodo.com/\">Gizmodo&#8217;s Live site</a>, is hosted on WordPress.com as a <a href=\"http://wordpress.com/vip-hosting/\">VIP</a>, which is how they managed to avoid the problems that hit <a href=\"http://www.crunchgear.com/2008/01/15/a-macworld-apology/\">Crunchgear</a>, <a href=\"http://www.engadget.com/2008/01/15/yeah-about-those-server-problems/\">Engadget</a>, <a href=\"http://blog.twitter.com/2008/01/macworld.html\">Twitter</a>, <a href=\"http://paul.kedrosky.com/archives/2008/01/15/steve_jobs_prov.html\">et al</a>. <a href=\"http://flickr.com/photos/photomatt/2196355052/\">Here&#8217;s a Flickr picture showing how spiky the traffic can be</a>. (That&#8217;s from the iPhone keynote, not the latest one.)</p>\";s:7:\"pubdate\";s:31:\"Tue, 15 Jan 2008 23:38:06 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:1033:\"<p><a href=\"http://glencampbell.name/2008/01/15/rating-the-livebloggers/\">Rating the Livebloggers</a> talks about three of the blogs that were covering Steve Jobs keynote where he announced the <a href=\"http://gizmodo.com/345115/macbook-air-hands+on\">Macbook Air</a>. The one with the highest rating, <a href=\"http://live.gizmodo.com/\">Gizmodo&#8217;s Live site</a>, is hosted on WordPress.com as a <a href=\"http://wordpress.com/vip-hosting/\">VIP</a>, which is how they managed to avoid the problems that hit <a href=\"http://www.crunchgear.com/2008/01/15/a-macworld-apology/\">Crunchgear</a>, <a href=\"http://www.engadget.com/2008/01/15/yeah-about-those-server-problems/\">Engadget</a>, <a href=\"http://blog.twitter.com/2008/01/macworld.html\">Twitter</a>, <a href=\"http://paul.kedrosky.com/archives/2008/01/15/steve_jobs_prov.html\">et al</a>. <a href=\"http://flickr.com/photos/photomatt/2196355052/\">Here&#8217;s a Flickr picture showing how spiky the traffic can be</a>. (That&#8217;s from the iPhone keynote, not the latest one.)</p>\";}i:4;a:7:{s:5:\"title\";s:58:\"Weblog Tools Collection: WordPress Theme Releases for 1/14\";s:4:\"guid\";s:88:\"http://weblogtoolscollection.com/archives/2008/01/15/wordpress-theme-releases-for-114-3/\";s:4:\"link\";s:88:\"http://weblogtoolscollection.com/archives/2008/01/15/wordpress-theme-releases-for-114-3/\";s:11:\"description\";s:4738:\"<h3></h3>
<h1></h1>
<h3>One Column Themes</h3>
<p><strong>DePo Skinny</strong></p>
<p>A very simple one column theme with easy integration for your Flickr pictures at the top of the page. It is a real bare bone theme and is only 500 pixels wide. Though DePo Skinny does not have a sidebar it makes it up in the footer with a bottom sidebar to display additional information.</p>
<p>Being a one column theme main advertisement options are within the post itself.</p>
<p><em>Widget Ready: </em>No Sidebar Options</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em><strong>Invalid</strong> XHTML 1.0 Transitional with 30 errors |<strong> </strong>Valid CSS</p>
<p><a href=\"http://powazek.com/depo-skinny\" target=\"_blank\">Demo</a> | <a href=\"http://powazek.com/depo-skinny.zip\" target=\"_blank\">Download</a></p>
<h3>Two Column Themes</h3>
<p><strong>Twister 2.0</strong></p>
<p>Twister 2.0 is made up of dark colors with a mix of gray and black with on a grayish background. The links are white in color and easy to spot with the darkish background. However the text color is harder to read in bright lights. This is an update over the earlier version which includes CSS code cleanup a fix for sidebar in IE6 and a new addition of 3 new columns in the footer.</p>
<p>Overall a good looking theme which is a bit more than simple. Main flaw is that there is very limited advertisement options.</p>
<p><em>Widget Ready: </em>Yes</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em>Valid XHTML 1.0 Transitional | <strong>Invalid</strong> CSS with 90 warnings</p>
<p><a href=\"http://www.refueled.net/demo/index.php?wptheme=Twister+2.0\" target=\"_blank\">Demo</a> | <a href=\"http://www.refueled.net/lounge/go.php?http://refueled.net/downloads/Twister2.zip\" target=\"_blank\">Download</a></p>
<p><strong>Codelog</strong></p>
<p>Codelog is a minimalistic two column theme with sparse use of colors. The theme consists of a sidebar and navigation to the left side. The right side consists of the content area.</p>
<p>Codelog theme is quite simple and makes use of 3-4 colors. Advertising options are limited to the content area.</p>
<p><em>Widget Ready: </em>No</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em>Valid XHTML 1.1 | Valid CSS</p>
<p><a href=\"http://www.codelog.net/codelog-theme\" target=\"_blank\">Demo</a> | <a href=\"http://www.codelog.net/download/codelog-0.1.zip\" target=\"_blank\">Download</a></p>
<h3>Three Column Themes</h3>
<p><strong>Amazing Grace</strong></p>
<p>Amazing Grace is a fast loading theme made with light colors that are variants of green. There are two levels of menus one on the top of the page and one included in the header which are quite diversified to gain maximum user attention on the top of the page.</p>
<p>The link colors are a bit dull and a darker shade would look more better. Other than that a good theme which can be optimized to include better advertisement options.</p>
<p><em>Widget Ready: Yes</em></p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em><strike><strong>Invalid</strong> XHTML 1.0 Transitional with 45 errors</strike> Valid XHTML 1.0 Transitional| Valid CSS</p>
<p><a href=\"http://www.prelovac.com/vladimir/\" target=\"_blank\">Demo</a> | <a href=\"http://www.prelovac.com/vladimir/download-manager.php?id=4\" target=\"_blank\">Download</a></p>
<p><strong>ColorblindS</strong></p>
<p>Colorblinds is a dark 3 column theme with minimal use of colors, the background is made up of gray and black with small squares and rectangles forming part of the background image. The text is again gray with the links a mix of variations of green. Comes built with a drop down menu which I don&#8217;t see would be useful for regular blogs. Overall quite a simple theme and good for blogs which do not want much fanfare.</p>
<p>The major backdrop is advertising options are quite limited for both contextual as well as banner ads.</p>
<p><em>Widget Ready: </em>Yes</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE7, Flock and Opera browsers. In IE6 I could see some color loss in the content area.</p>
<p><em>Validations: </em>Valid XHTML 1.0 Transitional | Valid CSS</p>
<p><a href=\"http://aventhusiast.com/demo2/\" target=\"_blank\">Demo</a> | <a href=\"http://aventhusiast.com/downloads/ColorblindS.zip\" target=\"_blank\">Download</a></p>\";s:7:\"pubdate\";s:31:\"Tue, 15 Jan 2008 15:30:16 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:12:\"Keith Dsouza\";}s:7:\"summary\";s:4738:\"<h3></h3>
<h1></h1>
<h3>One Column Themes</h3>
<p><strong>DePo Skinny</strong></p>
<p>A very simple one column theme with easy integration for your Flickr pictures at the top of the page. It is a real bare bone theme and is only 500 pixels wide. Though DePo Skinny does not have a sidebar it makes it up in the footer with a bottom sidebar to display additional information.</p>
<p>Being a one column theme main advertisement options are within the post itself.</p>
<p><em>Widget Ready: </em>No Sidebar Options</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em><strong>Invalid</strong> XHTML 1.0 Transitional with 30 errors |<strong> </strong>Valid CSS</p>
<p><a href=\"http://powazek.com/depo-skinny\" target=\"_blank\">Demo</a> | <a href=\"http://powazek.com/depo-skinny.zip\" target=\"_blank\">Download</a></p>
<h3>Two Column Themes</h3>
<p><strong>Twister 2.0</strong></p>
<p>Twister 2.0 is made up of dark colors with a mix of gray and black with on a grayish background. The links are white in color and easy to spot with the darkish background. However the text color is harder to read in bright lights. This is an update over the earlier version which includes CSS code cleanup a fix for sidebar in IE6 and a new addition of 3 new columns in the footer.</p>
<p>Overall a good looking theme which is a bit more than simple. Main flaw is that there is very limited advertisement options.</p>
<p><em>Widget Ready: </em>Yes</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em>Valid XHTML 1.0 Transitional | <strong>Invalid</strong> CSS with 90 warnings</p>
<p><a href=\"http://www.refueled.net/demo/index.php?wptheme=Twister+2.0\" target=\"_blank\">Demo</a> | <a href=\"http://www.refueled.net/lounge/go.php?http://refueled.net/downloads/Twister2.zip\" target=\"_blank\">Download</a></p>
<p><strong>Codelog</strong></p>
<p>Codelog is a minimalistic two column theme with sparse use of colors. The theme consists of a sidebar and navigation to the left side. The right side consists of the content area.</p>
<p>Codelog theme is quite simple and makes use of 3-4 colors. Advertising options are limited to the content area.</p>
<p><em>Widget Ready: </em>No</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em>Valid XHTML 1.1 | Valid CSS</p>
<p><a href=\"http://www.codelog.net/codelog-theme\" target=\"_blank\">Demo</a> | <a href=\"http://www.codelog.net/download/codelog-0.1.zip\" target=\"_blank\">Download</a></p>
<h3>Three Column Themes</h3>
<p><strong>Amazing Grace</strong></p>
<p>Amazing Grace is a fast loading theme made with light colors that are variants of green. There are two levels of menus one on the top of the page and one included in the header which are quite diversified to gain maximum user attention on the top of the page.</p>
<p>The link colors are a bit dull and a darker shade would look more better. Other than that a good theme which can be optimized to include better advertisement options.</p>
<p><em>Widget Ready: Yes</em></p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE6, IE7, Flock and Opera browsers.</p>
<p><em>Validations: </em><strike><strong>Invalid</strong> XHTML 1.0 Transitional with 45 errors</strike> Valid XHTML 1.0 Transitional| Valid CSS</p>
<p><a href=\"http://www.prelovac.com/vladimir/\" target=\"_blank\">Demo</a> | <a href=\"http://www.prelovac.com/vladimir/download-manager.php?id=4\" target=\"_blank\">Download</a></p>
<p><strong>ColorblindS</strong></p>
<p>Colorblinds is a dark 3 column theme with minimal use of colors, the background is made up of gray and black with small squares and rectangles forming part of the background image. The text is again gray with the links a mix of variations of green. Comes built with a drop down menu which I don&#8217;t see would be useful for regular blogs. Overall quite a simple theme and good for blogs which do not want much fanfare.</p>
<p>The major backdrop is advertising options are quite limited for both contextual as well as banner ads.</p>
<p><em>Widget Ready: </em>Yes</p>
<p><em>Compatibility: </em>There were no issues that I saw with this theme on Firefox 2+, IE7, Flock and Opera browsers. In IE6 I could see some color loss in the content area.</p>
<p><em>Validations: </em>Valid XHTML 1.0 Transitional | Valid CSS</p>
<p><a href=\"http://aventhusiast.com/demo2/\" target=\"_blank\">Demo</a> | <a href=\"http://aventhusiast.com/downloads/ColorblindS.zip\" target=\"_blank\">Download</a></p>\";}i:5;a:7:{s:5:\"title\";s:57:\"Weblog Tools Collection: Suggestions For Plugin Standards\";s:4:\"guid\";s:86:\"http://weblogtoolscollection.com/archives/2008/01/14/suggestions-for-plugin-standards/\";s:4:\"link\";s:86:\"http://weblogtoolscollection.com/archives/2008/01/14/suggestions-for-plugin-standards/\";s:11:\"description\";s:10605:\"<p><em>This post is not written by me but is reproduced, with permission, from a post in the <a href=\"http://weblogtoolscollection.com/news/topic/suggestions-for-plugin-standards\">Weblog Tools Collection News Forums</a>. It was written by <a href=\"http://www.sunrisedancer.com/weathervane/\">Weathervane</a>. Since  Frank has downloaded 530 plus plugins, and most of his thoughts are well expressed and documented, this post might trigger some good conversation. Please chime in.</em></p>
<p class=\"post\">As a new WordPress blogger, I wanted to customize my installation, so I began a review of the available plugins. My first installation of WordPress was version 2.3.1. Because this version was a significant change, there was a list of v2.3.1-compatible plugins, of which I downloaded and tried most of them.</p>
<p>Since then, I’ve downloaded 530± plugins (this was what’s left after deleting extensions of commercial services), and tried/tested most of them. Five-hundred± is an incredible number and rivals, I think, Photoshop actions or plugins—and there are lots of those. The WordPress plugins community is impressively prolific.</p>
<p>Whenever I’ve had a problem with a plugin, I’ve added a text file to the plugin’s folder. (If it was a “Fatal Error,” “Warning,” SQL error, etc., I’ve pasted the error in the file.) Then I’ve gone to the author’s site and added a comment telling them about the error, including my version information for WordPress, MySQL, PHP, server, and browser. (I’ve frequently heard back from the author with their help.)</p>
<p>About blog comments for plugin pages: It sure is nice to have lots of comments but there are two issues that make them tedious when they’re about a technical issue: trackbacks, praise.</p>
<blockquote><p> Maybe praise could be responded to with a thanks and deleted; it just clutters the list when you’re also using the comments for technical support. We have to scan through all that before we find answers. If we can find the answer, we won’t waste your time duplicating a question you’ve answered, and being disappointed when you don’t respond. (How &#8217;bout using a rating plugin so visitors can leave behind evidence of their appreciation.)</p>
<p>Those trackbacks/pingbacks are the most unusable gibberish. “[…] blah blah, yada yada […]” makes no sense to the average person. (Developers/engineers talking amongst each other has been an obstacle for computer users since the microcomputer was popularized by the IBM PC and the Apple.) I understand that authors want traffic to their site but it’s just as easy to do by adding your URL to your comment entry—most comment forms have a “your Web site” input.</p></blockquote>
<p>Your blog should be as creative as you want it to be when it’s blogging but it needs some standardizing when it’s about technical content, like plugins. A lot of plugin authors are already good about how they prepare their downloads. Establishing a standard, however, is mostly for the user. Below is a short list of recommendations for plugin standards—from a user’s point-of-view.</p>
<p><strong>Naming Conventions</strong></p>
<ol>
<li>Do not append your WordPress plugins with “wp-“ or “wp_.” We know it’s for WordPress, it was in your description. Use an evocative name even if it’s only “joe’s-.“ It’s not just you. When ASP was popular, everything (it seemed) was called asp this and asp that (as in asp calendar, asp blog, asp faq, and on and on).</li>
<li>Tell us where we’ll find your plugin access. If your plugin options are in the Admin Area under Options, say so.</li>
<li>Don’t create an Admin. Area menu item. Your plugin access has a home in Options or Management or within the other existing Admin. Area menu items.</li>
<li>Do not add your plugin access in an unexpected Admin. Area menu item, such as a Plugins submenu item.</li>
</ol>
<p><strong>Operations Convention:</strong></p>
<ol>
<li>It would help us if authors would either agree to include update notice capability in their plugins or let us know if it does not have it. This way we can schedule to occasionally visit their site’s plugin page.</li>
<li>It would be a great help if plugins were always updated and tested in the latest version of WordPress. Too often a plugin is said to be compatible with version 2 or higher but activating it in version 2.3 or higher fails.</li>
<li>Clearly state any conditions required for your plugin. Some plugins must be in their own folder (even if it’s only a one-page plugin); state if the folder must be named the way you provided it in your download file. Also state whether or not a one-page plugin can be renamed.</li>
<li>Clearly state—in user language—what we need to do to get your plugin result. Please don&#8217;t say, &#8220;Place the <em>if (function_exists(&#8217;timeofdeath&#8217;)) {timeofdeath(); }</em> function on your page.&#8221; We&#8217;re not savvy enough to know that what you actually want us to put in the page is <em>&lt;?php if (function_exists(&#8217;timeofdeath&#8217;)) {timeofdeath(); } ?&gt;</em>.<br />
And let us know where in our template to insert your function. An instruction such as, &#8220;Once it’s activated in WordPress, you can call it from your WordPress template using the yada_yada() function&#8221; is unhelpful to the untutored.</li>
<li>If the operation of a plugin is theme-dependant, how will we know that? There seem to be a lot of questions (usually as comments in the plugin&#8217;s page) whose answer relates to the blogger&#8217;s theme. Can the author can help us identify what needs to be in our theme/template for the plugin to work?</li>
<li>I&#8217;ve begun to learn enough PHP to appreciate the value of &#8220;if (function_exists &#8230;.&#8221; That helps to gracefully fail the function if something&#8217;s happened to the function.</li>
<li>If your plugin requires a Key or API or database file (for your IP-related plugin), as you know the URL to get one could you include the URL? We can go hunting around, say Google, until we find the Google Map API but it would be thoughtful to include that URL.</li>
</ol>
<p><strong>Structural Conventions:</strong></p>
<ol>
<li>Have a unified file set for your plugin. You may have instructions at your plugin page but including a readme file and a link file in your download helps.</li>
<li>The structure of the download file really helps us identify the nature of your plugin files and how to install them:<br />
* If your plugin is only <strong>one file</strong> then put it in a subfolder called “plugins.” Everything else should be in the root folder. When your plugin download is uncompressed we’d have a folder with your readme, a URL shortcut, and any screen capture files. Within this folder is a second folder called /plugins containing your plugin file.	* If your plugin has <strong>multiple files</strong>, then instead of /plugins, your folder would have an expressive name. It would help if the name of the subfolder was the same as the name we’re going to see listed in the Admin Area Plugins list.</p>
<p>* Now for the biggie: Some plugins have files that go into <strong>multiple folders</strong> (/plugins, with others going elsewhere, like /wp-admin). The plugin could uncompress to a folder called /installation with two folders in it: /wp-admin and /wp-includes/plugins, containing their respective files—or something like that. With this structure I only have to drop the folders in /installation into my WordPress folder and it&#8217;s done.</li>
<li>It would help us users if readme files contained a standard set of topics:</li>
</ol>
<blockquote>
<ul>
<li>Plugin name (as we&#8217;ll see it in the Plugins listing)</li>
<li>Plugin version</li>
<li>Plugin URL</li>
<li>Demo URL(s)</li>
<li>Author</li>
<li>Author&#8217;s URL</li>
<li>Author&#8217;s email or contact page URL</li>
<li>WP Version compatibility</li>
<li>System requirement(s)</li>
<li>Description</li>
<li>Features</li>
<li>Release notes (what you&#8217;ve changed since the last version)</li>
<li>Screen capture description(s) (if you included captures)</li>
<li>Installation instructions (including structural requirements, if any)</li>
<li>Configuration options (including where to find the option/management form(s)</li>
<li>Usage (function parameters, with output examples if practical)</li>
<li>Donation URL (if you&#8217;ve got one)</li>
</ul>
</blockquote>
<p>If these topics are clearly written, there&#8217;s no need for a FAQ.</p>
<p><strong>Nice Gestures</strong></p>
<ol>
<li>User testing. In business, there&#8217;s User Requirements Testing (URT). The people who commissioned the work test the application to ensure it meets the application flow they described in their requirements. There is another testing format that seems to have disappeared from the corporation, let&#8217;s call it Real Time Testing (RTT). I wrote about my experience with a plugin I really liked, <a href=\"http://www.sunrisedancer.com/weathervane/?p=114\">Thinking It Through: The DG Review Site Plugin</a>. I wish the author had given the plugin to a non-coder, blogger friend to try-out. The plugin&#8217;s a real nice idea but &#8230;.</li>
<li>If you include images that you made using software that stores it&#8217;s originals in a specific format—like Photoshop, Illustrator—include them so we can customize them for our site design.</li>
<li>We should maintain a list of existing plugin names, so that authors won’t duplicate plugin names. Microsoft did this a long time ago for various Windows objects/components. It cuts-out confusion.</li>
<li>Someday, it would be nice if the WordPress would focus on plugins. Say, something that assists in installing them. A Manage or Options submenu, with a browse button to select the file or the folder to be added to /plugins. It would require some thinking but the WordPress people are pretty good thinkers.</li>
<li>You should be using your plugin on your site, if for no other reason than to show us it works—it gives us courage. If your plugin page says, There&#8217;s an example of my plugin running in my sidebar, then have it running there. Occasionally check your plugin page to see that everything is up-to-date and correct.</li>
</ol>
<p>Admittedly, this must seem ungrateful of me. Authors took the time to code, freely offered their work, and I&#8217;m suggesting a little more work. I think some standards would cut-down blogger frustration, requests for help, and give us all more time for blogging (or coding).</p>\";s:7:\"pubdate\";s:31:\"Tue, 15 Jan 2008 00:15:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Mark Ghosh\";}s:7:\"summary\";s:10605:\"<p><em>This post is not written by me but is reproduced, with permission, from a post in the <a href=\"http://weblogtoolscollection.com/news/topic/suggestions-for-plugin-standards\">Weblog Tools Collection News Forums</a>. It was written by <a href=\"http://www.sunrisedancer.com/weathervane/\">Weathervane</a>. Since  Frank has downloaded 530 plus plugins, and most of his thoughts are well expressed and documented, this post might trigger some good conversation. Please chime in.</em></p>
<p class=\"post\">As a new WordPress blogger, I wanted to customize my installation, so I began a review of the available plugins. My first installation of WordPress was version 2.3.1. Because this version was a significant change, there was a list of v2.3.1-compatible plugins, of which I downloaded and tried most of them.</p>
<p>Since then, I’ve downloaded 530± plugins (this was what’s left after deleting extensions of commercial services), and tried/tested most of them. Five-hundred± is an incredible number and rivals, I think, Photoshop actions or plugins—and there are lots of those. The WordPress plugins community is impressively prolific.</p>
<p>Whenever I’ve had a problem with a plugin, I’ve added a text file to the plugin’s folder. (If it was a “Fatal Error,” “Warning,” SQL error, etc., I’ve pasted the error in the file.) Then I’ve gone to the author’s site and added a comment telling them about the error, including my version information for WordPress, MySQL, PHP, server, and browser. (I’ve frequently heard back from the author with their help.)</p>
<p>About blog comments for plugin pages: It sure is nice to have lots of comments but there are two issues that make them tedious when they’re about a technical issue: trackbacks, praise.</p>
<blockquote><p> Maybe praise could be responded to with a thanks and deleted; it just clutters the list when you’re also using the comments for technical support. We have to scan through all that before we find answers. If we can find the answer, we won’t waste your time duplicating a question you’ve answered, and being disappointed when you don’t respond. (How &#8217;bout using a rating plugin so visitors can leave behind evidence of their appreciation.)</p>
<p>Those trackbacks/pingbacks are the most unusable gibberish. “[…] blah blah, yada yada […]” makes no sense to the average person. (Developers/engineers talking amongst each other has been an obstacle for computer users since the microcomputer was popularized by the IBM PC and the Apple.) I understand that authors want traffic to their site but it’s just as easy to do by adding your URL to your comment entry—most comment forms have a “your Web site” input.</p></blockquote>
<p>Your blog should be as creative as you want it to be when it’s blogging but it needs some standardizing when it’s about technical content, like plugins. A lot of plugin authors are already good about how they prepare their downloads. Establishing a standard, however, is mostly for the user. Below is a short list of recommendations for plugin standards—from a user’s point-of-view.</p>
<p><strong>Naming Conventions</strong></p>
<ol>
<li>Do not append your WordPress plugins with “wp-“ or “wp_.” We know it’s for WordPress, it was in your description. Use an evocative name even if it’s only “joe’s-.“ It’s not just you. When ASP was popular, everything (it seemed) was called asp this and asp that (as in asp calendar, asp blog, asp faq, and on and on).</li>
<li>Tell us where we’ll find your plugin access. If your plugin options are in the Admin Area under Options, say so.</li>
<li>Don’t create an Admin. Area menu item. Your plugin access has a home in Options or Management or within the other existing Admin. Area menu items.</li>
<li>Do not add your plugin access in an unexpected Admin. Area menu item, such as a Plugins submenu item.</li>
</ol>
<p><strong>Operations Convention:</strong></p>
<ol>
<li>It would help us if authors would either agree to include update notice capability in their plugins or let us know if it does not have it. This way we can schedule to occasionally visit their site’s plugin page.</li>
<li>It would be a great help if plugins were always updated and tested in the latest version of WordPress. Too often a plugin is said to be compatible with version 2 or higher but activating it in version 2.3 or higher fails.</li>
<li>Clearly state any conditions required for your plugin. Some plugins must be in their own folder (even if it’s only a one-page plugin); state if the folder must be named the way you provided it in your download file. Also state whether or not a one-page plugin can be renamed.</li>
<li>Clearly state—in user language—what we need to do to get your plugin result. Please don&#8217;t say, &#8220;Place the <em>if (function_exists(&#8217;timeofdeath&#8217;)) {timeofdeath(); }</em> function on your page.&#8221; We&#8217;re not savvy enough to know that what you actually want us to put in the page is <em>&lt;?php if (function_exists(&#8217;timeofdeath&#8217;)) {timeofdeath(); } ?&gt;</em>.<br />
And let us know where in our template to insert your function. An instruction such as, &#8220;Once it’s activated in WordPress, you can call it from your WordPress template using the yada_yada() function&#8221; is unhelpful to the untutored.</li>
<li>If the operation of a plugin is theme-dependant, how will we know that? There seem to be a lot of questions (usually as comments in the plugin&#8217;s page) whose answer relates to the blogger&#8217;s theme. Can the author can help us identify what needs to be in our theme/template for the plugin to work?</li>
<li>I&#8217;ve begun to learn enough PHP to appreciate the value of &#8220;if (function_exists &#8230;.&#8221; That helps to gracefully fail the function if something&#8217;s happened to the function.</li>
<li>If your plugin requires a Key or API or database file (for your IP-related plugin), as you know the URL to get one could you include the URL? We can go hunting around, say Google, until we find the Google Map API but it would be thoughtful to include that URL.</li>
</ol>
<p><strong>Structural Conventions:</strong></p>
<ol>
<li>Have a unified file set for your plugin. You may have instructions at your plugin page but including a readme file and a link file in your download helps.</li>
<li>The structure of the download file really helps us identify the nature of your plugin files and how to install them:<br />
* If your plugin is only <strong>one file</strong> then put it in a subfolder called “plugins.” Everything else should be in the root folder. When your plugin download is uncompressed we’d have a folder with your readme, a URL shortcut, and any screen capture files. Within this folder is a second folder called /plugins containing your plugin file.	* If your plugin has <strong>multiple files</strong>, then instead of /plugins, your folder would have an expressive name. It would help if the name of the subfolder was the same as the name we’re going to see listed in the Admin Area Plugins list.</p>
<p>* Now for the biggie: Some plugins have files that go into <strong>multiple folders</strong> (/plugins, with others going elsewhere, like /wp-admin). The plugin could uncompress to a folder called /installation with two folders in it: /wp-admin and /wp-includes/plugins, containing their respective files—or something like that. With this structure I only have to drop the folders in /installation into my WordPress folder and it&#8217;s done.</li>
<li>It would help us users if readme files contained a standard set of topics:</li>
</ol>
<blockquote>
<ul>
<li>Plugin name (as we&#8217;ll see it in the Plugins listing)</li>
<li>Plugin version</li>
<li>Plugin URL</li>
<li>Demo URL(s)</li>
<li>Author</li>
<li>Author&#8217;s URL</li>
<li>Author&#8217;s email or contact page URL</li>
<li>WP Version compatibility</li>
<li>System requirement(s)</li>
<li>Description</li>
<li>Features</li>
<li>Release notes (what you&#8217;ve changed since the last version)</li>
<li>Screen capture description(s) (if you included captures)</li>
<li>Installation instructions (including structural requirements, if any)</li>
<li>Configuration options (including where to find the option/management form(s)</li>
<li>Usage (function parameters, with output examples if practical)</li>
<li>Donation URL (if you&#8217;ve got one)</li>
</ul>
</blockquote>
<p>If these topics are clearly written, there&#8217;s no need for a FAQ.</p>
<p><strong>Nice Gestures</strong></p>
<ol>
<li>User testing. In business, there&#8217;s User Requirements Testing (URT). The people who commissioned the work test the application to ensure it meets the application flow they described in their requirements. There is another testing format that seems to have disappeared from the corporation, let&#8217;s call it Real Time Testing (RTT). I wrote about my experience with a plugin I really liked, <a href=\"http://www.sunrisedancer.com/weathervane/?p=114\">Thinking It Through: The DG Review Site Plugin</a>. I wish the author had given the plugin to a non-coder, blogger friend to try-out. The plugin&#8217;s a real nice idea but &#8230;.</li>
<li>If you include images that you made using software that stores it&#8217;s originals in a specific format—like Photoshop, Illustrator—include them so we can customize them for our site design.</li>
<li>We should maintain a list of existing plugin names, so that authors won’t duplicate plugin names. Microsoft did this a long time ago for various Windows objects/components. It cuts-out confusion.</li>
<li>Someday, it would be nice if the WordPress would focus on plugins. Say, something that assists in installing them. A Manage or Options submenu, with a browse button to select the file or the folder to be added to /plugins. It would require some thinking but the WordPress people are pretty good thinkers.</li>
<li>You should be using your plugin on your site, if for no other reason than to show us it works—it gives us courage. If your plugin page says, There&#8217;s an example of my plugin running in my sidebar, then have it running there. Occasionally check your plugin page to see that everything is up-to-date and correct.</li>
</ol>
<p>Admittedly, this must seem ungrateful of me. Authors took the time to code, freely offered their work, and I&#8217;m suggesting a little more work. I think some standards would cut-down blogger frustration, requests for help, and give us all more time for blogging (or coding).</p>\";}i:6;a:7:{s:5:\"title\";s:60:\"Weblog Tools Collection: CoverItlive.com: Liveblog any event\";s:4:\"guid\";s:87:\"http://weblogtoolscollection.com/archives/2008/01/14/coveritlivecom-liveblog-any-event/\";s:4:\"link\";s:87:\"http://weblogtoolscollection.com/archives/2008/01/14/coveritlivecom-liveblog-any-event/\";s:11:\"description\";s:638:\"<p><a href=\"http://www.coveritlive.com/\">CoverItlive.com</a> is a free (for now) service that allows you to live blog events  and publish items directly to any publishing platform. Now this is pretty commonplace and can easily be done with WordPress (and a few extra plugins) but CoverItLive makes it easier and quicker to embed a variety of media and interact with your readers in real time. There is also an instant replay function, which as inane as that might be, might become handy at some point. Now I barely ever liveblog anything, but I can see a lot of use for this at conferences.<br />
Have you liveblogged anything before?</p>\";s:7:\"pubdate\";s:31:\"Mon, 14 Jan 2008 15:45:05 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Mark Ghosh\";}s:7:\"summary\";s:638:\"<p><a href=\"http://www.coveritlive.com/\">CoverItlive.com</a> is a free (for now) service that allows you to live blog events  and publish items directly to any publishing platform. Now this is pretty commonplace and can easily be done with WordPress (and a few extra plugins) but CoverItLive makes it easier and quicker to embed a variety of media and interact with your readers in real time. There is also an instant replay function, which as inane as that might be, might become handy at some point. Now I barely ever liveblog anything, but I can see a lot of use for this at conferences.<br />
Have you liveblogged anything before?</p>\";}i:7;a:7:{s:5:\"title\";s:31:\"Matt: WordPress in South Africa\";s:4:\"guid\";s:28:\"http://photomatt.net/?p=3159\";s:4:\"link\";s:58:\"http://photomatt.net/2008/01/13/wordpress-in-south-africa/\";s:11:\"description\";s:728:\"<p><a href=\"http://blogs.thetimes.co.za/desousa\">Paul De Sousa</a> writes in: &#8220;One of South Africa&#8217;s largest media groups, Avusa, which owns most of the countries BIGGEST newspapers is now using WordPress. Here are 2 of their MU installations: <a href=\"http://blogs.thetimes.co.za/\">The Times is South Africa&#8217;s first interactive newspaper</a>, it&#8217;s part of The Sunday Times which is the countries largest newspaper. <a href=\"http://blogs.fm.co.za/\">Financial Mail is a largely financial newspaper also owned by Avusa</a>. It&#8217;s expected that in the near future more rollouts for other publications, newspapers, and magazines will happen as WordPress is ingrained into our online strategy.&#8221;</p>\";s:7:\"pubdate\";s:31:\"Mon, 14 Jan 2008 07:20:21 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:728:\"<p><a href=\"http://blogs.thetimes.co.za/desousa\">Paul De Sousa</a> writes in: &#8220;One of South Africa&#8217;s largest media groups, Avusa, which owns most of the countries BIGGEST newspapers is now using WordPress. Here are 2 of their MU installations: <a href=\"http://blogs.thetimes.co.za/\">The Times is South Africa&#8217;s first interactive newspaper</a>, it&#8217;s part of The Sunday Times which is the countries largest newspaper. <a href=\"http://blogs.fm.co.za/\">Financial Mail is a largely financial newspaper also owned by Avusa</a>. It&#8217;s expected that in the near future more rollouts for other publications, newspapers, and magazines will happen as WordPress is ingrained into our online strategy.&#8221;</p>\";}i:8;a:7:{s:5:\"title\";s:72:\"Peter Westwood: WordPress weekly digest 7th January to 13th January 2008\";s:4:\"guid\";s:95:\"http://westi.wordpress.com/2008/01/13/wordpress-weekly-digest-7th-january-to-13th-january-2008/\";s:4:\"link\";s:95:\"http://westi.wordpress.com/2008/01/13/wordpress-weekly-digest-7th-january-to-13th-january-2008/\";s:11:\"description\";s:4247:\"<div class=\"snap_preview\"><br /><p>It has been a busy week again for WordPress 2.5, the changes this week were:</p>
<ul>
<li> Update of the jQuery form pluginto the latest version (<a href=\"http://trac.wordpress.org/ticket/5048\">#5048</a>).</li>
<li>Addition of mass select functionality to the user editing page (<a href=\"http://trac.wordpress.org/ticket/5592\">#5592</a>).</li>
<li>Pass extra information to the filters in <code>get_lastpostdate()</code> and <code>get_lastpostmodified()</code> (<a href=\"http://trac.wordpress.org/ticket/5292\">#5292</a>).</li>
<li>Introduction of a new interface for widget management (<a href=\"http://trac.wordpress.org/ticket/5583\">#5583</a>).</li>
<li>A switch to jQuery color for fades instead of FAT (<a href=\"http://trac.wordpress.org/ticket/5369\">#5369</a>).</li>
<li>Introduction of a newimage uploader (<a href=\"http://trac.wordpress.org/ticket/5609\">#5609</a>).</li>
<li>Addition of the ability to re-activate all the plugins deactivated by the deactivate all button (<a href=\"http://trac.wordpress.org/ticket/4176\">#4176</a>).</li>
<li>Changes to ensure that the current user information is setup before the init hook fires (<a href=\"http://trac.wordpress.org/ticket/4181\">#4181</a>).</li>
<li>Introduction of &#8220;Just-In-Time&#8221; loading of the tinymce translations (<a href=\"http://trac.wordpress.org/ticket/5605\">#5605</a>).</li>
<li>New interface for category addition and setting in the Write-&gt;Post page (<a href=\"http://trac.wordpress.org/ticket/5618\">#5618</a>).</li>
<li>Documentation for <code>locale.php</code> and <code>pluggable.php</code> (<a href=\"http://trac.wordpress.org/ticket/5621\">#5621</a>, <a href=\"http://trac.wordpress.org/ticket/5509\">#5509</a>).</li>
<li>Fixes for some PHP E_NOTICE messages when <a href=\"http://westi.wordpress.com/2007/09/30/wordpress-weekly-digest-24th-september-to-30th-september-2007/\">WP_DEBUG</a> is enabled (<a href=\"http://trac.wordpress.org/ticket/5607\">#5607</a>).</li>
<li>Changes to ensure that post GUIDs are retained when importing from RSS (<a href=\"http://trac.wordpress.org/ticket/5589\">#5589</a>).</li>
<li>Introduction of new xmlrpc functions to get a list of valid post and page statuses (<a href=\"http://trac.wordpress.org/ticket/5569\">#5569</a>).</li>
<li>Addition of the abilioty to limit the depth of the tree displayed by wp_list_categories() (<a href=\"http://trac.wordpress.org/ticket/2461\">#2461</a>).</li>
<li>Reversion of the change to sent the &#8220;Sender&#8221; in <code>wp_mail()</code> (<a href=\"http://trac.wordpress.org/ticket/5273\">#5273</a>).</li>
<li>Optimisation of the SQL query used to determine what urls are awaiting pinging (<a href=\"http://trac.wordpress.org/ticket/5649\">#5649</a>).</li>
</ul>
<p>For even more information on some of the other little changes that went in this week you can read the whole <a href=\"http://trac.wordpress.org/timeline?from=01%2F13%2F08&amp;daysback=6&amp;changeset=on\">weekly trac timeline</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/25/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/25/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/25/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=25&subd=westi&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Sun, 13 Jan 2008 22:25:55 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Peter Westwood\";}s:7:\"summary\";s:4247:\"<div class=\"snap_preview\"><br /><p>It has been a busy week again for WordPress 2.5, the changes this week were:</p>
<ul>
<li> Update of the jQuery form pluginto the latest version (<a href=\"http://trac.wordpress.org/ticket/5048\">#5048</a>).</li>
<li>Addition of mass select functionality to the user editing page (<a href=\"http://trac.wordpress.org/ticket/5592\">#5592</a>).</li>
<li>Pass extra information to the filters in <code>get_lastpostdate()</code> and <code>get_lastpostmodified()</code> (<a href=\"http://trac.wordpress.org/ticket/5292\">#5292</a>).</li>
<li>Introduction of a new interface for widget management (<a href=\"http://trac.wordpress.org/ticket/5583\">#5583</a>).</li>
<li>A switch to jQuery color for fades instead of FAT (<a href=\"http://trac.wordpress.org/ticket/5369\">#5369</a>).</li>
<li>Introduction of a newimage uploader (<a href=\"http://trac.wordpress.org/ticket/5609\">#5609</a>).</li>
<li>Addition of the ability to re-activate all the plugins deactivated by the deactivate all button (<a href=\"http://trac.wordpress.org/ticket/4176\">#4176</a>).</li>
<li>Changes to ensure that the current user information is setup before the init hook fires (<a href=\"http://trac.wordpress.org/ticket/4181\">#4181</a>).</li>
<li>Introduction of &#8220;Just-In-Time&#8221; loading of the tinymce translations (<a href=\"http://trac.wordpress.org/ticket/5605\">#5605</a>).</li>
<li>New interface for category addition and setting in the Write-&gt;Post page (<a href=\"http://trac.wordpress.org/ticket/5618\">#5618</a>).</li>
<li>Documentation for <code>locale.php</code> and <code>pluggable.php</code> (<a href=\"http://trac.wordpress.org/ticket/5621\">#5621</a>, <a href=\"http://trac.wordpress.org/ticket/5509\">#5509</a>).</li>
<li>Fixes for some PHP E_NOTICE messages when <a href=\"http://westi.wordpress.com/2007/09/30/wordpress-weekly-digest-24th-september-to-30th-september-2007/\">WP_DEBUG</a> is enabled (<a href=\"http://trac.wordpress.org/ticket/5607\">#5607</a>).</li>
<li>Changes to ensure that post GUIDs are retained when importing from RSS (<a href=\"http://trac.wordpress.org/ticket/5589\">#5589</a>).</li>
<li>Introduction of new xmlrpc functions to get a list of valid post and page statuses (<a href=\"http://trac.wordpress.org/ticket/5569\">#5569</a>).</li>
<li>Addition of the abilioty to limit the depth of the tree displayed by wp_list_categories() (<a href=\"http://trac.wordpress.org/ticket/2461\">#2461</a>).</li>
<li>Reversion of the change to sent the &#8220;Sender&#8221; in <code>wp_mail()</code> (<a href=\"http://trac.wordpress.org/ticket/5273\">#5273</a>).</li>
<li>Optimisation of the SQL query used to determine what urls are awaiting pinging (<a href=\"http://trac.wordpress.org/ticket/5649\">#5649</a>).</li>
</ul>
<p>For even more information on some of the other little changes that went in this week you can read the whole <a href=\"http://trac.wordpress.org/timeline?from=01%2F13%2F08&amp;daysback=6&amp;changeset=on\">weekly trac timeline</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/25/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/25/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/25/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/25/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/25/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=25&subd=westi&ref=&feed=1\" /></div>\";}i:9;a:7:{s:5:\"title\";s:62:\"Weblog Tools Collection: What Makes a WordPress Theme Premium?\";s:4:\"guid\";s:90:\"http://weblogtoolscollection.com/archives/2008/01/12/what-makes-a-wordpress-theme-premium/\";s:4:\"link\";s:90:\"http://weblogtoolscollection.com/archives/2008/01/12/what-makes-a-wordpress-theme-premium/\";s:11:\"description\";s:1069:\"<p>About a week ago Smashing Magazine released an article covering <a href=\"http://www.smashingmagazine.com/2008/01/08/100-excellent-free-high-quality-wordpress-themes/\">100 free WordPress themes</a>.  And just yesterday they released an article covering <a href=\"http://www.smashingmagazine.com/2008/01/11/premium-wordpress-themes-are-they-here-to-stay/\">premium WordPress themes</a>.</p>
<p>My questions to the reader is:  what makes a WordPress theme premium?</p>
<h3>Is it the Features?</h3>
<p>What features does a theme have to have to be considered premium?  What are you looking for that will immediately tell a premium theme apart from a non-premium theme?</p>
<h3>Is it the Design?</h3>
<p>Are premium themes designed any differently than their non-premium counterparts?  What design elements does a premium theme have that others don&#8217;t?</p>
<h3>Is it the Support?</h3>
<p>Do premium themes offer more in terms of author support and upgrades?</p>
<h3>Or Something Else&#8230;</h3>
<p>Please weigh in on what you feel makes a WordPress theme premium.</p>\";s:7:\"pubdate\";s:31:\"Sat, 12 Jan 2008 23:45:05 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Ronald Huereca\";}s:7:\"summary\";s:1069:\"<p>About a week ago Smashing Magazine released an article covering <a href=\"http://www.smashingmagazine.com/2008/01/08/100-excellent-free-high-quality-wordpress-themes/\">100 free WordPress themes</a>.  And just yesterday they released an article covering <a href=\"http://www.smashingmagazine.com/2008/01/11/premium-wordpress-themes-are-they-here-to-stay/\">premium WordPress themes</a>.</p>
<p>My questions to the reader is:  what makes a WordPress theme premium?</p>
<h3>Is it the Features?</h3>
<p>What features does a theme have to have to be considered premium?  What are you looking for that will immediately tell a premium theme apart from a non-premium theme?</p>
<h3>Is it the Design?</h3>
<p>Are premium themes designed any differently than their non-premium counterparts?  What design elements does a premium theme have that others don&#8217;t?</p>
<h3>Is it the Support?</h3>
<p>Do premium themes offer more in terms of author support and upgrades?</p>
<h3>Or Something Else&#8230;</h3>
<p>Please weigh in on what you feel makes a WordPress theme premium.</p>\";}i:10;a:7:{s:5:\"title\";s:54:\"Weblog Tools Collection: Uninstalling Conundrum Part 2\";s:4:\"guid\";s:83:\"http://weblogtoolscollection.com/archives/2008/01/12/uninstalling-conundrum-part-2/\";s:4:\"link\";s:83:\"http://weblogtoolscollection.com/archives/2008/01/12/uninstalling-conundrum-part-2/\";s:11:\"description\";s:7572:\"<p>First off, I want to thank each and every one of you who put your thinking caps on and came up with some awesome ideas and solutions for this perplexing problem. I think its time to consolidate the ideas that we came up with, and review what the underlying problems are.</p>
<p>Nick was first out of the gate</p>
<blockquote><p>For both of my plugins, I provided uninstall capability. Whenever the user deactivates the plugin, it is effectively uninstalled, removing all data related to the plugin. The user could then do whatever they wanted with the file containing the plugin.</p>
<p>It was easy to do it this way because WordPress provides a hook for action upon deactivation of a plugin.</p></blockquote>
<p>The problem that I and many others have is that, deactivating a plugin should not have the same affect as uninstalling it. This is wrong. Who wants to reconfigure their plugin after deactivating it, when all we&#8217;re trying to do is upgrade WordPress?</p>
<p>Michael Martin then chipped in and offered up his opinion:</p>
<blockquote><p>You would then have to have an “Uninstall” function, completely separate from the normal “Deactivate” function.</p>
<p>When upgrading WordPress, or trouble-shooting a problem, you constantly active/deactivate plugins. When you reactivate them, you expect all of your settings to have been retained. That’s why “Uninstall” would need to be a separate function.</p>
<p>And then what happens when certain plugin authors don’t bother with an uninstall? They aren’t under any forced rules to offer it (Unless the WP.org directory adds them, like you said). Does that make the plugin worse really? And what if the plugin doesn’t add database entries anyway? It wouldn’t need an Uninstall option, but regular users would get confused at some plugins being able to be uninstalled, whilst others are only deactivated.</p>
<p>I think that adding the option would get a little more confusing than things should be. WordPress have never hidden this (”Deactivate” was a carefully chosen word I imagine). I suppose it’s just a bad assumption that has developed over time (I have it too I imagine. I’ve never gone through my database to properly remove a plugin!).</p></blockquote>
<p>Michael raised quite a few interesting points. First off, I completely support the Uninstall function of a plugin becoming seperate of the Deactivate function. His next point is one that seriously needs some undertaking. He is right. There are no rules or concrete guidelines for how a plugin should be uninstalled. Which means, there are no guidelines for which to enforce upon these plugins. This a problem in and of itself, at least with all of the plugins associated with the official WordPress.org Plugin Database.</p>
<p>As for Michaels next point, this is one of the problems that I haven&#8217;t been able to come up with an answer for. He is right though. While some plugins would have an uninstall button, others would not, causing the end user to be confused. So help me out, how do we solve this particular issue?</p>
<p>Toxic happened to mention a plugin called <strong>Clean Options.</strong></p>
<blockquote><p><a href=\"http://www.mittineague.com/dev/co.php\">Clean Options</a> can be used to clean up some of the detritus left over from deactivated plugins.</p></blockquote>
<p>Kirk M reminded us that it&#8217;s just not the plugins that add or modify database information that are the problems.</p>
<blockquote><p>There are plugins that create DB tables that do have the uninstall feature built into the plugin’s options page and of course many that don’t. Usually these uninstalls can be found at the bottom of the a plugins options page as a “Reset and Remove” (or something similar) link. But it’s not just the plugins that create new database tables that are the problem when removing, it’s also the plugins that add files and entries to the WP core files and/or add entries into your .htaccess file that are not removed when a plugin is deleted.</p></blockquote>
<p>And that is indeed true. Which goes back to the topic of how there are currently no strict guidelines that discuss how a plugin should be removed, if it happens to modify core data or modify database information.</p>
<p><strong>Andrew Rickmann</strong> actually created a tool that adds an uninstallation option to the plugins page. However, the option will only show up if the plugin is deactivated, and if the plugin author has created an uninstall file. Andrew&#8217;s tool has been very well received. But the problem lyes again with every plugin author not including this installation file which then, makes this tool somewhat obsolete.</p>
<p>And last but not least, Keith has created a <a href=\"http://www.doubleblackdesign.com/2007/11/20/wordpress-plugin-framework-v004-released/\" title=\"http://www.doubleblackdesign.com/2007/11/20/wordpress-plugin-framework-v004-released/\" target=\"_blank\">WordPress Plugin Framework</a> (WPF) which allows plugin developers to deactivate and uninstall their plugins.</p>
<h2>Where Do We Go From Here?</h2>
<p>The only way of fixing the uninstalling problem, is a round of solutions to what I believe are multiple problems. As for uninstalling a plugin, as an end user, this is the way I&#8217;d like to see it done.</p>
<blockquote><p>I don’t want options or anything to change when I deactivate a plugin. What I want to see is an uninstall button if the plugin is deactivated. If the plugin is activated, I want the Uninstall button to be greyed out. We also have to make sure there is a confirmation message when you click on the uninstall button to protect against MISS CLICKS.</p></blockquote>
<p>As for tighter restrictions on the official WordPress plugin database, I feel they are necessary. I talked with Photomatt himself today, and suggested that WordPress come up with a quality assurance team or what can be called a plugin validation team. This is a similar approach that folks from PHPBB3 have taken with their mod database. This is how I explained it:</p>
<blockquote><p>PHPBB 3.0 which is a complete rewrite of their forum software, they have a mod validation team. Mods are submitted to the database but the validation team has to go through the code and ensure that the mod was developed, following the coding guidelines they have set forth. This ensures maximum compatibility and it also keeps crappy coded mods from entering the official mod database.</p></blockquote>
<p>So what I&#8217;m proposing is that, the WordPress team should get together along with the community and develop a series of coding guidelines. These are the guidelines that third party plugins would have to abide by, in order to be housed within the official WordPress plugin database. This is the only way WordPress would be able to somewhat control the quality of plugins that are coded and released to the public. Granted, you&#8217;re not going to solve the problem completely as people will still be able to code plugins for WordPress and release them via their own website, but then, end users of WordPress should think twice about those particular plugins and realize that the only safe route to go should be through the official source of plugins that being the WordPress.org plugin database.</p>
<p>Matt thought the PHPBB3 mod validation process was interesting and has stated that perhaps in the future, parts of their process could some day be implemented into WordPress.org. Until then, we will need to use the solutions that have been provided by the community.</p>\";s:7:\"pubdate\";s:31:\"Sat, 12 Jan 2008 17:15:06 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jeffro2pt0\";}s:7:\"summary\";s:7572:\"<p>First off, I want to thank each and every one of you who put your thinking caps on and came up with some awesome ideas and solutions for this perplexing problem. I think its time to consolidate the ideas that we came up with, and review what the underlying problems are.</p>
<p>Nick was first out of the gate</p>
<blockquote><p>For both of my plugins, I provided uninstall capability. Whenever the user deactivates the plugin, it is effectively uninstalled, removing all data related to the plugin. The user could then do whatever they wanted with the file containing the plugin.</p>
<p>It was easy to do it this way because WordPress provides a hook for action upon deactivation of a plugin.</p></blockquote>
<p>The problem that I and many others have is that, deactivating a plugin should not have the same affect as uninstalling it. This is wrong. Who wants to reconfigure their plugin after deactivating it, when all we&#8217;re trying to do is upgrade WordPress?</p>
<p>Michael Martin then chipped in and offered up his opinion:</p>
<blockquote><p>You would then have to have an “Uninstall” function, completely separate from the normal “Deactivate” function.</p>
<p>When upgrading WordPress, or trouble-shooting a problem, you constantly active/deactivate plugins. When you reactivate them, you expect all of your settings to have been retained. That’s why “Uninstall” would need to be a separate function.</p>
<p>And then what happens when certain plugin authors don’t bother with an uninstall? They aren’t under any forced rules to offer it (Unless the WP.org directory adds them, like you said). Does that make the plugin worse really? And what if the plugin doesn’t add database entries anyway? It wouldn’t need an Uninstall option, but regular users would get confused at some plugins being able to be uninstalled, whilst others are only deactivated.</p>
<p>I think that adding the option would get a little more confusing than things should be. WordPress have never hidden this (”Deactivate” was a carefully chosen word I imagine). I suppose it’s just a bad assumption that has developed over time (I have it too I imagine. I’ve never gone through my database to properly remove a plugin!).</p></blockquote>
<p>Michael raised quite a few interesting points. First off, I completely support the Uninstall function of a plugin becoming seperate of the Deactivate function. His next point is one that seriously needs some undertaking. He is right. There are no rules or concrete guidelines for how a plugin should be uninstalled. Which means, there are no guidelines for which to enforce upon these plugins. This a problem in and of itself, at least with all of the plugins associated with the official WordPress.org Plugin Database.</p>
<p>As for Michaels next point, this is one of the problems that I haven&#8217;t been able to come up with an answer for. He is right though. While some plugins would have an uninstall button, others would not, causing the end user to be confused. So help me out, how do we solve this particular issue?</p>
<p>Toxic happened to mention a plugin called <strong>Clean Options.</strong></p>
<blockquote><p><a href=\"http://www.mittineague.com/dev/co.php\">Clean Options</a> can be used to clean up some of the detritus left over from deactivated plugins.</p></blockquote>
<p>Kirk M reminded us that it&#8217;s just not the plugins that add or modify database information that are the problems.</p>
<blockquote><p>There are plugins that create DB tables that do have the uninstall feature built into the plugin’s options page and of course many that don’t. Usually these uninstalls can be found at the bottom of the a plugins options page as a “Reset and Remove” (or something similar) link. But it’s not just the plugins that create new database tables that are the problem when removing, it’s also the plugins that add files and entries to the WP core files and/or add entries into your .htaccess file that are not removed when a plugin is deleted.</p></blockquote>
<p>And that is indeed true. Which goes back to the topic of how there are currently no strict guidelines that discuss how a plugin should be removed, if it happens to modify core data or modify database information.</p>
<p><strong>Andrew Rickmann</strong> actually created a tool that adds an uninstallation option to the plugins page. However, the option will only show up if the plugin is deactivated, and if the plugin author has created an uninstall file. Andrew&#8217;s tool has been very well received. But the problem lyes again with every plugin author not including this installation file which then, makes this tool somewhat obsolete.</p>
<p>And last but not least, Keith has created a <a href=\"http://www.doubleblackdesign.com/2007/11/20/wordpress-plugin-framework-v004-released/\" title=\"http://www.doubleblackdesign.com/2007/11/20/wordpress-plugin-framework-v004-released/\" target=\"_blank\">WordPress Plugin Framework</a> (WPF) which allows plugin developers to deactivate and uninstall their plugins.</p>
<h2>Where Do We Go From Here?</h2>
<p>The only way of fixing the uninstalling problem, is a round of solutions to what I believe are multiple problems. As for uninstalling a plugin, as an end user, this is the way I&#8217;d like to see it done.</p>
<blockquote><p>I don’t want options or anything to change when I deactivate a plugin. What I want to see is an uninstall button if the plugin is deactivated. If the plugin is activated, I want the Uninstall button to be greyed out. We also have to make sure there is a confirmation message when you click on the uninstall button to protect against MISS CLICKS.</p></blockquote>
<p>As for tighter restrictions on the official WordPress plugin database, I feel they are necessary. I talked with Photomatt himself today, and suggested that WordPress come up with a quality assurance team or what can be called a plugin validation team. This is a similar approach that folks from PHPBB3 have taken with their mod database. This is how I explained it:</p>
<blockquote><p>PHPBB 3.0 which is a complete rewrite of their forum software, they have a mod validation team. Mods are submitted to the database but the validation team has to go through the code and ensure that the mod was developed, following the coding guidelines they have set forth. This ensures maximum compatibility and it also keeps crappy coded mods from entering the official mod database.</p></blockquote>
<p>So what I&#8217;m proposing is that, the WordPress team should get together along with the community and develop a series of coding guidelines. These are the guidelines that third party plugins would have to abide by, in order to be housed within the official WordPress plugin database. This is the only way WordPress would be able to somewhat control the quality of plugins that are coded and released to the public. Granted, you&#8217;re not going to solve the problem completely as people will still be able to code plugins for WordPress and release them via their own website, but then, end users of WordPress should think twice about those particular plugins and realize that the only safe route to go should be through the official source of plugins that being the WordPress.org plugin database.</p>
<p>Matt thought the PHPBB3 mod validation process was interesting and has stated that perhaps in the future, parts of their process could some day be implemented into WordPress.org. Until then, we will need to use the solutions that have been provided by the community.</p>\";}i:11;a:7:{s:5:\"title\";s:17:\"Matt: Twenty-four\";s:4:\"guid\";s:28:\"http://photomatt.net/?p=3158\";s:4:\"link\";s:44:\"http://photomatt.net/2008/01/11/twenty-four/\";s:11:\"description\";s:899:\"<p>Every year my birthday sneaks up on me, and this was no exception. After the lull of the holidays and the whirlwind first few days of the year, I am now officially 24. This is the sixth year I&#8217;ve celebrated with you guys on this blog, <a href=\"http://photomatt.net/2003/01/11/bday/\">19</a>, <a href=\"http://photomatt.net/2004/01/11/so-im-20/\">20</a>, <a href=\"http://photomatt.net/2005/01/11/hot-barely-legal-matt/\">21</a>, <a href=\"http://photomatt.net/2006/01/11/matt-22/\">22</a>, and <a href=\"http://photomatt.net/2007/01/11/twenty-three/\">23</a>. This year should be interesting because many of the things I started 2–5 years ago are just now starting to come to fruition. I&#8217;m also hoping there will be some big changes on photomatt.net, including possibly a change in domain name. I&#8217;ll post more on that as it develops though. I hope everyone has a wonderful weekend!</p>\";s:7:\"pubdate\";s:31:\"Sat, 12 Jan 2008 01:26:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:899:\"<p>Every year my birthday sneaks up on me, and this was no exception. After the lull of the holidays and the whirlwind first few days of the year, I am now officially 24. This is the sixth year I&#8217;ve celebrated with you guys on this blog, <a href=\"http://photomatt.net/2003/01/11/bday/\">19</a>, <a href=\"http://photomatt.net/2004/01/11/so-im-20/\">20</a>, <a href=\"http://photomatt.net/2005/01/11/hot-barely-legal-matt/\">21</a>, <a href=\"http://photomatt.net/2006/01/11/matt-22/\">22</a>, and <a href=\"http://photomatt.net/2007/01/11/twenty-three/\">23</a>. This year should be interesting because many of the things I started 2–5 years ago are just now starting to come to fruition. I&#8217;m also hoping there will be some big changes on photomatt.net, including possibly a change in domain name. I&#8217;ll post more on that as it develops though. I hope everyone has a wonderful weekend!</p>\";}i:12;a:7:{s:5:\"title\";s:39:\"Andy Skelton: Apology: Not Useless Code\";s:4:\"guid\";s:62:\"http://andy.wordpress.com/2008/01/11/apology-not-useless-code/\";s:4:\"link\";s:62:\"http://andy.wordpress.com/2008/01/11/apology-not-useless-code/\";s:11:\"description\";s:2311:\"<div class=\"snap_preview\"><br /><blockquote><p>at the top of the main loop, have_posts() and is_404() are mutually exclusive.</p>
<p><cite><a href=\"http://andy.wordpress.com/2006/08/13/useless-code-in-wordpress-themes/\">Useless Code in WordPress Themes</a></cite></p></blockquote>
<p>That is true sometimes, but not always. More specifically, it can be false when a non-permalink URL seeks a non-existent post. For example, <code>/?p=-1</code>.</p>
<blockquote><p>Issue a 404 if a permalink request doesn&#8217;t match any posts.  Don&#8217;t issue a 404 if one was already issued, if the request was a search, or if the request was a regular query string request rather than a permalink request.</p>
<p><cite><a href=\"http://trac.wordpress.org/browser/tags/2.3.2/wp-includes/classes.php#L278\">classes.php</a></cite></p></blockquote>
<p>Now it makes sense that the single.php template file would check <code>have_posts()</code>. Let the healing begin.</p>
<p>(Are there any documented examples of this bug occurring outside of single.php?)</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/andy.wordpress.com/168/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/andy.wordpress.com/168/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/andy.wordpress.com/168/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=andy.wordpress.com&blog=155&post=168&subd=andy&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Fri, 11 Jan 2008 23:38:12 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Andy\";}s:7:\"summary\";s:2311:\"<div class=\"snap_preview\"><br /><blockquote><p>at the top of the main loop, have_posts() and is_404() are mutually exclusive.</p>
<p><cite><a href=\"http://andy.wordpress.com/2006/08/13/useless-code-in-wordpress-themes/\">Useless Code in WordPress Themes</a></cite></p></blockquote>
<p>That is true sometimes, but not always. More specifically, it can be false when a non-permalink URL seeks a non-existent post. For example, <code>/?p=-1</code>.</p>
<blockquote><p>Issue a 404 if a permalink request doesn&#8217;t match any posts.  Don&#8217;t issue a 404 if one was already issued, if the request was a search, or if the request was a regular query string request rather than a permalink request.</p>
<p><cite><a href=\"http://trac.wordpress.org/browser/tags/2.3.2/wp-includes/classes.php#L278\">classes.php</a></cite></p></blockquote>
<p>Now it makes sense that the single.php template file would check <code>have_posts()</code>. Let the healing begin.</p>
<p>(Are there any documented examples of this bug occurring outside of single.php?)</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/andy.wordpress.com/168/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/andy.wordpress.com/168/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/andy.wordpress.com/168/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/andy.wordpress.com/168/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/andy.wordpress.com/168/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=andy.wordpress.com&blog=155&post=168&subd=andy&ref=&feed=1\" /></div>\";}i:13;a:7:{s:5:\"title\";s:57:\"Weblog Tools Collection: NewsGator Makes Client Apps Free\";s:4:\"guid\";s:86:\"http://weblogtoolscollection.com/archives/2008/01/11/newsgator-makes-client-apps-free/\";s:4:\"link\";s:86:\"http://weblogtoolscollection.com/archives/2008/01/11/newsgator-makes-client-apps-free/\";s:11:\"description\";s:499:\"<p><a href=\"http://enterpriserss.typepad.com/enterprise_rss/2008/01/newsgator-makes.html\">NewsGator Makes Client Apps Free</a>: NetNewsWire 3.1, FeedDemon 2.6, and NewsGator Go! for Windows Mobile 2.0. and NewsGator Inbox 3.0 are now free to download and use. FeedDemon is a desktop news aggregator that I helped beta test and I have used off and on and Bradbury is a tremendous developer. If you were looking for a powerful desktop aggregator that is easy to use, FeedDemon might be the ticket.</p>\";s:7:\"pubdate\";s:31:\"Fri, 11 Jan 2008 19:30:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Mark Ghosh\";}s:7:\"summary\";s:499:\"<p><a href=\"http://enterpriserss.typepad.com/enterprise_rss/2008/01/newsgator-makes.html\">NewsGator Makes Client Apps Free</a>: NetNewsWire 3.1, FeedDemon 2.6, and NewsGator Go! for Windows Mobile 2.0. and NewsGator Inbox 3.0 are now free to download and use. FeedDemon is a desktop news aggregator that I helped beta test and I have used off and on and Bradbury is a tremendous developer. If you were looking for a powerful desktop aggregator that is easy to use, FeedDemon might be the ticket.</p>\";}i:14;a:7:{s:5:\"title\";s:46:\"Donncha: Ping. The ping heard across the world\";s:4:\"guid\";s:66:\"http://ocaoimh.ie/2008/01/11/ping-the-ping-heard-across-the-world/\";s:4:\"link\";s:66:\"http://ocaoimh.ie/2008/01/11/ping-the-ping-heard-across-the-world/\";s:11:\"description\";s:2086:\"<p>If you&#8217;re wondering why trackbacks and pings aren&#8217;t working on your blog then you might want to do what I did earlier today: allow your blog to talk to other servers.</p>
<p>WordPress needs either <code>allow_url_fopen</code> to be set <code>On</code> or to have the Curl extension loaded. If you&#8217;re having problems receiving pings from other blogs then both of these are probably turned off or missing. Wouldn&#8217;t it be nice if Options->Discussion warned that pings wouldn&#8217;t work?</p>
<p>Look in your php.ini, or the output of phpinfo() to check for both. If you want to enable fopen, then the entry in php.ini should look like this: </p>
<blockquote><p>;;;;;;;;;;;;;;;;;;<br />
; Fopen wrappers ;<br />
;;;;;;;;;;;;;;;;;;</p>
<p>; Whether to allow the treatment of URLs (like http:// or ftp://) as files.<br />
allow_url_fopen = On</p></blockquote>
<p>I <a href=\"http://ocaoimh.ie/2007/11/12/100000-page-views-in-5-minutes/\">switched</a> to <a href=\"http://litespeedtech.com/\">Litespeed web server</a> a while back  and by default <code>allow_url_fopen</code> is set to Off and the curl library isn&#8217;t included. Check /opt/lsws/php/php.ini and make sure remote fopens are allowed!</p>
<p>Thanks <a href=\"http://barry.wordpress.com/\">Barry</a> for helping me fix that.</p>
<p>PS. if you linked to this blog recently, feel free to save your post again. WordPress will ping my site again and this time the ping will get through.</p>
<p><img src=\"http://ocaoimh.ie/?voyeur=1\" /></p><p><strong>Related Posts</strong><ul><li><a href=\"http://ocaoimh.ie/2002/08/19/heard-on-ircnia/\" rel=\"bookmark\" title=\"Permanent Link: Heard on IRC:<Niall> What w …\"> What w …\"> What w …\">Heard on IRC: What w …</a></li><li><a href=\"http://ocaoimh.ie/2006/10/06/ping-google-too/\" rel=\"bookmark\" title=\"Permanent Link: Ping Google Too!\">Ping Google Too!</a></li><li><a href=\"http://ocaoimh.ie/2004/03/02/cherry-blossom-girl-c64-rip-off/\" rel=\"bookmark\" title=\"Permanent Link: Cherry Blossom Girl - C64 rip off?\">Cherry Blossom Girl - C64 rip off?</a></li></ul></p>\";s:7:\"pubdate\";s:31:\"Fri, 11 Jan 2008 19:07:57 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:7:\"Donncha\";}s:7:\"summary\";s:2086:\"<p>If you&#8217;re wondering why trackbacks and pings aren&#8217;t working on your blog then you might want to do what I did earlier today: allow your blog to talk to other servers.</p>
<p>WordPress needs either <code>allow_url_fopen</code> to be set <code>On</code> or to have the Curl extension loaded. If you&#8217;re having problems receiving pings from other blogs then both of these are probably turned off or missing. Wouldn&#8217;t it be nice if Options->Discussion warned that pings wouldn&#8217;t work?</p>
<p>Look in your php.ini, or the output of phpinfo() to check for both. If you want to enable fopen, then the entry in php.ini should look like this: </p>
<blockquote><p>;;;;;;;;;;;;;;;;;;<br />
; Fopen wrappers ;<br />
;;;;;;;;;;;;;;;;;;</p>
<p>; Whether to allow the treatment of URLs (like http:// or ftp://) as files.<br />
allow_url_fopen = On</p></blockquote>
<p>I <a href=\"http://ocaoimh.ie/2007/11/12/100000-page-views-in-5-minutes/\">switched</a> to <a href=\"http://litespeedtech.com/\">Litespeed web server</a> a while back  and by default <code>allow_url_fopen</code> is set to Off and the curl library isn&#8217;t included. Check /opt/lsws/php/php.ini and make sure remote fopens are allowed!</p>
<p>Thanks <a href=\"http://barry.wordpress.com/\">Barry</a> for helping me fix that.</p>
<p>PS. if you linked to this blog recently, feel free to save your post again. WordPress will ping my site again and this time the ping will get through.</p>
<p><img src=\"http://ocaoimh.ie/?voyeur=1\" /></p><p><strong>Related Posts</strong><ul><li><a href=\"http://ocaoimh.ie/2002/08/19/heard-on-ircnia/\" rel=\"bookmark\" title=\"Permanent Link: Heard on IRC:<Niall> What w …\"> What w …\"> What w …\">Heard on IRC: What w …</a></li><li><a href=\"http://ocaoimh.ie/2006/10/06/ping-google-too/\" rel=\"bookmark\" title=\"Permanent Link: Ping Google Too!\">Ping Google Too!</a></li><li><a href=\"http://ocaoimh.ie/2004/03/02/cherry-blossom-girl-c64-rip-off/\" rel=\"bookmark\" title=\"Permanent Link: Cherry Blossom Girl - C64 rip off?\">Cherry Blossom Girl - C64 rip off?</a></li></ul></p>\";}i:15;a:7:{s:5:\"title\";s:28:\"Matt: Music Industry Lessons\";s:4:\"guid\";s:55:\"http://photomatt.net/2008/01/10/music-industry-lessons/\";s:4:\"link\";s:55:\"http://photomatt.net/2008/01/10/music-industry-lessons/\";s:11:\"description\";s:182:\"<p><a href=\"http://sethgodin.typepad.com/seths_blog/2008/01/music-lessons.html\">Music lessons</a>. &#8220;Things you can learn from the music business (as it falls apart).&#8221;</p>\";s:7:\"pubdate\";s:31:\"Fri, 11 Jan 2008 00:00:25 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:182:\"<p><a href=\"http://sethgodin.typepad.com/seths_blog/2008/01/music-lessons.html\">Music lessons</a>. &#8220;Things you can learn from the music business (as it falls apart).&#8221;</p>\";}i:16;a:7:{s:5:\"title\";s:18:\"Matt: Top Emailers\";s:4:\"guid\";s:45:\"http://photomatt.net/2008/01/10/top-emailers/\";s:4:\"link\";s:45:\"http://photomatt.net/2008/01/10/top-emailers/\";s:11:\"description\";s:995:\"<p>These are the people I received the most email from in 2007 (started logging in April):</p>
<ol>
<li><a href=\"http://toni.schneidersf.com/\">Toni Schneider</a> &#8212; 996</li>
<li><a href=\"http://mayadesai.wordpress.com/\">Maya Desai</a> &#8212;  802</li>
<li>Mom &#8212; 357</li>
<li><a href=\"http://raanan.com/\">Raanan Bar-Cohen</a> &#8212; 349</li>
<li><a href=\"http://barry.wordpress.com/\">Barry Abrahamson</a> &#8212; 250</li>
<li><a href=\"http://boren.nu/\">Ryan Boren</a> &#8212; 195</li>
<li><a href=\"http://ocaoimh.ie/\">Donncha O Caoimh</a> &#8212; 145</li>
<li><a href=\"http://iammattthomas.com/\">Matt Thomas</a> &#8212; 118</li>
<li><a href=\"http://sphere.wordpress.com/\">Tony Conrad</a> &#8212; 105</li>
<li><a href=\"http://vcmike.wordpress.com/\">Mike Hirshland</a> &#8212; 90</li>
</ol>
<p>Thanks to all those who played! Better next year to those who didn&#8217;t win. <img src=\"http://photomatt.net/blog/wp-includes/images/smilies/icon_wink.gif\" alt=\";)\" class=\"wp-smiley\" /></p>\";s:7:\"pubdate\";s:31:\"Thu, 10 Jan 2008 20:59:15 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:995:\"<p>These are the people I received the most email from in 2007 (started logging in April):</p>
<ol>
<li><a href=\"http://toni.schneidersf.com/\">Toni Schneider</a> &#8212; 996</li>
<li><a href=\"http://mayadesai.wordpress.com/\">Maya Desai</a> &#8212;  802</li>
<li>Mom &#8212; 357</li>
<li><a href=\"http://raanan.com/\">Raanan Bar-Cohen</a> &#8212; 349</li>
<li><a href=\"http://barry.wordpress.com/\">Barry Abrahamson</a> &#8212; 250</li>
<li><a href=\"http://boren.nu/\">Ryan Boren</a> &#8212; 195</li>
<li><a href=\"http://ocaoimh.ie/\">Donncha O Caoimh</a> &#8212; 145</li>
<li><a href=\"http://iammattthomas.com/\">Matt Thomas</a> &#8212; 118</li>
<li><a href=\"http://sphere.wordpress.com/\">Tony Conrad</a> &#8212; 105</li>
<li><a href=\"http://vcmike.wordpress.com/\">Mike Hirshland</a> &#8212; 90</li>
</ol>
<p>Thanks to all those who played! Better next year to those who didn&#8217;t win. <img src=\"http://photomatt.net/blog/wp-includes/images/smilies/icon_wink.gif\" alt=\";)\" class=\"wp-smiley\" /></p>\";}i:17;a:7:{s:5:\"title\";s:24:\"Matt: Youtube for Gamers\";s:4:\"guid\";s:51:\"http://photomatt.net/2008/01/10/youtube-for-gamers/\";s:4:\"link\";s:51:\"http://photomatt.net/2008/01/10/youtube-for-gamers/\";s:11:\"description\";s:514:\"<p>If you&#8217;re a computer gamer you should check out <a href=\"http://www.wegame.com/\">WeGame</a>, a game video site from my friend <a href=\"http://jaredkim.wordpress.com/\">Jared Kim</a>. It&#8217;s beta so it&#8217;s just a taste of what&#8217;s to come, but <a href=\"http://www.techcrunch.com/2008/01/09/wegame-launches-as-youtube-for-gamers/\">you can read what Techcrunch thought</a>. WeGame is the only company besides <a href=\"http://sphere.com/\">Sphere</a> that I&#8217;ve elected to be an adviser to.</p>\";s:7:\"pubdate\";s:31:\"Thu, 10 Jan 2008 10:25:38 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:514:\"<p>If you&#8217;re a computer gamer you should check out <a href=\"http://www.wegame.com/\">WeGame</a>, a game video site from my friend <a href=\"http://jaredkim.wordpress.com/\">Jared Kim</a>. It&#8217;s beta so it&#8217;s just a taste of what&#8217;s to come, but <a href=\"http://www.techcrunch.com/2008/01/09/wegame-launches-as-youtube-for-gamers/\">you can read what Techcrunch thought</a>. WeGame is the only company besides <a href=\"http://sphere.com/\">Sphere</a> that I&#8217;ve elected to be an adviser to.</p>\";}i:18;a:7:{s:5:\"title\";s:56:\"Weblog Tools Collection: WordPress Plugin Uninstall Tool\";s:4:\"guid\";s:85:\"http://weblogtoolscollection.com/archives/2008/01/09/wordpress-plugin-uninstall-tool/\";s:4:\"link\";s:85:\"http://weblogtoolscollection.com/archives/2008/01/09/wordpress-plugin-uninstall-tool/\";s:11:\"description\";s:1248:\"<p>In response to Jeff&#8217;s post <a href=\"http://weblogtoolscollection.com/archives/2008/01/07/uninstall-is-there-such-a-thing/\">regarding uninstalling plugins</a>, Andrew Rickmann has created a tool that <a href=\"http://www.wp-fun.co.uk/2008/01/09/fun-with-uninstallation/\">adds an uninstallation option on the plugins page</a>.  The uninstall option will only show up if the plugin has been deactivated and if the plugin author has created an uninstall file.</p>
<p class=\"screenshot\"><a href=\"http://weblogtoolscollection.com/b2-img/2008/01/screenshot.jpeg\" title=\"Hello Dolly Uninstall\"><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/screenshot.thumbnail.jpeg\" alt=\"Hello Dolly Uninstall\" /></a><br />
Click image for larger size &#8212; Uninstall Option for Hello Dolly</p>
<p>Andrew is unsure of the demand for a tool like this, so please <a href=\"http://www.wp-fun.co.uk/2008/01/09/fun-with-uninstallation/\">let him know your thoughts</a> on having an uninstall option on the plugins page.</p>
<blockquote><p> <strong>Update Jan 11</strong>: Andrew has released a second iteration of the uninstall tool.  <a href=\"http://www.wp-fun.co.uk/2008/01/11/fun-with-uninstallation-2/\">Click here</a> to check it out.</p></blockquote>\";s:7:\"pubdate\";s:31:\"Wed, 09 Jan 2008 23:15:09 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Ronald Huereca\";}s:7:\"summary\";s:1248:\"<p>In response to Jeff&#8217;s post <a href=\"http://weblogtoolscollection.com/archives/2008/01/07/uninstall-is-there-such-a-thing/\">regarding uninstalling plugins</a>, Andrew Rickmann has created a tool that <a href=\"http://www.wp-fun.co.uk/2008/01/09/fun-with-uninstallation/\">adds an uninstallation option on the plugins page</a>.  The uninstall option will only show up if the plugin has been deactivated and if the plugin author has created an uninstall file.</p>
<p class=\"screenshot\"><a href=\"http://weblogtoolscollection.com/b2-img/2008/01/screenshot.jpeg\" title=\"Hello Dolly Uninstall\"><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/screenshot.thumbnail.jpeg\" alt=\"Hello Dolly Uninstall\" /></a><br />
Click image for larger size &#8212; Uninstall Option for Hello Dolly</p>
<p>Andrew is unsure of the demand for a tool like this, so please <a href=\"http://www.wp-fun.co.uk/2008/01/09/fun-with-uninstallation/\">let him know your thoughts</a> on having an uninstall option on the plugins page.</p>
<blockquote><p> <strong>Update Jan 11</strong>: Andrew has released a second iteration of the uninstall tool.  <a href=\"http://www.wp-fun.co.uk/2008/01/11/fun-with-uninstallation-2/\">Click here</a> to check it out.</p></blockquote>\";}i:19;a:7:{s:5:\"title\";s:78:\"Peter Westwood: WordPress weekly digest 31st December 2007 to 6th January 2008\";s:4:\"guid\";s:101:\"http://westi.wordpress.com/2008/01/08/wordpress-weekly-digest-31st-december-2007-to-6th-january-2008/\";s:4:\"link\";s:101:\"http://westi.wordpress.com/2008/01/08/wordpress-weekly-digest-31st-december-2007-to-6th-january-2008/\";s:11:\"description\";s:4277:\"<div class=\"snap_preview\"><br /><p>It has been a busy week again for WordPress <strike>2.4</strike> 2.5, the changes this week were:</p>
<ul>
<li> Separation of cookie generation from cookie setting by introduce <code>wp_generate_auth_cookie()</code> (<a href=\"http://trac.wordpress.org/ticket/5367\">#5367</a>).</li>
<li>Changes to allow filtering the view of available themes based on theme tags (<a href=\"http://trac.wordpress.org/ticket/5545\">#5545</a>).</li>
<li>Improvements in the WXR importer to defer post comment counting during importing (<a href=\"http://trac.wordpress.org/ticket/5557\">#5557</a>).</li>
<li>Allow translation of calendar caption (<a href=\"http://trac.wordpress.org/ticket/5562\">#5562</a>).</li>
<li>Introduction of a new xmlrpc method <code>wp.getCommentCount()</code> (<a href=\"http://trac.wordpress.org/ticket/5463\">#5463</a>).</li>
<li>New API for setting a posts &#8220;type&#8221; (<a href=\"http://trac.wordpress.org/ticket/4844\">#4844</a>).</li>
<li>Addition of a separator location argument to <code>wp_title()</code> to allow for changing the ordering of the output - effectively integrating the popular <a href=\"http://elasticdog.com/2004/09/optimal-title/\">Optimal Title</a> plugin (<a href=\"http://trac.wordpress.org/ticket/4407\">#4407</a>).</li>
<li>Removal of the file based persistence of the WordPress object cache (<a href=\"http://trac.wordpress.org/ticket/5570\">#5570</a>).</li>
<li>Introduction of auto-suggest for tag entering (<a href=\"http://trac.wordpress.org/changeset/6542\">[6542]</a>).</li>
<li>phpdoc for <code>cache.php</code>, <code>comment.php</code>, <code>l10n.php</code> and <code>registration.php</code> (<a href=\"http://trac.wordpress.org/ticket/5511\">#5511</a>, <a href=\"http://trac.wordpress.org/ticket/5578\">#5578</a>, <a href=\"http://trac.wordpress.org/ticket/5590\">#5590</a> and <a href=\"http://trac.wordpress.org/ticket/4383\">#4383</a>,).</li>
<li>File level phpdoc for a whole raft of files (<a href=\"http://trac.wordpress.org/ticket/5572\">#5572</a>).</li>
<li>Work on transitioning the admin autosave javascript over to using jQuery (<a href=\"http://trac.wordpress.org/ticket/3824\">#3842</a>).</li>
<li>Improvements to the javascript that enabled switching between Visual and Code editors so as to not mangle table markup (<a href=\"http://trac.wordpress.org/ticket/5577\">#5577</a>).</li>
<li>A new interface for selecting which widgets you want on which sidebar (<a href=\"http://trac.wordpress.org/ticket/5583\">#5583</a>).</li>
<li>Changes to the dual visual/code editors to remember which one you used last (<a href=\"http://trac.wordpress.org/ticket/3978\">#3978</a>).</li>
</ul>
<p>As you will have probably read elsewhere the next major WordPress version will v2.5 as is to be released in March.</p>
<p>For even more information on some of the other little changes that went in this week you can read the whole <a href=\"http://trac.wordpress.org/timeline?from=01%2F06%2F08&amp;daysback=6&amp;changeset=on\">weekly trac timeline</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/24/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/24/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/24/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=24&subd=westi&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Tue, 08 Jan 2008 22:07:43 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Peter Westwood\";}s:7:\"summary\";s:4277:\"<div class=\"snap_preview\"><br /><p>It has been a busy week again for WordPress <strike>2.4</strike> 2.5, the changes this week were:</p>
<ul>
<li> Separation of cookie generation from cookie setting by introduce <code>wp_generate_auth_cookie()</code> (<a href=\"http://trac.wordpress.org/ticket/5367\">#5367</a>).</li>
<li>Changes to allow filtering the view of available themes based on theme tags (<a href=\"http://trac.wordpress.org/ticket/5545\">#5545</a>).</li>
<li>Improvements in the WXR importer to defer post comment counting during importing (<a href=\"http://trac.wordpress.org/ticket/5557\">#5557</a>).</li>
<li>Allow translation of calendar caption (<a href=\"http://trac.wordpress.org/ticket/5562\">#5562</a>).</li>
<li>Introduction of a new xmlrpc method <code>wp.getCommentCount()</code> (<a href=\"http://trac.wordpress.org/ticket/5463\">#5463</a>).</li>
<li>New API for setting a posts &#8220;type&#8221; (<a href=\"http://trac.wordpress.org/ticket/4844\">#4844</a>).</li>
<li>Addition of a separator location argument to <code>wp_title()</code> to allow for changing the ordering of the output - effectively integrating the popular <a href=\"http://elasticdog.com/2004/09/optimal-title/\">Optimal Title</a> plugin (<a href=\"http://trac.wordpress.org/ticket/4407\">#4407</a>).</li>
<li>Removal of the file based persistence of the WordPress object cache (<a href=\"http://trac.wordpress.org/ticket/5570\">#5570</a>).</li>
<li>Introduction of auto-suggest for tag entering (<a href=\"http://trac.wordpress.org/changeset/6542\">[6542]</a>).</li>
<li>phpdoc for <code>cache.php</code>, <code>comment.php</code>, <code>l10n.php</code> and <code>registration.php</code> (<a href=\"http://trac.wordpress.org/ticket/5511\">#5511</a>, <a href=\"http://trac.wordpress.org/ticket/5578\">#5578</a>, <a href=\"http://trac.wordpress.org/ticket/5590\">#5590</a> and <a href=\"http://trac.wordpress.org/ticket/4383\">#4383</a>,).</li>
<li>File level phpdoc for a whole raft of files (<a href=\"http://trac.wordpress.org/ticket/5572\">#5572</a>).</li>
<li>Work on transitioning the admin autosave javascript over to using jQuery (<a href=\"http://trac.wordpress.org/ticket/3824\">#3842</a>).</li>
<li>Improvements to the javascript that enabled switching between Visual and Code editors so as to not mangle table markup (<a href=\"http://trac.wordpress.org/ticket/5577\">#5577</a>).</li>
<li>A new interface for selecting which widgets you want on which sidebar (<a href=\"http://trac.wordpress.org/ticket/5583\">#5583</a>).</li>
<li>Changes to the dual visual/code editors to remember which one you used last (<a href=\"http://trac.wordpress.org/ticket/3978\">#3978</a>).</li>
</ul>
<p>As you will have probably read elsewhere the next major WordPress version will v2.5 as is to be released in March.</p>
<p>For even more information on some of the other little changes that went in this week you can read the whole <a href=\"http://trac.wordpress.org/timeline?from=01%2F06%2F08&amp;daysback=6&amp;changeset=on\">weekly trac timeline</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/24/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/24/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/24/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/24/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/24/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=24&subd=westi&ref=&feed=1\" /></div>\";}i:20;a:7:{s:5:\"title\";s:57:\"Weblog Tools Collection: WordPress Theme Releases for 1/8\";s:4:\"guid\";s:85:\"http://weblogtoolscollection.com/archives/2008/01/08/wordpress-theme-releases-for-18/\";s:4:\"link\";s:85:\"http://weblogtoolscollection.com/archives/2008/01/08/wordpress-theme-releases-for-18/\";s:11:\"description\";s:1470:\"<p><a href=\"http://www.dennis.ca/weblog/antropov-wordpress-theme/\">Antropov</a> is a 3-column, light-colored theme built on the Cutline theme.</p>
<p><a href=\"http://www.blogohblog.com/wordpress-theme-brilliance/\">Brilliance</a> is a 2-column theme with a very simple, clean layout and design.</p>
<p><a href=\"http://graphpaperpress.com/2008/01/05/deadwood-lite/\">Deadwood-lite</a> is a 2-column, minimal theme primed for writers who want to focus their online efforts on readability, pull quotes, and clarity.</p>
<p><a href=\"http://wp-themes.designdisease.com/2007/12/21/dilectio-wordpress-theme/\">Dilectio</a> is a 3-column theme with artistic stylings.</p>
<p><a href=\"http://gordonbrander.com/2008/01/05/hardcover-theme-for-wordpress\">Hardcover</a> is a 2-column theme with crisp design and typography.</p>
<p><a href=\"http://www.tgpo.org/index.php/2008/01/01/landis/\">Landis</a> is a 2-column theme with two customizable options for the site title and tagline.</p>
<p><a href=\"http://www.stevencampbell.org/features/sparkwp-wordpress-theme\">SparkWP</a> is a 2-column, minimalistic, light-on-dark theme.</p>
<p><a href=\"http://www.hfdesign.nl/wordpress-webdesign-theme-download/\">Webdesign</a> is a 2-column theme with light-blue colors. (Download page is Dutch.)</p>
<p><a href=\"http://www.internet-starter-guide.com/blog/wordpress-themes/why-walk-alone-wordpress-theme/\">Why walk alone?</a> is a bright beachscape theme available in 2- and 3-column varieties.</p>\";s:7:\"pubdate\";s:31:\"Tue, 08 Jan 2008 04:45:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:11:\"Jim Stitzel\";}s:7:\"summary\";s:1470:\"<p><a href=\"http://www.dennis.ca/weblog/antropov-wordpress-theme/\">Antropov</a> is a 3-column, light-colored theme built on the Cutline theme.</p>
<p><a href=\"http://www.blogohblog.com/wordpress-theme-brilliance/\">Brilliance</a> is a 2-column theme with a very simple, clean layout and design.</p>
<p><a href=\"http://graphpaperpress.com/2008/01/05/deadwood-lite/\">Deadwood-lite</a> is a 2-column, minimal theme primed for writers who want to focus their online efforts on readability, pull quotes, and clarity.</p>
<p><a href=\"http://wp-themes.designdisease.com/2007/12/21/dilectio-wordpress-theme/\">Dilectio</a> is a 3-column theme with artistic stylings.</p>
<p><a href=\"http://gordonbrander.com/2008/01/05/hardcover-theme-for-wordpress\">Hardcover</a> is a 2-column theme with crisp design and typography.</p>
<p><a href=\"http://www.tgpo.org/index.php/2008/01/01/landis/\">Landis</a> is a 2-column theme with two customizable options for the site title and tagline.</p>
<p><a href=\"http://www.stevencampbell.org/features/sparkwp-wordpress-theme\">SparkWP</a> is a 2-column, minimalistic, light-on-dark theme.</p>
<p><a href=\"http://www.hfdesign.nl/wordpress-webdesign-theme-download/\">Webdesign</a> is a 2-column theme with light-blue colors. (Download page is Dutch.)</p>
<p><a href=\"http://www.internet-starter-guide.com/blog/wordpress-themes/why-walk-alone-wordpress-theme/\">Why walk alone?</a> is a bright beachscape theme available in 2- and 3-column varieties.</p>\";}i:21;a:7:{s:5:\"title\";s:58:\"Weblog Tools Collection: WordPress Plugin Releases for 1/8\";s:4:\"guid\";s:86:\"http://weblogtoolscollection.com/archives/2008/01/08/wordpress-plugin-releases-for-18/\";s:4:\"link\";s:86:\"http://weblogtoolscollection.com/archives/2008/01/08/wordpress-plugin-releases-for-18/\";s:11:\"description\";s:719:\"<p><a href=\"http://www.weinschenker.name/comment-url-control/\">Comment URL Control</a> will allow you to remove unwanted author-URIs entered by a commenter with one single click of your mouse.</p>
<p><a href=\"http://wordpress.org/extend/plugins/wp-crontrol/\">WP-Crontrol</a> lets you take control over what&#8217;s happening in the WP-Cron system.</p>
<p><a href=\"http://climbtothestars.org/archives/2007/12/28/bunnys-language-linker-new-wordpress-plugin/\">Language Linker</a> allows you to link sister pages that are written in multiple languages.</p>
<p><a href=\"http://wordpress.org/extend/plugins/related-posts/\">RelatedPosts</a> provides a variety of options for displaying posts that are related through tags.</p>\";s:7:\"pubdate\";s:31:\"Tue, 08 Jan 2008 04:45:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:11:\"Jim Stitzel\";}s:7:\"summary\";s:719:\"<p><a href=\"http://www.weinschenker.name/comment-url-control/\">Comment URL Control</a> will allow you to remove unwanted author-URIs entered by a commenter with one single click of your mouse.</p>
<p><a href=\"http://wordpress.org/extend/plugins/wp-crontrol/\">WP-Crontrol</a> lets you take control over what&#8217;s happening in the WP-Cron system.</p>
<p><a href=\"http://climbtothestars.org/archives/2007/12/28/bunnys-language-linker-new-wordpress-plugin/\">Language Linker</a> allows you to link sister pages that are written in multiple languages.</p>
<p><a href=\"http://wordpress.org/extend/plugins/related-posts/\">RelatedPosts</a> provides a variety of options for displaying posts that are related through tags.</p>\";}i:22;a:7:{s:5:\"title\";s:35:\"Matt: ThinkGeek’s Crappy Wishlist\";s:4:\"guid\";s:59:\"http://photomatt.net/2008/01/07/thinkgeeks-crappy-wishlist/\";s:4:\"link\";s:59:\"http://photomatt.net/2008/01/07/thinkgeeks-crappy-wishlist/\";s:11:\"description\";s:3498:\"<p>I&#8217;ve always found the Wishlist concept to be cool, especially as Amazon implements it. I love it when the developer of a plugin or software I use links to their Wishlist because then I can buy them something personal, it seems less crude than a Paypal donate link where you&#8217;re putting an explicit price on things.</p>
<p>The other day <a href=\"http://kentbrewster.com/\">Kent Brewster</a> found a JS problem on WordPress.com. I was browsing <a href=\"http://kentbrewster.com/faq/\">his FAQ</a> and saw this: &#8220;My <a href=\"http://www.thinkgeek.com/brain/gimme.cgi?wid=81d55ed02\">ThinkGeek Wish List</a> is always open.&#8221;</p>
<p>If you click that link, you&#8217;ll see in red letters: &#8220;<b>To shop from this wishlist, please add items to your cart using this form only!</b> Otherwise, your gifts will not be removed from this wishlist, and the recipient may get duplicates.&#8221;</p>
<p>Okay &#8212; a little weird, but ThinkGeek&#8217;s home-grown shopping cart has always been a little odd, I&#8217;ll run with it. I add it to my cart from that form, go to the checkout form and sign in (I&#8217;ve spent lots of money with ThinkGeek over the years), and complete the order. (<a href=\"http://www.thinkgeek.com/books/humor/8edf/\">How to Survive a Robot Uprising</a>, for the record.)</p>
<p>So I send an email to their customer support: &#8220;I ordered something off someone&#8217;s wishlist, order e5886bb4. Everything in the order looks like it&#8217;s being shipped to me, not the recipient. Could you confirm it&#8217;s going to this guy&#8217;s wishlist and not me?&#8221; I then linked to the wishlist. Next morning, a response:</p>
<blockquote><p>Matt,<br />
This order is being shipped to [my address redacted]<br />
United States<br />
That was the address entered when the order was placed.<br />
Thanks,</p>
<p>Tracy G<br />
Customer Service</p></blockquote>
<p>Not helpful at all&#8230; my reply: &#8220;Why would I buy something off someone else&#8217;s wishlist and then ship it to me? If it can&#8217;t be shipped to the person who made the wishlist, then please cancel it.&#8221;</p>
<p>No response, and two days later the order ships, to me. This morning, a final response from Tracy:</p>
<blockquote><p>Mr. Mullenweg,<br />
When the order is placed the order you had the option of entering an alternate ship to address.<br />
Since your order has already shipped we can not change or cancel the order.<br />
Thanks,</p>
<p>Tracy G<br />
Customer Service</p></blockquote>
<p>Given the next-day shipping I paid extra for, the book should be arriving any day now. The whole point of a wishlist is that <em>I don&#8217;t know Kent&#8217;s address</em>, nor should I need to. Also the big red sentence on the wishlist page implied to me that Kent would get anything I order from that specific form/page, otherwise why would I need to add it to my cart specifically from that spot?</p>
<p>To Kent, my apologies. If the robot uprising comes before I&#8217;m able to get you this book and we both die in the aftermath I&#8217;ll buy you a drink.</p>
<p>To <a href=\"http://thinkgeek.com/\">ThinkGeek</a>, you&#8217;re cooler and smarter than this. Please fix your wishlist functionality.</p>
<p>To everyone else, set up a wishlist on <a href=\"http://amazon.com/\">Amazon</a>. It works, and if you link to it from your blog and do nice things people may order from it for you, and there&#8217;s nothing nicer than a surprise Amazon box showing up at the door.</p>\";s:7:\"pubdate\";s:31:\"Tue, 08 Jan 2008 02:32:31 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:3498:\"<p>I&#8217;ve always found the Wishlist concept to be cool, especially as Amazon implements it. I love it when the developer of a plugin or software I use links to their Wishlist because then I can buy them something personal, it seems less crude than a Paypal donate link where you&#8217;re putting an explicit price on things.</p>
<p>The other day <a href=\"http://kentbrewster.com/\">Kent Brewster</a> found a JS problem on WordPress.com. I was browsing <a href=\"http://kentbrewster.com/faq/\">his FAQ</a> and saw this: &#8220;My <a href=\"http://www.thinkgeek.com/brain/gimme.cgi?wid=81d55ed02\">ThinkGeek Wish List</a> is always open.&#8221;</p>
<p>If you click that link, you&#8217;ll see in red letters: &#8220;<b>To shop from this wishlist, please add items to your cart using this form only!</b> Otherwise, your gifts will not be removed from this wishlist, and the recipient may get duplicates.&#8221;</p>
<p>Okay &#8212; a little weird, but ThinkGeek&#8217;s home-grown shopping cart has always been a little odd, I&#8217;ll run with it. I add it to my cart from that form, go to the checkout form and sign in (I&#8217;ve spent lots of money with ThinkGeek over the years), and complete the order. (<a href=\"http://www.thinkgeek.com/books/humor/8edf/\">How to Survive a Robot Uprising</a>, for the record.)</p>
<p>So I send an email to their customer support: &#8220;I ordered something off someone&#8217;s wishlist, order e5886bb4. Everything in the order looks like it&#8217;s being shipped to me, not the recipient. Could you confirm it&#8217;s going to this guy&#8217;s wishlist and not me?&#8221; I then linked to the wishlist. Next morning, a response:</p>
<blockquote><p>Matt,<br />
This order is being shipped to [my address redacted]<br />
United States<br />
That was the address entered when the order was placed.<br />
Thanks,</p>
<p>Tracy G<br />
Customer Service</p></blockquote>
<p>Not helpful at all&#8230; my reply: &#8220;Why would I buy something off someone else&#8217;s wishlist and then ship it to me? If it can&#8217;t be shipped to the person who made the wishlist, then please cancel it.&#8221;</p>
<p>No response, and two days later the order ships, to me. This morning, a final response from Tracy:</p>
<blockquote><p>Mr. Mullenweg,<br />
When the order is placed the order you had the option of entering an alternate ship to address.<br />
Since your order has already shipped we can not change or cancel the order.<br />
Thanks,</p>
<p>Tracy G<br />
Customer Service</p></blockquote>
<p>Given the next-day shipping I paid extra for, the book should be arriving any day now. The whole point of a wishlist is that <em>I don&#8217;t know Kent&#8217;s address</em>, nor should I need to. Also the big red sentence on the wishlist page implied to me that Kent would get anything I order from that specific form/page, otherwise why would I need to add it to my cart specifically from that spot?</p>
<p>To Kent, my apologies. If the robot uprising comes before I&#8217;m able to get you this book and we both die in the aftermath I&#8217;ll buy you a drink.</p>
<p>To <a href=\"http://thinkgeek.com/\">ThinkGeek</a>, you&#8217;re cooler and smarter than this. Please fix your wishlist functionality.</p>
<p>To everyone else, set up a wishlist on <a href=\"http://amazon.com/\">Amazon</a>. It works, and if you link to it from your blog and do nice things people may order from it for you, and there&#8217;s nothing nicer than a surprise Amazon box showing up at the door.</p>\";}i:23;a:7:{s:5:\"title\";s:59:\"Weblog Tools Collection: Uninstall - Is There Such A Thing?\";s:4:\"guid\";s:85:\"http://weblogtoolscollection.com/archives/2008/01/07/uninstall-is-there-such-a-thing/\";s:4:\"link\";s:85:\"http://weblogtoolscollection.com/archives/2008/01/07/uninstall-is-there-such-a-thing/\";s:11:\"description\";s:3104:\"<p>When you think of uninstall, do you think of completely removing something? The official definition for the word is as follows, <strong>(uninstall)  To remove completely from a system. </strong>I ask this question because I have discovered a problem that needs to be addressed by WordPress plugin authors.</p>
<p>Over the lifespan of a WordPress installation, there may be a number of plugins that are installed and subsequently uninstalled. Typically, the installation of a WordPress plugin consist of uploading files, folders and then activating the plugin within the admin panel. However, some plugins include a bonus. These are the plugins that create database entries either in the form of tables or data.</p>
<p>I&#8217;ve used WordPress for over 7 months now, and for those 7 months, I believed that when I deleted the folders and files that were attributed to a plugin, that it was in fact, uninstalled. Only now have I come to realize that this is not the case. Sure, the folders and hardcoded files for the plugin might be deleted, but if that plugin created any database entries, those are left behind unless the plugin author added the ability to delete entries made by the plugin. What does this all mean? It means that over time, your database may be filling up with garbage data that is difficult to get rid of unless your familiar with PHPMyAdmin and working with the actual database. Not to mention, playing with the actual database is risky business. All of this gook that accumulates in the database adds to its size and can cause problems somewhere down the line.</p>
<p>So, I got a hold of a few plugin developers and asked them what the problem was. I thought it had to do with the WordPress Core not providing a way for plugin authors to easily code in uninstall instructions. However, it appears as though this responsibility is entirely of the plugin author. When I consulted with <strong>Ronald Huereca,</strong> author of the popular plugin <a href=\"http://www.raproject.com/wordpress/wp-ajax-edit-comments/\" rel=\"bookmark\">WP Ajax Edit Comments</a> and asked him who was responsible for the removal of database code, he replied with:</p>
<blockquote><p>It is the plugin author&#8217;s responsibility to delete any necessary overhead (including options and/or database tables) that a plugin might use.  The plugin author can have the user do this manually or at deactivation.  But at least have some kind of option.</p></blockquote>
<p>The purpose of this post is not to chastise WordPress plugin developers but instead, raise awareness of an issue that I don&#8217;t think too many people know about. I would be grateful if any of the plugin authors out there would comment on this post and answer a few questions I had.</p>
<p>Why have so many plugin authors neglected to add this functionality to their plugin?</p>
<p>What are some solutions that plugin authors could use to easily add this option to their code?</p>
<p>Should there be tighter restrictions on how a plugin gets into the WordPress.org plugin database?</p>
<p>Looking forward to hearing your responses.</p>\";s:7:\"pubdate\";s:31:\"Mon, 07 Jan 2008 13:00:15 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jeffro2pt0\";}s:7:\"summary\";s:3104:\"<p>When you think of uninstall, do you think of completely removing something? The official definition for the word is as follows, <strong>(uninstall)  To remove completely from a system. </strong>I ask this question because I have discovered a problem that needs to be addressed by WordPress plugin authors.</p>
<p>Over the lifespan of a WordPress installation, there may be a number of plugins that are installed and subsequently uninstalled. Typically, the installation of a WordPress plugin consist of uploading files, folders and then activating the plugin within the admin panel. However, some plugins include a bonus. These are the plugins that create database entries either in the form of tables or data.</p>
<p>I&#8217;ve used WordPress for over 7 months now, and for those 7 months, I believed that when I deleted the folders and files that were attributed to a plugin, that it was in fact, uninstalled. Only now have I come to realize that this is not the case. Sure, the folders and hardcoded files for the plugin might be deleted, but if that plugin created any database entries, those are left behind unless the plugin author added the ability to delete entries made by the plugin. What does this all mean? It means that over time, your database may be filling up with garbage data that is difficult to get rid of unless your familiar with PHPMyAdmin and working with the actual database. Not to mention, playing with the actual database is risky business. All of this gook that accumulates in the database adds to its size and can cause problems somewhere down the line.</p>
<p>So, I got a hold of a few plugin developers and asked them what the problem was. I thought it had to do with the WordPress Core not providing a way for plugin authors to easily code in uninstall instructions. However, it appears as though this responsibility is entirely of the plugin author. When I consulted with <strong>Ronald Huereca,</strong> author of the popular plugin <a href=\"http://www.raproject.com/wordpress/wp-ajax-edit-comments/\" rel=\"bookmark\">WP Ajax Edit Comments</a> and asked him who was responsible for the removal of database code, he replied with:</p>
<blockquote><p>It is the plugin author&#8217;s responsibility to delete any necessary overhead (including options and/or database tables) that a plugin might use.  The plugin author can have the user do this manually or at deactivation.  But at least have some kind of option.</p></blockquote>
<p>The purpose of this post is not to chastise WordPress plugin developers but instead, raise awareness of an issue that I don&#8217;t think too many people know about. I would be grateful if any of the plugin authors out there would comment on this post and answer a few questions I had.</p>
<p>Why have so many plugin authors neglected to add this functionality to their plugin?</p>
<p>What are some solutions that plugin authors could use to easily add this option to their code?</p>
<p>Should there be tighter restrictions on how a plugin gets into the WordPress.org plugin database?</p>
<p>Looking forward to hearing your responses.</p>\";}i:24;a:7:{s:5:\"title\";s:29:\"Donncha: Phoar! What a spike!\";s:4:\"guid\";s:48:\"http://ocaoimh.ie/2008/01/07/phoar-what-a-spike/\";s:4:\"link\";s:48:\"http://ocaoimh.ie/2008/01/07/phoar-what-a-spike/\";s:11:\"description\";s:2527:\"<p>I released <a href=\"http://ocaoimh.ie/wp-super-cache/\">WP Super Cache 0.5.3</a> on Friday last. From the <a href=\"http://wordpress.org/extend/plugins/wp-super-cache/statistics/\">stats</a> it looks like people are upgrading which is good news!</p>
<p>This version has a number of fixes and improvements:</p>
<ul>
<li> If your blog is installed in a sub-directory you&#8217;ll want to upgrade. This version fixes the mod_rewrite rules that search for the cached files. If upgrading, make sure you delete the Super Cache rules so they&#8217;ll be upgraded. (Thanks Otto42)</li>
<li> With a click of a link in the backend page you can view your mod_rewrite rules to check that they are ok. This may help the adventurous who want to upgrade those rules manually too.</li>
<li> The plugin now warns if your blog&#8217;s root directory is writeable. Most of the time there&#8217;s absolutely no reason for this so it&#8217;s good to be reminded to fix it.</li>
<li> Check that $mutex is set. This is really only useful if your <a href=\"http://wordpress.org/support/topic/146052?replies=4\">server is borked</a> and the filesystem is mounted read-only but it&#8217;s good to be complete.</li>
</ul>
<p>Wondering about the title? Check out this traffic graph Scott Beale <a href=\"http://laughingsquid.com/best-buy-cease-desist-traffic-stats/\">posted</a> a few weeks ago and you&#8217;ll understand. One of his posts hit the front page of Digg (twice) then Slashdot.org, and was covered by lots of other blogs and media. Wow.</p>
<blockquote><p>On December 12th our blog hit a record high of 222,523 views in one day.</p></blockquote>
<p><a href=\"http://www.flickr.com/photos/laughingsquid/2127683434/\" class=\"tt-flickr\"><img src=\"http://farm3.static.flickr.com/2144/2127683434_8beede718a.jpg\" alt=\"Best Buy Cease &#038; Desist Traffic Stats\" width=\"500\" height=\"231\" border=\"0\" /></a></p>
<p><img src=\"http://ocaoimh.ie/?voyeur=1\" /></p><p><strong>Related Posts</strong><ul><li><a href=\"http://ocaoimh.ie/2003/12/05/bars-in-cobh-spike-island/\" rel=\"bookmark\" title=\"Permanent Link: Bars in Cobh - Spike Island\">Bars in Cobh - Spike Island</a></li><li><a href=\"http://ocaoimh.ie/2002/02/27/ananova-spike-mill/\" rel=\"bookmark\" title=\"Permanent Link: Ananova - Spike Milligan has d &#8230;\">Ananova - Spike Milligan has d &#8230;</a></li><li><a href=\"http://ocaoimh.ie/2003/01/21/dublin-city-and-rive/\" rel=\"bookmark\" title=\"Permanent Link: Dublin City and River Liffey - &#8230;\">Dublin City and River Liffey - &#8230;</a></li></ul></p>\";s:7:\"pubdate\";s:31:\"Mon, 07 Jan 2008 10:50:58 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:7:\"Donncha\";}s:7:\"summary\";s:2527:\"<p>I released <a href=\"http://ocaoimh.ie/wp-super-cache/\">WP Super Cache 0.5.3</a> on Friday last. From the <a href=\"http://wordpress.org/extend/plugins/wp-super-cache/statistics/\">stats</a> it looks like people are upgrading which is good news!</p>
<p>This version has a number of fixes and improvements:</p>
<ul>
<li> If your blog is installed in a sub-directory you&#8217;ll want to upgrade. This version fixes the mod_rewrite rules that search for the cached files. If upgrading, make sure you delete the Super Cache rules so they&#8217;ll be upgraded. (Thanks Otto42)</li>
<li> With a click of a link in the backend page you can view your mod_rewrite rules to check that they are ok. This may help the adventurous who want to upgrade those rules manually too.</li>
<li> The plugin now warns if your blog&#8217;s root directory is writeable. Most of the time there&#8217;s absolutely no reason for this so it&#8217;s good to be reminded to fix it.</li>
<li> Check that $mutex is set. This is really only useful if your <a href=\"http://wordpress.org/support/topic/146052?replies=4\">server is borked</a> and the filesystem is mounted read-only but it&#8217;s good to be complete.</li>
</ul>
<p>Wondering about the title? Check out this traffic graph Scott Beale <a href=\"http://laughingsquid.com/best-buy-cease-desist-traffic-stats/\">posted</a> a few weeks ago and you&#8217;ll understand. One of his posts hit the front page of Digg (twice) then Slashdot.org, and was covered by lots of other blogs and media. Wow.</p>
<blockquote><p>On December 12th our blog hit a record high of 222,523 views in one day.</p></blockquote>
<p><a href=\"http://www.flickr.com/photos/laughingsquid/2127683434/\" class=\"tt-flickr\"><img src=\"http://farm3.static.flickr.com/2144/2127683434_8beede718a.jpg\" alt=\"Best Buy Cease &#038; Desist Traffic Stats\" width=\"500\" height=\"231\" border=\"0\" /></a></p>
<p><img src=\"http://ocaoimh.ie/?voyeur=1\" /></p><p><strong>Related Posts</strong><ul><li><a href=\"http://ocaoimh.ie/2003/12/05/bars-in-cobh-spike-island/\" rel=\"bookmark\" title=\"Permanent Link: Bars in Cobh - Spike Island\">Bars in Cobh - Spike Island</a></li><li><a href=\"http://ocaoimh.ie/2002/02/27/ananova-spike-mill/\" rel=\"bookmark\" title=\"Permanent Link: Ananova - Spike Milligan has d &#8230;\">Ananova - Spike Milligan has d &#8230;</a></li><li><a href=\"http://ocaoimh.ie/2003/01/21/dublin-city-and-rive/\" rel=\"bookmark\" title=\"Permanent Link: Dublin City and River Liffey - &#8230;\">Dublin City and River Liffey - &#8230;</a></li></ul></p>\";}i:25;a:7:{s:5:\"title\";s:18:\"Matt: Wikia Search\";s:4:\"guid\";s:45:\"http://photomatt.net/2008/01/07/wikia-search/\";s:4:\"link\";s:45:\"http://photomatt.net/2008/01/07/wikia-search/\";s:11:\"description\";s:565:\"<p><a href=\"http://alpha.search.wikia.com/\">Wikia Search is pretty darn cool</a>. Not sure what I was expecting, I guess I assumed that search would be much harder than doing a wiki. The &#8220;Visvo&#8221; index seems good enough for daily search use. Their social networking stuff is clean too, <a href=\"http://alpha.search.wikia.com/profile/profile.html?vuid=308402\">here&#8217;s my profile &#8212; please add me as a friend</a>! (I hope those links work post-alpha.) If they can pull off an open source ranking algorithm&#8230; that&#8217;s pretty exciting.</p>\";s:7:\"pubdate\";s:31:\"Mon, 07 Jan 2008 08:52:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:565:\"<p><a href=\"http://alpha.search.wikia.com/\">Wikia Search is pretty darn cool</a>. Not sure what I was expecting, I guess I assumed that search would be much harder than doing a wiki. The &#8220;Visvo&#8221; index seems good enough for daily search use. Their social networking stuff is clean too, <a href=\"http://alpha.search.wikia.com/profile/profile.html?vuid=308402\">here&#8217;s my profile &#8212; please add me as a friend</a>! (I hope those links work post-alpha.) If they can pull off an open source ranking algorithm&#8230; that&#8217;s pretty exciting.</p>\";}i:26;a:7:{s:5:\"title\";s:36:\"Matt: General Motors using WordPress\";s:4:\"guid\";s:63:\"http://photomatt.net/2008/01/05/general-motors-using-wordpress/\";s:4:\"link\";s:63:\"http://photomatt.net/2008/01/05/general-motors-using-wordpress/\";s:11:\"description\";s:367:\"<p><a href=\"http://slashdot.org/article.pl?sid=08/01/04/2045222\">General Motors Embraces Open Source for New Community Site</a>. &#8220;GM has introduced a new website called GMnext. The site utilizes WordPress and launching in spring a Wiki allowing General Motors to get better feedback on topics such as energy, design and technology from the community.&#8221;</p>\";s:7:\"pubdate\";s:31:\"Sun, 06 Jan 2008 06:28:24 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:367:\"<p><a href=\"http://slashdot.org/article.pl?sid=08/01/04/2045222\">General Motors Embraces Open Source for New Community Site</a>. &#8220;GM has introduced a new website called GMnext. The site utilizes WordPress and launching in spring a Wiki allowing General Motors to get better feedback on topics such as energy, design and technology from the community.&#8221;</p>\";}i:27;a:7:{s:5:\"title\";s:23:\"Akismet: Subkismet .NET\";s:4:\"guid\";s:49:\"http://blog.akismet.com/2008/01/05/subkismet-net/\";s:4:\"link\";s:49:\"http://blog.akismet.com/2008/01/05/subkismet-net/\";s:11:\"description\";s:1747:\"<div class=\"snap_preview\"><br /><p><a href=\"http://nayyeri.net/blog/subkismet-1-0-released/\">Subkismet 1.0 Released : Keyvan Nayyeri</a></p>
<blockquote><p>Subkismet is a framework to fight against spam in .NET web applications which assists .NET developers to stop spammers and defeat them. Subkismet is actually a set of controls, service clients and other tools to accomplish this goal but we&#8217;re making it a framework smoothly</p></blockquote>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/akismet.wordpress.com/90/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/akismet.wordpress.com/90/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/akismet.wordpress.com/90/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=blog.akismet.com&blog=116920&post=90&subd=akismet&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Sat, 05 Jan 2008 19:38:10 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Matt Mullenweg\";}s:7:\"summary\";s:1747:\"<div class=\"snap_preview\"><br /><p><a href=\"http://nayyeri.net/blog/subkismet-1-0-released/\">Subkismet 1.0 Released : Keyvan Nayyeri</a></p>
<blockquote><p>Subkismet is a framework to fight against spam in .NET web applications which assists .NET developers to stop spammers and defeat them. Subkismet is actually a set of controls, service clients and other tools to accomplish this goal but we&#8217;re making it a framework smoothly</p></blockquote>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/akismet.wordpress.com/90/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/akismet.wordpress.com/90/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/akismet.wordpress.com/90/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/akismet.wordpress.com/90/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/akismet.wordpress.com/90/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=blog.akismet.com&blog=116920&post=90&subd=akismet&ref=&feed=1\" /></div>\";}i:28;a:7:{s:5:\"title\";s:44:\"Lorelle on WP: WordPress 2.4 Release Delayed\";s:4:\"guid\";s:69:\"http://lorelle.wordpress.com/2008/01/04/wordpress-24-release-delayed/\";s:4:\"link\";s:69:\"http://lorelle.wordpress.com/2008/01/04/wordpress-24-release-delayed/\";s:11:\"description\";s:7511:\"<div class=\"snap_preview\"><br /><p><a href=\"http://lorelle.wordpress.com/tag/wordpress-news/\" title=\"WordPress News\"><img src=\"http://lorelle.files.wordpress.com/2007/01/wpnews1.png\" alt=\"WordPress News\" align=\"right\" /></a>According to <a href=\"http://weblogtoolscollection.com/archives/2008/01/04/24-skipped-25-is-next/\" title=\"2.4 Skipped 2.5 Is Next\">Weblog Tools Collection</a>, referencing comments and announcements made in the developer mailing list, the much anticipated WordPress 2.4 will be released in March not January. </p>
<p>Indeed, WordPress 2.4 has now been removed from the <a href=\"http://trac.wordpress.org/roadmap/\" title=\"WordPress\">WordPress Roadmap</a>, and <a href=\"http://trac.wordpress.org/milestone/2.5\" title=\"2.5\">WordPress 2.5</a> is still scheduled for March 24, 2008.</p>
<p>The reasons appear to be because of the holidays, as well as the amount of changes that need to be made to accommodate the new Administration Panels interface. The decision includes skipping version 2.4 and going straight to 2.5, which was to be released in March. </p>
<p>I&#8217;ve been warning my readers on the <a href=\"http://www.blogherald.com/\" title=\"Blog Herald\" rel=\"tag\">Blog Herald</a> not to be disappointed if this coming version was delayed. There are a lot of great improvements and features coming, and crowding them in during the busy holiday season is just a little much. This also gives WordPress Theme and Plugin developers time to update their stuff in time for the release in March.</p>
<p>The mandatory update, <a href=\"http://wordpress.org/development/2007/12/wordpress-232/\" title=\"WordPress 2.3.2\">WordPress 2.3.2</a>, is out and is a <strong>required update</strong> to fix some security vulnerabilities. The <a href=\"http://westi.wordpress.com/2007/12/30/wordpress-232-in-detail/\" title=\"WordPress 2.3.2 in detail\">full details of the update</a> include an urgent security release to fix a <a href=\"http://trac.wordpress.org/ticket/5487\" title=\"expose your draft posts\">vulnerability in draft posts</a>, <a href=\"http://trac.wordpress.org/ticket/5473\" title=\"suppresses some error messages\">suppression of some errors messages</a> that may put your database at risk, and other <a href=\"http://trac.wordpress.org/query?status=closed&amp;milestone=2.3.2&amp;resolution=fixed&amp;order=priority\" title=\"fixed bugs\">bug fixes</a>. <a href=\"http://wordpress.org/download/\" title=\"Get 2.3.2 now\">Upgrade to WordPress 2.3.2 now</a>.</p>
<p>The buzz around the new backend WordPress Administration Panels is spreading. <a href=\"http://www.tubetorial.com/wordpress-24-administration-panel-preview/\" title=\"WordPress 2.4 Administration Panel Preview\">Tubetorial has a &#8220;WordPress 2.4 Administration Panel Preview&#8221;</a> video which shows just what has been done to date, with a lot more to come. <a href=\"http://hyper123.net/wp_demo/\" title=\"Hyper SVN WordPress Administration Panels Demo\">Hyper SVN has a &#8220;live&#8221; demo</a> of the new WordPress Administration Panels. Expect many of these sneak previews hitting the web as everyone wants to be the first to show it off. </p>
<p>Remember, the delay in releasing this next version of WordPress means that these sneak previews are not the final design. Things will change a lot as the development continues. </p>
<p>Also expect a few more security releases in the interim which may include some of the new improvements they&#8217;ve been working on.</p>
<p>You can keep up with more WordPress news and announcements on the <a href=\"http://wwww.blogherald.com/?s=wordpress+wednesday\" title=\"Articles on WordPress Wednesday\">WordPress Wednesday</a> on the <a href=\"http://www.blogherald.com/\" title=\"Blog Herald\" rel=\"tag\">Blog Herald</a>.</p>
<h4>Related Articles</h4>
<ul>
<li><a href=\"http://lorelle.wordpress.com/2007/12/05/staying-on-track-with-wordpress-24-news/\" title=\"Staying on Track with WordPress 2.4 News\">Staying on Track with WordPress 2.4 News</a></li>
<li><a href=\"http://www.blogherald.com/2007/11/29/wordpress-wednesday-news-will-you-turn-off-akismet-wordpress-24-delayed-and-more-wordpress-news/\" title=\"Will You Turn Off Akismet? WordPress 2.4 Delayed, and More WordPress News\">WordPress Wednesday News: Will You Turn Off Akismet? WordPress 2.4 Delayed, and More WordPress News</a></li>
<li><a href=\"http://lorelle.wordpress.com/2007/10/26/wordpress-23-tag-news/\" title=\"WordPress 2.3 Tag News\">WordPress 2.3 Tag News</a></li>
</ul>
<p><img src=\"http://lorelle.files.wordpress.com/2006/08/sig.gif\" alt=\"\" /><br />
<hr />
<p><font size=\"-1\"><b>Site Search Tags:</b> <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+news\" rel=\"tag\">wordpress news</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+2.4\" rel=\"tag\">wordpress 2.4</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+2.5\" rel=\"tag\">wordpress 2.5</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+delayed\" rel=\"tag\">wordpress delayed</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+versions\" rel=\"tag\">wordpress versions</a> </p>
<p><a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/02/rss.png\" alt=\"Feed on Lorelle on WordPress\" /></a> <a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\">Subscribe</a>  <a href=\"http://feeds.feedburner.com/LorelleOnWordpress\" title=\"Feedburner Lorelle on WordPress Feed\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/04/feedburnericon.gif\" alt=\"Feedburner icon\" />Via Feedburner</a>  <a href=\"http://www.feedblitz.com/f/?Sub=182399\" title=\"Lorelle on WordPress - full site feed email subscription\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/03/email.gif\" alt=\"\" />Subscribe by Email</a><br /><a href=\"http://lorelle.wordpress.com/about/\" title=\"Copyright Protected by Brent and Lorelle VanFossen\">Copyright Lorelle VanFossen</a>, the author of <a href=\"http://lorelle.wordpress.com/books/blogging-tips/\" title=\"Blogging Tips Book By Lorelle VanFossen\"><em>Blogging Tips, What Bloggers Won\'t Tell You About Blogging</em></a>.</font></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2312/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2312/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2312/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2312&subd=lorelle&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Sat, 05 Jan 2008 03:57:42 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:17:\"Lorelle VanFossen\";}s:7:\"summary\";s:7511:\"<div class=\"snap_preview\"><br /><p><a href=\"http://lorelle.wordpress.com/tag/wordpress-news/\" title=\"WordPress News\"><img src=\"http://lorelle.files.wordpress.com/2007/01/wpnews1.png\" alt=\"WordPress News\" align=\"right\" /></a>According to <a href=\"http://weblogtoolscollection.com/archives/2008/01/04/24-skipped-25-is-next/\" title=\"2.4 Skipped 2.5 Is Next\">Weblog Tools Collection</a>, referencing comments and announcements made in the developer mailing list, the much anticipated WordPress 2.4 will be released in March not January. </p>
<p>Indeed, WordPress 2.4 has now been removed from the <a href=\"http://trac.wordpress.org/roadmap/\" title=\"WordPress\">WordPress Roadmap</a>, and <a href=\"http://trac.wordpress.org/milestone/2.5\" title=\"2.5\">WordPress 2.5</a> is still scheduled for March 24, 2008.</p>
<p>The reasons appear to be because of the holidays, as well as the amount of changes that need to be made to accommodate the new Administration Panels interface. The decision includes skipping version 2.4 and going straight to 2.5, which was to be released in March. </p>
<p>I&#8217;ve been warning my readers on the <a href=\"http://www.blogherald.com/\" title=\"Blog Herald\" rel=\"tag\">Blog Herald</a> not to be disappointed if this coming version was delayed. There are a lot of great improvements and features coming, and crowding them in during the busy holiday season is just a little much. This also gives WordPress Theme and Plugin developers time to update their stuff in time for the release in March.</p>
<p>The mandatory update, <a href=\"http://wordpress.org/development/2007/12/wordpress-232/\" title=\"WordPress 2.3.2\">WordPress 2.3.2</a>, is out and is a <strong>required update</strong> to fix some security vulnerabilities. The <a href=\"http://westi.wordpress.com/2007/12/30/wordpress-232-in-detail/\" title=\"WordPress 2.3.2 in detail\">full details of the update</a> include an urgent security release to fix a <a href=\"http://trac.wordpress.org/ticket/5487\" title=\"expose your draft posts\">vulnerability in draft posts</a>, <a href=\"http://trac.wordpress.org/ticket/5473\" title=\"suppresses some error messages\">suppression of some errors messages</a> that may put your database at risk, and other <a href=\"http://trac.wordpress.org/query?status=closed&amp;milestone=2.3.2&amp;resolution=fixed&amp;order=priority\" title=\"fixed bugs\">bug fixes</a>. <a href=\"http://wordpress.org/download/\" title=\"Get 2.3.2 now\">Upgrade to WordPress 2.3.2 now</a>.</p>
<p>The buzz around the new backend WordPress Administration Panels is spreading. <a href=\"http://www.tubetorial.com/wordpress-24-administration-panel-preview/\" title=\"WordPress 2.4 Administration Panel Preview\">Tubetorial has a &#8220;WordPress 2.4 Administration Panel Preview&#8221;</a> video which shows just what has been done to date, with a lot more to come. <a href=\"http://hyper123.net/wp_demo/\" title=\"Hyper SVN WordPress Administration Panels Demo\">Hyper SVN has a &#8220;live&#8221; demo</a> of the new WordPress Administration Panels. Expect many of these sneak previews hitting the web as everyone wants to be the first to show it off. </p>
<p>Remember, the delay in releasing this next version of WordPress means that these sneak previews are not the final design. Things will change a lot as the development continues. </p>
<p>Also expect a few more security releases in the interim which may include some of the new improvements they&#8217;ve been working on.</p>
<p>You can keep up with more WordPress news and announcements on the <a href=\"http://wwww.blogherald.com/?s=wordpress+wednesday\" title=\"Articles on WordPress Wednesday\">WordPress Wednesday</a> on the <a href=\"http://www.blogherald.com/\" title=\"Blog Herald\" rel=\"tag\">Blog Herald</a>.</p>
<h4>Related Articles</h4>
<ul>
<li><a href=\"http://lorelle.wordpress.com/2007/12/05/staying-on-track-with-wordpress-24-news/\" title=\"Staying on Track with WordPress 2.4 News\">Staying on Track with WordPress 2.4 News</a></li>
<li><a href=\"http://www.blogherald.com/2007/11/29/wordpress-wednesday-news-will-you-turn-off-akismet-wordpress-24-delayed-and-more-wordpress-news/\" title=\"Will You Turn Off Akismet? WordPress 2.4 Delayed, and More WordPress News\">WordPress Wednesday News: Will You Turn Off Akismet? WordPress 2.4 Delayed, and More WordPress News</a></li>
<li><a href=\"http://lorelle.wordpress.com/2007/10/26/wordpress-23-tag-news/\" title=\"WordPress 2.3 Tag News\">WordPress 2.3 Tag News</a></li>
</ul>
<p><img src=\"http://lorelle.files.wordpress.com/2006/08/sig.gif\" alt=\"\" /><br />
<hr />
<p><font size=\"-1\"><b>Site Search Tags:</b> <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+news\" rel=\"tag\">wordpress news</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+2.4\" rel=\"tag\">wordpress 2.4</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+2.5\" rel=\"tag\">wordpress 2.5</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+delayed\" rel=\"tag\">wordpress delayed</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+versions\" rel=\"tag\">wordpress versions</a> </p>
<p><a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/02/rss.png\" alt=\"Feed on Lorelle on WordPress\" /></a> <a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\">Subscribe</a>  <a href=\"http://feeds.feedburner.com/LorelleOnWordpress\" title=\"Feedburner Lorelle on WordPress Feed\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/04/feedburnericon.gif\" alt=\"Feedburner icon\" />Via Feedburner</a>  <a href=\"http://www.feedblitz.com/f/?Sub=182399\" title=\"Lorelle on WordPress - full site feed email subscription\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/03/email.gif\" alt=\"\" />Subscribe by Email</a><br /><a href=\"http://lorelle.wordpress.com/about/\" title=\"Copyright Protected by Brent and Lorelle VanFossen\">Copyright Lorelle VanFossen</a>, the author of <a href=\"http://lorelle.wordpress.com/books/blogging-tips/\" title=\"Blogging Tips Book By Lorelle VanFossen\"><em>Blogging Tips, What Bloggers Won\'t Tell You About Blogging</em></a>.</font></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2312/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2312/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2312/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2312/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2312/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2312&subd=lorelle&ref=&feed=1\" /></div>\";}i:29;a:7:{s:5:\"title\";s:65:\"Lorelle on WP: Unworthy Again: Nominated for Performancing Awards\";s:4:\"guid\";s:90:\"http://lorelle.wordpress.com/2008/01/04/unworthy-again-nominated-for-performancing-awards/\";s:4:\"link\";s:90:\"http://lorelle.wordpress.com/2008/01/04/unworthy-again-nominated-for-performancing-awards/\";s:11:\"description\";s:3839:\"<div class=\"snap_preview\"><br /><p>On the list of things <a href=\"http://lorelle.wordpress.com/2006/06/04/nominated-for-9rules-not-worthy/\" title=\"Nominated for 9Rules - Not Worthy\">I&#8217;m not worthy of</a> are two award nominations from Peformancing: <a href=\"http://performancing.com/performancing-awards/most-influential-blogger-performancing-awards-2007-readers-choice-poll\" title=\"Performancing Awards for Most Influential Blogger Readers Choice 2007\">Most Influential Blogger Award</a> and <a href=\"http://performancing.com/performancing-awards/best-writing-blogging-blog-performancing-awards-2007-readers-choice-poll\" title=\"Performancing Best Writing Blogging Blog Awards 2007\">Best Writing and Blogging Award</a>.</p>
<p>It&#8217;s a reader&#8217;s choice poll, so you can vote for your favorites. I&#8217;m in good company, but also intimidated by the company I&#8217;m in. They are MUCH better than me at all of this blogging stuff. Give them your vote and I&#8217;m going to vote for them, too. </p>
<p>Thanks to Performancing and their crew for including me and my little blog about WordPress and blogging. </p>
<p>I just keep doing what I do, pausing to kick your blogging ass once in a while. I&#8217;m just glad you are here. That means more to me than the awards. Thanks.</p>
<p><img src=\"http://lorelle.files.wordpress.com/2006/08/sig.gif\" alt=\"\" /><br />
<hr />
<p><font size=\"-1\"><a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/02/rss.png\" alt=\"Feed on Lorelle on WordPress\" /></a> <a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\">Subscribe</a>  <a href=\"http://feeds.feedburner.com/LorelleOnWordpress\" title=\"Feedburner Lorelle on WordPress Feed\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/04/feedburnericon.gif\" alt=\"Feedburner icon\" />Via Feedburner</a>  <a href=\"http://www.feedblitz.com/f/?Sub=182399\" title=\"Lorelle on WordPress - full site feed email subscription\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/03/email.gif\" alt=\"\" />Subscribe by Email</a><br /><a href=\"http://lorelle.wordpress.com/about/\" title=\"Copyright Protected by Brent and Lorelle VanFossen\">Copyright Lorelle VanFossen</a>, the author of <a href=\"http://lorelle.wordpress.com/books/blogging-tips/\" title=\"Blogging Tips Book By Lorelle VanFossen\"><em>Blogging Tips, What Bloggers Won\'t Tell You About Blogging</em></a>.</font></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2310/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2310/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2310/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2310&subd=lorelle&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Sat, 05 Jan 2008 01:57:17 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:17:\"Lorelle VanFossen\";}s:7:\"summary\";s:3839:\"<div class=\"snap_preview\"><br /><p>On the list of things <a href=\"http://lorelle.wordpress.com/2006/06/04/nominated-for-9rules-not-worthy/\" title=\"Nominated for 9Rules - Not Worthy\">I&#8217;m not worthy of</a> are two award nominations from Peformancing: <a href=\"http://performancing.com/performancing-awards/most-influential-blogger-performancing-awards-2007-readers-choice-poll\" title=\"Performancing Awards for Most Influential Blogger Readers Choice 2007\">Most Influential Blogger Award</a> and <a href=\"http://performancing.com/performancing-awards/best-writing-blogging-blog-performancing-awards-2007-readers-choice-poll\" title=\"Performancing Best Writing Blogging Blog Awards 2007\">Best Writing and Blogging Award</a>.</p>
<p>It&#8217;s a reader&#8217;s choice poll, so you can vote for your favorites. I&#8217;m in good company, but also intimidated by the company I&#8217;m in. They are MUCH better than me at all of this blogging stuff. Give them your vote and I&#8217;m going to vote for them, too. </p>
<p>Thanks to Performancing and their crew for including me and my little blog about WordPress and blogging. </p>
<p>I just keep doing what I do, pausing to kick your blogging ass once in a while. I&#8217;m just glad you are here. That means more to me than the awards. Thanks.</p>
<p><img src=\"http://lorelle.files.wordpress.com/2006/08/sig.gif\" alt=\"\" /><br />
<hr />
<p><font size=\"-1\"><a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/02/rss.png\" alt=\"Feed on Lorelle on WordPress\" /></a> <a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\">Subscribe</a>  <a href=\"http://feeds.feedburner.com/LorelleOnWordpress\" title=\"Feedburner Lorelle on WordPress Feed\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/04/feedburnericon.gif\" alt=\"Feedburner icon\" />Via Feedburner</a>  <a href=\"http://www.feedblitz.com/f/?Sub=182399\" title=\"Lorelle on WordPress - full site feed email subscription\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/03/email.gif\" alt=\"\" />Subscribe by Email</a><br /><a href=\"http://lorelle.wordpress.com/about/\" title=\"Copyright Protected by Brent and Lorelle VanFossen\">Copyright Lorelle VanFossen</a>, the author of <a href=\"http://lorelle.wordpress.com/books/blogging-tips/\" title=\"Blogging Tips Book By Lorelle VanFossen\"><em>Blogging Tips, What Bloggers Won\'t Tell You About Blogging</em></a>.</font></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2310/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2310/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2310/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2310/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2310/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2310&subd=lorelle&ref=&feed=1\" /></div>\";}i:30;a:7:{s:5:\"title\";s:73:\"Weblog Tools Collection: Best Blog Typography - Performancing Awards 2007\";s:4:\"guid\";s:100:\"http://weblogtoolscollection.com/archives/2008/01/04/best-blog-typography-performancing-awards-2007/\";s:4:\"link\";s:100:\"http://weblogtoolscollection.com/archives/2008/01/04/best-blog-typography-performancing-awards-2007/\";s:11:\"description\";s:909:\"<p><a href=\"http://performancing.com/performancing-awards/best-blog-typography-performancing-awards-2007-readers-choice-poll\">Best Blog Typography - Performancing Awards 2007 Reader&#8217;s Choice Poll </a> WeblogToolsCollection.com has been chosen to be one of the contenders for the Best Blog Typography Award from Performancing.com. The blog with the most number of votes by January 10, 2007 wins the 2007 Reader&#8217;s Choice award. They define typography as &#8220;design and arrangement of fonts&#8221;. We are in some tremendous company (ALA, Freeland Switch etc.), but please vote for us if you feel that we deserve the honor. Check out and vote for contestants in the rest of <a href=\"http://performancing.com/tags/performancing-awards\">Performancing Awards</a>. Thanks Performancing</p>
<p>[EDIT] How could I forget the original designer? Thanks <a href=\"http://weblog.jcraveiro.com/\">João</a></p>\";s:7:\"pubdate\";s:31:\"Sat, 05 Jan 2008 01:30:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Mark Ghosh\";}s:7:\"summary\";s:909:\"<p><a href=\"http://performancing.com/performancing-awards/best-blog-typography-performancing-awards-2007-readers-choice-poll\">Best Blog Typography - Performancing Awards 2007 Reader&#8217;s Choice Poll </a> WeblogToolsCollection.com has been chosen to be one of the contenders for the Best Blog Typography Award from Performancing.com. The blog with the most number of votes by January 10, 2007 wins the 2007 Reader&#8217;s Choice award. They define typography as &#8220;design and arrangement of fonts&#8221;. We are in some tremendous company (ALA, Freeland Switch etc.), but please vote for us if you feel that we deserve the honor. Check out and vote for contestants in the rest of <a href=\"http://performancing.com/tags/performancing-awards\">Performancing Awards</a>. Thanks Performancing</p>
<p>[EDIT] How could I forget the original designer? Thanks <a href=\"http://weblog.jcraveiro.com/\">João</a></p>\";}i:31;a:7:{s:5:\"title\";s:18:\"Matt: Particletree\";s:4:\"guid\";s:45:\"http://photomatt.net/2008/01/04/particletree/\";s:4:\"link\";s:45:\"http://photomatt.net/2008/01/04/particletree/\";s:11:\"description\";s:207:\"<p><a href=\"http://particletree.com/\">Particletre</a> is a beautiful site and web magazine, built with WordPress. It&#8217;s from the fine folks who brought you the <a href=\"http://wufoo.com/\">Wufoo</a>.</p>\";s:7:\"pubdate\";s:31:\"Fri, 04 Jan 2008 23:57:13 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:207:\"<p><a href=\"http://particletree.com/\">Particletre</a> is a beautiful site and web magazine, built with WordPress. It&#8217;s from the fine folks who brought you the <a href=\"http://wufoo.com/\">Wufoo</a>.</p>\";}i:32;a:7:{s:5:\"title\";s:48:\"Weblog Tools Collection: 2.4 Skipped 2.5 Is Next\";s:4:\"guid\";s:75:\"http://weblogtoolscollection.com/archives/2008/01/04/24-skipped-25-is-next/\";s:4:\"link\";s:75:\"http://weblogtoolscollection.com/archives/2008/01/04/24-skipped-25-is-next/\";s:11:\"description\";s:661:\"<p>As discussed in the developer mailing list, the next release of WordPress will be in March instead of January because of the holidays and the amount of changes that will take place in the codebase as well as the admin section. The decision was made to consider 2.4 a skipped December release and move straight on to 2.5. The reasons for the change in the schedule include some good things cooking in the oven and the developers do not want this to become a rushed release.</p>
<p>So to sum things up. There will be no 2.4. Instead, we will see 2.5 which is scheduled for release in March. Various official docs and roadmaps will be updated in due course.</p>\";s:7:\"pubdate\";s:31:\"Fri, 04 Jan 2008 13:15:05 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jeffro2pt0\";}s:7:\"summary\";s:661:\"<p>As discussed in the developer mailing list, the next release of WordPress will be in March instead of January because of the holidays and the amount of changes that will take place in the codebase as well as the admin section. The decision was made to consider 2.4 a skipped December release and move straight on to 2.5. The reasons for the change in the schedule include some good things cooking in the oven and the developers do not want this to become a rushed release.</p>
<p>So to sum things up. There will be no 2.4. Instead, we will see 2.5 which is scheduled for release in March. Various official docs and roadmaps will be updated in due course.</p>\";}i:33;a:7:{s:5:\"title\";s:33:\"bbPress: bbPress 0.8.3.1 released\";s:4:\"guid\";s:54:\"http://bbpress.org/blog/2008/01/bbpress-0831-released/\";s:4:\"link\";s:54:\"http://bbpress.org/blog/2008/01/bbpress-0831-released/\";s:11:\"description\";s:1364:\"<p>Due to popular demand we have bundled a bug-fix release for bbPress. 0.8.3.1 (still called &#8220;Desmond&#8221; I believe) and it is now available for <a href=\"http://bbpress.org/download/\">download</a>.</p>
<p>This version is <em>not</em> the latest development release so as to remain as compatible as possible with the current version of WordPress.</p>
<p>The primary reason for the release is to fix some bugs in the MySQLi implementation. We anticipate that MySQLi support will be dropped in the future and to this end we have made MySQL the default extension instead of MySQLi.</p>
<p>A few other fixes and enhancements have also snuck in:</p>
<ul>
<li>Deep forum breadcrumbs with thanks to baptiste</li>
<li>More consistent topic labeling methods - users of the <a href=\"http://bbpress.org/plugins/topic/16\">support forum plugin</a> will probably need to upgrade to version 2.3.3</li>
<li>Some fixes to stop orphaned sub-forums from disappearing from all view</li>
<li>There is now one of those fancy checkboxes to mark a user as a bozo</li>
</ul>
<p>A couple of those changes will affect existing themes. If you have questions about adapting your theme to be compatible with the new topic labeling and forum breadcrumb features, then ask over on <a href=\"http://bbpress.org/forums/topic/making-your-theme-compatible-with-0831\">this forum topic</a>.</p>\";s:7:\"pubdate\";s:31:\"Fri, 04 Jan 2008 02:31:54 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Sam Bauers\";}s:7:\"summary\";s:1364:\"<p>Due to popular demand we have bundled a bug-fix release for bbPress. 0.8.3.1 (still called &#8220;Desmond&#8221; I believe) and it is now available for <a href=\"http://bbpress.org/download/\">download</a>.</p>
<p>This version is <em>not</em> the latest development release so as to remain as compatible as possible with the current version of WordPress.</p>
<p>The primary reason for the release is to fix some bugs in the MySQLi implementation. We anticipate that MySQLi support will be dropped in the future and to this end we have made MySQL the default extension instead of MySQLi.</p>
<p>A few other fixes and enhancements have also snuck in:</p>
<ul>
<li>Deep forum breadcrumbs with thanks to baptiste</li>
<li>More consistent topic labeling methods - users of the <a href=\"http://bbpress.org/plugins/topic/16\">support forum plugin</a> will probably need to upgrade to version 2.3.3</li>
<li>Some fixes to stop orphaned sub-forums from disappearing from all view</li>
<li>There is now one of those fancy checkboxes to mark a user as a bozo</li>
</ul>
<p>A couple of those changes will affect existing themes. If you have questions about adapting your theme to be compatible with the new topic labeling and forum breadcrumb features, then ask over on <a href=\"http://bbpress.org/forums/topic/making-your-theme-compatible-with-0831\">this forum topic</a>.</p>\";}i:34;a:7:{s:5:\"title\";s:32:\"Matt: Graffitti disses WordPress\";s:4:\"guid\";s:59:\"http://photomatt.net/2008/01/03/graffitti-disses-wordpress/\";s:4:\"link\";s:59:\"http://photomatt.net/2008/01/03/graffitti-disses-wordpress/\";s:11:\"description\";s:368:\"<p><a href=\"http://charlesstricklin.com/2008/01/03/graffitti-disses-wordpress/\">Graffitti disses WordPress</a>, their <a href=\"http://graffiticms.com/landing-pages/the-wordpress-as-a-content-management-system-cms-alternative/\">landing page boasts a 2-minute install</a>. Seems pretty aggressive for a product that&#8217;s only available for pre-purchase (at $199).</p>\";s:7:\"pubdate\";s:31:\"Thu, 03 Jan 2008 21:44:25 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:368:\"<p><a href=\"http://charlesstricklin.com/2008/01/03/graffitti-disses-wordpress/\">Graffitti disses WordPress</a>, their <a href=\"http://graffiticms.com/landing-pages/the-wordpress-as-a-content-management-system-cms-alternative/\">landing page boasts a 2-minute install</a>. Seems pretty aggressive for a product that&#8217;s only available for pre-purchase (at $199).</p>\";}i:35;a:7:{s:5:\"title\";s:54:\"Weblog Tools Collection: Advanced WordPress Help Sheet\";s:4:\"guid\";s:83:\"http://weblogtoolscollection.com/archives/2008/01/03/advanced-wordpress-help-sheet/\";s:4:\"link\";s:83:\"http://weblogtoolscollection.com/archives/2008/01/03/advanced-wordpress-help-sheet/\";s:11:\"description\";s:706:\"<p><a href=\"http://wpcandy.com/the-advanced-wordpress-help-sheet/\">The Advanced WordPress Help Sheet</a>: Michael has put together another <a href=\"http://wpcandy.com/wp-content/uploads/Advanced-WordPress-Help-Sheet.pdf\">PDF Help sheet for WordPress</a>, this time with advanced tips and tricks to use various WordPress functions within your theme. This includes various code snippets from Styling Different Categories to Dynamic Page Titles. He says that this is the first of a few others that he will be putting together and is up for suggestions and ideas. Also check out Michael&#8217;s other <a href=\"http://wpcandy.com/the-wordpress-help-sheet/\">WordPress Help Sheet</a> from the past. Via Email.</p>\";s:7:\"pubdate\";s:31:\"Thu, 03 Jan 2008 18:45:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Mark Ghosh\";}s:7:\"summary\";s:706:\"<p><a href=\"http://wpcandy.com/the-advanced-wordpress-help-sheet/\">The Advanced WordPress Help Sheet</a>: Michael has put together another <a href=\"http://wpcandy.com/wp-content/uploads/Advanced-WordPress-Help-Sheet.pdf\">PDF Help sheet for WordPress</a>, this time with advanced tips and tricks to use various WordPress functions within your theme. This includes various code snippets from Styling Different Categories to Dynamic Page Titles. He says that this is the first of a few others that he will be putting together and is up for suggestions and ideas. Also check out Michael&#8217;s other <a href=\"http://wpcandy.com/the-wordpress-help-sheet/\">WordPress Help Sheet</a> from the past. Via Email.</p>\";}i:36;a:7:{s:5:\"title\";s:64:\"Weblog Tools Collection: Install WordPress Locally - Part 2 Of 2\";s:4:\"guid\";s:91:\"http://weblogtoolscollection.com/archives/2008/01/03/install-wordpress-locally-part-2-of-2/\";s:4:\"link\";s:91:\"http://weblogtoolscollection.com/archives/2008/01/03/install-wordpress-locally-part-2-of-2/\";s:11:\"description\";s:9574:\"<p>Welcome to part two of a two part series of articles that will guide you through the process of installing a fresh copy of WordPress or your public WordPress blog to your local machine. The first part of this series covered the installation and configuration of WampServer. Now it&#8217;s time to move on to the hard, technical stuff.</p>
<h2>Installing WordPress Fresh:</h2>
<p>One thing you must know before we move on is that, by default, your database username is &#8216;<strong>root</strong>&#8216; and the default password is <strong>blank</strong>. In other words, there is no password assigned to the username of root. This would be extremely insecure if this web server were made available to the public but because it&#8217;s assigned to the local address of your machine, you have nothing to worry about.</p>
<p>To begin, left click on the WampServer icon and select <strong>PHPMyAdmin</strong>. Where the text labeled <strong>CREATE NEW DATABASE</strong> is located, type in the name of the database that will house your installation of WordPress. For simplicity, I normally call the database <strong>wordpress</strong>. Then click on the <strong>Create</strong> button. We now have an empty database that the WP installation files can work with.</p>
<p><a href=\"http://wordpress.org/download/\" title=\"http://wordpress.org/download/\" target=\"_blank\">Download</a> the latest version of WordPress, then extract the files to your desktop. Open the WordPress folder and look for <strong>WP-Config-Sample</strong>. Open this file in your preferred text editor. The <strong>DB_Name</strong> is the name of the database you created for WordPress. The <strong>DB_User</strong> is root. The <strong>DB_Password</strong> is blank. These three values are the only ones you&#8217;ll have to change. Once those changes are in place, save the file as <strong>WP-Config.PHP</strong></p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/configexample.png\" alt=\"WP Config Example\" /></p>
<p>If you want to install WordPress into the <strong>ROOT</strong> directory as you would on a public web server, take all of the files and folders within the WordPress folder and move them into the WWW folder. <strong>WWW</strong> is the same as <strong>Public_HTML</strong> and is the folder which houses all of your web documents. If you don&#8217;t want to install WordPress into the root directory, create a new directory and place all of the files into that one. Just make sure the files are within the WWW folder, or else they won&#8217;t be accessible.</p>
<p>Once that&#8217;s finished, point your browser to <strong>http://localhost/wp-admin/install.php</strong> Follow the directions as they are pretty self explanatory and when your finished, you&#8217;ll have a fully functioning, fresh install of WordPress that you can do whatever you want with.</p>
<h2>Migrating WordPress From Public To Localhost:</h2>
<p>Migrating an existing WordPress install onto your local computer is not as easy as a fresh install. If you haven&#8217;t already, make sure you have made the appropriate PHP.ini file changes that were explained in <a href=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" title=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" target=\"_blank\">part 1</a>. If you don&#8217;t, you will run into numerous errors about the SQL file being too large to import.</p>
<p>In my circumstance, my webhost offers it&#8217;s customers Cpanel as a means to control all aspects of my Webhosting account. Cpanel provides me with a way to generate a full backup of my domain. This backup includes all of the hardcoded directories and files attached to my domain as well as any databases I have created. After you create a full backup of your domain through Cpanel <strong>(if you have that option)</strong> download the backup to your desktop. Once downloaded, open up the file and browse to the Public_HTML directory. Extract this directory&#8217;s contents into the WWW folder on your hard drive.</p>
<p>Once thats finished,  look inside of the mysql directory within your backup file. This directory contains all of the MySQL databases you have created through your webhosting account. Extract the SQL file that pertains to your WordPress install and place it on the desktop.</p>
<blockquote><p>Ok, before we move on, lets review where we&#8217;re at. We backed up all of the files related to the hosting account and then downloaded that file to the desktop. We then extracted all of the files within the Public_HTML directory into the WWW directory. We then looked inside of the backup file and extracted the SQL file that pertains to the WordPress installation. At this point, the folder structure within the WWW folder on your hard drive should mimic that of what you would see within the Public_HTML folder on your webhost.</p></blockquote>
<p>Now, left click on the WampServer icon and click on PHPMyAdmin. Click on the link that says <strong>IMPORT</strong>. Click on the <strong>BROWSE</strong> button and locate the SQL file you extracted to your desktop that pertains to your WordPress installation. After you locate and double click on the file, click on the <strong>GO</strong> button. It might take a little while, but the import process should be successful. If you receive an error that states the SQL file was too large, please re-visit <a href=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" title=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" target=\"_blank\">part 1</a> and make sure the changes were saved to your PHP.ini file. Also, I wanted to share that if you have the SezWho comment rating plugin installed, you may receive errors that are related to the plugins database tables. If this is the case, you will need to open the SQL file in a text editor and remove all of the lines that pertain to those tables which are usually prefixed with <strong>sz_ </strong>and then try to import the SQL file again.</p>
<p><strong>If the import was successful, pat yourself on the back because were almost through with this process.</strong></p>
<p>If you do not want to do the next step through the database you can instead, add these constants to your WP-Config file and they will perform the same function as the database edits.</p>
<p><strong><code>define(\'WP_HOME\', \'localhost\' );</code><br />
<code>define(\'WP_SITEURL\', \'localhost\');</code></strong></p>
<p>In <strong>PHPMyAdmin</strong>, the database you imported will now be selectable in the drop menu that is located near the top left portion of the webpage. Click on the drop down arrow and select the database you just imported. Near the top center of the page, there will be a series of tabs. Click on the <strong>SEARCH</strong> tab. In the search box, type in the full URL to which your public WordPress install refers to. In my case, I typed in <a href=\"http://www.jeffro2pt0.com\" title=\"http://www.jeffro2pt0.com\" target=\"_blank\">http://www.jeffro2pt0.com</a> This will search the entire database for entries of that domain. The search results should find entries related to that domain within the table <strong>WP-OPTIONS</strong>. Click on the <strong>Browse</strong> link to dig into this particular table.</p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/optionnames.png\" alt=\"SQL Option Names\" /></p>
<p>You only need to concern yourself with the top two entries, <strong>SiteURL</strong> and <strong>HOME</strong>. Click on the <strong>Pencil</strong> icon for <strong>SiteURL</strong> which is just to the left of the <strong>X </strong>icon. This will open up the editing page. In the large text box on the bottom, change the <strong>URL</strong> to <strong>http://localhost</strong> then click on the <strong>GO</strong> button. Now do the same thing for <strong>HOME</strong>. After you change <strong>HOME</strong>, you can exit out of PHPMyAdmin.</p>
<p><strong>If you have never opened the .htaccess file to hard code redirection attributes, you can skip the next step and you are essentially finished. </strong></p>
<p>The last thing to do is to edit the <strong>.htaccess</strong> file and remove any hard coded redirection attributes. If you don&#8217;t do this, each time you try to load your blog on your local machine, it will automatically redirect to your public blog or which ever URL you configured in your .htaccess file.</p>
<h2>Victory Lane:</h2>
<p>If you&#8217;ve managed to read this far, congratulations. After all of that, you should be able to access and browse your blog on your local machine exactly how you would in a public domain. This guide is by no means a cure for all. This was my detailed approach as to how I migrated my public install to a local install. Some of the actions I performed may not have been necessary, nor required, but this is the way I did it and it worked!</p>
<p>If you have a correction or a different way of doing things, by all means leave a comment. I will edit this article as corrections come in so the most accurate information is presented.</p>
<p>Also, now that you have the ability to dig around the ins and outs of your blog through the database, you&#8217;ll be able to see some things that you might not of known about before. Stay tuned for another article which highlights a <strong>VERY</strong> important issue pertaining to plugin developers that needs to be discussed. Perhaps we&#8217;ll be able to come up with a solution.</p>\";s:7:\"pubdate\";s:31:\"Thu, 03 Jan 2008 15:30:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jeffro2pt0\";}s:7:\"summary\";s:9574:\"<p>Welcome to part two of a two part series of articles that will guide you through the process of installing a fresh copy of WordPress or your public WordPress blog to your local machine. The first part of this series covered the installation and configuration of WampServer. Now it&#8217;s time to move on to the hard, technical stuff.</p>
<h2>Installing WordPress Fresh:</h2>
<p>One thing you must know before we move on is that, by default, your database username is &#8216;<strong>root</strong>&#8216; and the default password is <strong>blank</strong>. In other words, there is no password assigned to the username of root. This would be extremely insecure if this web server were made available to the public but because it&#8217;s assigned to the local address of your machine, you have nothing to worry about.</p>
<p>To begin, left click on the WampServer icon and select <strong>PHPMyAdmin</strong>. Where the text labeled <strong>CREATE NEW DATABASE</strong> is located, type in the name of the database that will house your installation of WordPress. For simplicity, I normally call the database <strong>wordpress</strong>. Then click on the <strong>Create</strong> button. We now have an empty database that the WP installation files can work with.</p>
<p><a href=\"http://wordpress.org/download/\" title=\"http://wordpress.org/download/\" target=\"_blank\">Download</a> the latest version of WordPress, then extract the files to your desktop. Open the WordPress folder and look for <strong>WP-Config-Sample</strong>. Open this file in your preferred text editor. The <strong>DB_Name</strong> is the name of the database you created for WordPress. The <strong>DB_User</strong> is root. The <strong>DB_Password</strong> is blank. These three values are the only ones you&#8217;ll have to change. Once those changes are in place, save the file as <strong>WP-Config.PHP</strong></p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/configexample.png\" alt=\"WP Config Example\" /></p>
<p>If you want to install WordPress into the <strong>ROOT</strong> directory as you would on a public web server, take all of the files and folders within the WordPress folder and move them into the WWW folder. <strong>WWW</strong> is the same as <strong>Public_HTML</strong> and is the folder which houses all of your web documents. If you don&#8217;t want to install WordPress into the root directory, create a new directory and place all of the files into that one. Just make sure the files are within the WWW folder, or else they won&#8217;t be accessible.</p>
<p>Once that&#8217;s finished, point your browser to <strong>http://localhost/wp-admin/install.php</strong> Follow the directions as they are pretty self explanatory and when your finished, you&#8217;ll have a fully functioning, fresh install of WordPress that you can do whatever you want with.</p>
<h2>Migrating WordPress From Public To Localhost:</h2>
<p>Migrating an existing WordPress install onto your local computer is not as easy as a fresh install. If you haven&#8217;t already, make sure you have made the appropriate PHP.ini file changes that were explained in <a href=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" title=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" target=\"_blank\">part 1</a>. If you don&#8217;t, you will run into numerous errors about the SQL file being too large to import.</p>
<p>In my circumstance, my webhost offers it&#8217;s customers Cpanel as a means to control all aspects of my Webhosting account. Cpanel provides me with a way to generate a full backup of my domain. This backup includes all of the hardcoded directories and files attached to my domain as well as any databases I have created. After you create a full backup of your domain through Cpanel <strong>(if you have that option)</strong> download the backup to your desktop. Once downloaded, open up the file and browse to the Public_HTML directory. Extract this directory&#8217;s contents into the WWW folder on your hard drive.</p>
<p>Once thats finished,  look inside of the mysql directory within your backup file. This directory contains all of the MySQL databases you have created through your webhosting account. Extract the SQL file that pertains to your WordPress install and place it on the desktop.</p>
<blockquote><p>Ok, before we move on, lets review where we&#8217;re at. We backed up all of the files related to the hosting account and then downloaded that file to the desktop. We then extracted all of the files within the Public_HTML directory into the WWW directory. We then looked inside of the backup file and extracted the SQL file that pertains to the WordPress installation. At this point, the folder structure within the WWW folder on your hard drive should mimic that of what you would see within the Public_HTML folder on your webhost.</p></blockquote>
<p>Now, left click on the WampServer icon and click on PHPMyAdmin. Click on the link that says <strong>IMPORT</strong>. Click on the <strong>BROWSE</strong> button and locate the SQL file you extracted to your desktop that pertains to your WordPress installation. After you locate and double click on the file, click on the <strong>GO</strong> button. It might take a little while, but the import process should be successful. If you receive an error that states the SQL file was too large, please re-visit <a href=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" title=\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\" target=\"_blank\">part 1</a> and make sure the changes were saved to your PHP.ini file. Also, I wanted to share that if you have the SezWho comment rating plugin installed, you may receive errors that are related to the plugins database tables. If this is the case, you will need to open the SQL file in a text editor and remove all of the lines that pertain to those tables which are usually prefixed with <strong>sz_ </strong>and then try to import the SQL file again.</p>
<p><strong>If the import was successful, pat yourself on the back because were almost through with this process.</strong></p>
<p>If you do not want to do the next step through the database you can instead, add these constants to your WP-Config file and they will perform the same function as the database edits.</p>
<p><strong><code>define(\'WP_HOME\', \'localhost\' );</code><br />
<code>define(\'WP_SITEURL\', \'localhost\');</code></strong></p>
<p>In <strong>PHPMyAdmin</strong>, the database you imported will now be selectable in the drop menu that is located near the top left portion of the webpage. Click on the drop down arrow and select the database you just imported. Near the top center of the page, there will be a series of tabs. Click on the <strong>SEARCH</strong> tab. In the search box, type in the full URL to which your public WordPress install refers to. In my case, I typed in <a href=\"http://www.jeffro2pt0.com\" title=\"http://www.jeffro2pt0.com\" target=\"_blank\">http://www.jeffro2pt0.com</a> This will search the entire database for entries of that domain. The search results should find entries related to that domain within the table <strong>WP-OPTIONS</strong>. Click on the <strong>Browse</strong> link to dig into this particular table.</p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2008/01/optionnames.png\" alt=\"SQL Option Names\" /></p>
<p>You only need to concern yourself with the top two entries, <strong>SiteURL</strong> and <strong>HOME</strong>. Click on the <strong>Pencil</strong> icon for <strong>SiteURL</strong> which is just to the left of the <strong>X </strong>icon. This will open up the editing page. In the large text box on the bottom, change the <strong>URL</strong> to <strong>http://localhost</strong> then click on the <strong>GO</strong> button. Now do the same thing for <strong>HOME</strong>. After you change <strong>HOME</strong>, you can exit out of PHPMyAdmin.</p>
<p><strong>If you have never opened the .htaccess file to hard code redirection attributes, you can skip the next step and you are essentially finished. </strong></p>
<p>The last thing to do is to edit the <strong>.htaccess</strong> file and remove any hard coded redirection attributes. If you don&#8217;t do this, each time you try to load your blog on your local machine, it will automatically redirect to your public blog or which ever URL you configured in your .htaccess file.</p>
<h2>Victory Lane:</h2>
<p>If you&#8217;ve managed to read this far, congratulations. After all of that, you should be able to access and browse your blog on your local machine exactly how you would in a public domain. This guide is by no means a cure for all. This was my detailed approach as to how I migrated my public install to a local install. Some of the actions I performed may not have been necessary, nor required, but this is the way I did it and it worked!</p>
<p>If you have a correction or a different way of doing things, by all means leave a comment. I will edit this article as corrections come in so the most accurate information is presented.</p>
<p>Also, now that you have the ability to dig around the ins and outs of your blog through the database, you&#8217;ll be able to see some things that you might not of known about before. Stay tuned for another article which highlights a <strong>VERY</strong> important issue pertaining to plugin developers that needs to be discussed. Perhaps we&#8217;ll be able to come up with a solution.</p>\";}i:37;a:7:{s:5:\"title\";s:60:\"Gravatar: Email gets personal with Gravatar and MessageFaces\";s:4:\"guid\";s:87:\"http://blog.gravatar.com/2008/01/02/email-gets-personal-with-gravatar-and-messagefaces/\";s:4:\"link\";s:87:\"http://blog.gravatar.com/2008/01/02/email-gets-personal-with-gravatar-and-messagefaces/\";s:11:\"description\";s:1941:\"<div class=\"snap_preview\"><br /><p>It&#8217;s been brought to my attention that there is a very cool <a href=\"https://addons.mozilla.org/en-US/thunderbird/addon/393\">Thunderbird plugin called MessageFaces</a> which, after you enable the option in the plugin preferences, will show gravatars in the header section of the email messages you view.  We happen to think that this is terrific, and one more example of how Gravatar can be used to bring a touch of personalization where there would otherwise be nothing but the cold feel of a whitewashed internet.  Thanks very much to  Jens Bannmann for writing this very cool plugin!</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/gravatar.wordpress.com/44/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/gravatar.wordpress.com/44/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/gravatar.wordpress.com/44/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=blog.gravatar.com&blog=1886259&post=44&subd=gravatar&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Wed, 02 Jan 2008 19:27:53 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:11:\"apokalyptik\";}s:7:\"summary\";s:1941:\"<div class=\"snap_preview\"><br /><p>It&#8217;s been brought to my attention that there is a very cool <a href=\"https://addons.mozilla.org/en-US/thunderbird/addon/393\">Thunderbird plugin called MessageFaces</a> which, after you enable the option in the plugin preferences, will show gravatars in the header section of the email messages you view.  We happen to think that this is terrific, and one more example of how Gravatar can be used to bring a touch of personalization where there would otherwise be nothing but the cold feel of a whitewashed internet.  Thanks very much to  Jens Bannmann for writing this very cool plugin!</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/gravatar.wordpress.com/44/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/gravatar.wordpress.com/44/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/gravatar.wordpress.com/44/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/gravatar.wordpress.com/44/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/gravatar.wordpress.com/44/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=blog.gravatar.com&blog=1886259&post=44&subd=gravatar&ref=&feed=1\" /></div>\";}i:38;a:7:{s:5:\"title\";s:52:\"Weblog Tools Collection: WordPress 2.4 Admin Preview\";s:4:\"guid\";s:80:\"http://weblogtoolscollection.com/archives/2008/01/02/wordpress-24-admin-preview/\";s:4:\"link\";s:80:\"http://weblogtoolscollection.com/archives/2008/01/02/wordpress-24-admin-preview/\";s:11:\"description\";s:753:\"<p><a href=\"http://hyper123.net/wp_demo/\">WordPress 2.4 Admin Preview</a>: Jordan built up a mockup of the new WordPress 2.4 admin backend. Some of the features work, some of them do not. However you can still get a good idea of what it will look like in 2.4 and where the admin redesign is headed. Via Email. Also, <a href=\"http://www.tubetorial.com/wordpress-24-administration-panel-preview/\">TubeTorial has a video walkthrough of the new admin interface</a>.</p>
<p>[EDIT] Please be mindful of the fact that this is a cursory glance at unfinished work on the WordPress admin interace and nothing else. Please read <a href=\"http://weblogtoolscollection.com/archives/2008/01/02/wordpress-24-admin-preview/#comment-1207162\">Matt&#8217;s comment</a>.</p>\";s:7:\"pubdate\";s:31:\"Wed, 02 Jan 2008 15:30:08 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Mark Ghosh\";}s:7:\"summary\";s:753:\"<p><a href=\"http://hyper123.net/wp_demo/\">WordPress 2.4 Admin Preview</a>: Jordan built up a mockup of the new WordPress 2.4 admin backend. Some of the features work, some of them do not. However you can still get a good idea of what it will look like in 2.4 and where the admin redesign is headed. Via Email. Also, <a href=\"http://www.tubetorial.com/wordpress-24-administration-panel-preview/\">TubeTorial has a video walkthrough of the new admin interface</a>.</p>
<p>[EDIT] Please be mindful of the fact that this is a cursory glance at unfinished work on the WordPress admin interace and nothing else. Please read <a href=\"http://weblogtoolscollection.com/archives/2008/01/02/wordpress-24-admin-preview/#comment-1207162\">Matt&#8217;s comment</a>.</p>\";}i:39;a:7:{s:5:\"title\";s:55:\"Lorelle on WP: Considering Writing Some WordPress Tips?\";s:4:\"guid\";s:80:\"http://lorelle.wordpress.com/2008/01/02/considering-writing-some-wordpress-tips/\";s:4:\"link\";s:80:\"http://lorelle.wordpress.com/2008/01/02/considering-writing-some-wordpress-tips/\";s:11:\"description\";s:10151:\"<div class=\"snap_preview\"><br /><p><a href=\"http://lorelle.wordpress.com/tag/wordpress-tips/\" title=\"WordPress Tips\"><img src=\"http://lorelle.files.wordpress.com/2006/11/wordpresstips.gif\" alt=\"\" align=\"right\" /></a>Do you want to write a WordPress tip? I encourage you to do so, either on your blog, on the <a href=\"http://www.wordpress.org/support\" title=\"WordPress Support Forums\" rel=\"tag\">WordPress Support Forums</a>, or for the <a href=\"http://codex.wordpress.org/\" rel=\"tag\" title=\"WordPress Codex - online manual for WordPress Users\">WordPress Codex</a>, the online manual for WordPress Users. It takes a lot of volunteer work to create a body of work for WordPress users to rely upon to help them blog better with WordPress, so all help is always welcome.</p>
<p>However, would you please do a few things for all WordPress fans everywhere first, before you publish your WordPress tips?</p>
<ul>
<li><strong>Search First:</strong> Search the web first to find other articles written on the same subject. If those are good, don&#8217;t write yours. If they can be improved upon, then write yours. If you find a lot, reconsider writing the topic and find a new one. Or find a totally new perspective on the same subject. We really need new and improved tips, not redundant.</li>
<li><strong>Write Well:</strong> Read <a href=\"http://www.blogherald.com/2007/07/09/tips-for-writing-good-wordpress-tips/\" title=\"Tips For Writing Good WordPress Tips\">Tips For Writing Good WordPress Tips</a> for tips on how to write even better WordPress tips.</li>
<li><strong>Label It Appropriately:</strong> Is it a <a href=\"http://www.blogherald.com/2007/07/10/what-is-a-tip-technique-how-to-advice-guide-and-only-way-to-do-it/\" title=\"What Is A Tip, Technique, How-To, Advice, Guide, And Only Way To Do It?\">tip, technique, how-to, advice, guide, hack</a>, or the only way to do it? A tip shows you one method, a technique explores the method, advice is a suggestion on how to, a guide is a step-by-step instruction, and a hack is a change to the underlying code. Use keywords and make sure the title and opening paragraph defines the lesson to be learned clearly.</li>
<li><strong>Write It If It Fits Your Blog Purpose:</strong> As much fun as we love having with WordPress, if your blog is about sports, don&#8217;t blog a WordPress tip. Don&#8217;t disrupt your blog reader&#8217;s attention with something totally unrelated and unimportant to them. If you REALLY want to write a WordPress tip, add it to the wealth of WordPress information and resources in the <a href=\"http://codex.wordpress.org/\" rel=\"tag\" title=\"WordPress Codex - online manual for WordPress Users\">WordPress Codex</a> so everyone can enjoy it.</li>
<li><strong>Make Code Code:</strong> There is nothing more frustrating to someone who finally finds the answer they&#8217;ve been seeking on WordPress than to copy the code off the page and find out it doesn&#8217;t work because the author failed to convert the quote marks into text-based quote marks. Please, read and following the guidelines for <a href=\"http://www.blogherald.com/2007/07/16/writing-and-publishing-code-in-your-wordpress-blog-posts/\" title=\"Writing and Publishing Code in Your WordPress Blog Posts\">writing and publishing code in your WordPress Blog posts</a>.</li>
<li><strong>It&#8217;s WordPress:</strong> Help searchers find your WordPress tip by spelling it WordPress not wordpress, Wordpress, Word Press, or any of the other many variations. Do not use WP as few actually search for the initials when they are hunting for WordPress tips. It&#8217;s a Plugin not Plug-in nor plugged in. Use the keywords that name and describe what you are doing to help those searching to find your tip. The more you help them find you, the faster you&#8217;ll be the answer to their questions.</li>
<li><strong>Volunteer Your Time on the WordPress Support Forum:</strong> To really get an idea about what tips and needs WordPress users have, spend some time reading and volunteering to help on the <a href=\"http://www.wordpress.org/support\" title=\"WordPress Support Forums\" rel=\"tag\">WordPress Support Forums</a>. An hour or two a week is often enough to share your expertise with other WordPress users. The more you learn about what they are asking, and how to best respond to their needs, the better and more valuable the WordPress tips on your blog will be.</li>
</ul>
<p>They say it takes a village to raise a child. It takes a community to help make WordPress the success it is. Help us make WordPress even better by adding your tips, techniques, guides, and hacks on using WordPress to the community&#8217;s documentation collection. </p>
<h4>Related Articles</h4>
<ul>
<li><a href=\"http://lorelle.wordpress.com/2005/10/28/a-guide-to-the-wordpress-codex-the-online-manual-for-wordpress-users/\" title=\"A Guide to the WordPress Code, The Online Manual for WordPress Users\">A Guide to the WordPress Code, The Online Manual for WordPress Users</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/09/26/volunteering-on-the-wordpress-codex/\" title=\"Volunteering on the WordPress Codex\">Volunteering on the WordPress Codex</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/10/25/the-wonderful-world-of-wordpress-products/\" title=\"The Wonderful World of WordPress Products\">The Wonderful World of WordPress Products</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/12/23/give-the-gift-of-love-to-wordpress/\" title=\"Give the Gift of Love to WordPress\">Give the Gift of Love to WordPress</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/01/10/get-your-free-wordpresscom-blog-now/\" title=\"Get Your Free Wordpress.com Blog Now\">Get Your Free Wordpress.com Blog Now</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/08/30/getting-help-with-wordpresscom/\" title=\"Getting Help With wordpress.com\">Getting Help With WordPress.com</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/08/21/one-year-anniversary-review-helping-wordpresscom-users/\" title=\"Helping Wordpress.com Users\">One Year Anniversary Review: Helping WordPress.com Users</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/06/30/dont-buy-wordpress-its-free/\" title=\"Don’t Buy WordPress - It’s Free\">Don’t Buy WordPress - It’s Free</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/09/30/wordpress-help-in-your-language/\" title=\"WordPress Help in Your Language\">WordPress Help in Your Language</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/09/29/help-me-find-a-wordpress-theme/\" title=\"Help Me Find a WordPress Theme\">Help Me Find a WordPress Theme</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/08/16/first-step-to-wordpress-help-search-first/\" title=\"Search First\">First Step to WordPress Help: Search First</a></li>
</ul>
<p><img src=\"http://lorelle.files.wordpress.com/2006/08/sig.gif\" alt=\"\" /><br />
<hr />
<p><font size=\"-1\"><b>Site Search Tags:</b> <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+help\" rel=\"tag\">wordpress help</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+tips\" rel=\"tag\">wordpress tips</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+news\" rel=\"tag\">wordpress news</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+advice\" rel=\"tag\">wordpress advice</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+hack\" rel=\"tag\">wordpress hack</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+codex\" rel=\"tag\">wordpress codex</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+support+forum\" rel=\"tag\">wordpress support forum</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+support\" rel=\"tag\">wordpress support</a> <br /><a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/02/rss.png\" alt=\"Feed on Lorelle on WordPress\" /></a> <a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\">Subscribe</a>  <a href=\"http://feeds.feedburner.com/LorelleOnWordpress\" title=\"Feedburner Lorelle on WordPress Feed\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/04/feedburnericon.gif\" alt=\"Feedburner icon\" />Via Feedburner</a>  <a href=\"http://www.feedblitz.com/f/?Sub=182399\" title=\"Lorelle on WordPress - full site feed email subscription\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/03/email.gif\" alt=\"\" />Subscribe by Email</a></p>
<p><a href=\"http://lorelle.wordpress.com/about/\" title=\"Copyright Protected by Brent and Lorelle VanFossen\">Copyright Lorelle VanFossen</a>, and author of <a href=\"http://lorelle.wordpress.com/books/blogging-tips/\" title=\"Blogging Tips Book By Lorelle VanFossen\"><em>Blogging Tips, What Bloggers Won\'t Tell You About Blogging</em></a>.</font></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2285/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2285/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2285/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2285&subd=lorelle&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Wed, 02 Jan 2008 12:57:30 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:17:\"Lorelle VanFossen\";}s:7:\"summary\";s:10151:\"<div class=\"snap_preview\"><br /><p><a href=\"http://lorelle.wordpress.com/tag/wordpress-tips/\" title=\"WordPress Tips\"><img src=\"http://lorelle.files.wordpress.com/2006/11/wordpresstips.gif\" alt=\"\" align=\"right\" /></a>Do you want to write a WordPress tip? I encourage you to do so, either on your blog, on the <a href=\"http://www.wordpress.org/support\" title=\"WordPress Support Forums\" rel=\"tag\">WordPress Support Forums</a>, or for the <a href=\"http://codex.wordpress.org/\" rel=\"tag\" title=\"WordPress Codex - online manual for WordPress Users\">WordPress Codex</a>, the online manual for WordPress Users. It takes a lot of volunteer work to create a body of work for WordPress users to rely upon to help them blog better with WordPress, so all help is always welcome.</p>
<p>However, would you please do a few things for all WordPress fans everywhere first, before you publish your WordPress tips?</p>
<ul>
<li><strong>Search First:</strong> Search the web first to find other articles written on the same subject. If those are good, don&#8217;t write yours. If they can be improved upon, then write yours. If you find a lot, reconsider writing the topic and find a new one. Or find a totally new perspective on the same subject. We really need new and improved tips, not redundant.</li>
<li><strong>Write Well:</strong> Read <a href=\"http://www.blogherald.com/2007/07/09/tips-for-writing-good-wordpress-tips/\" title=\"Tips For Writing Good WordPress Tips\">Tips For Writing Good WordPress Tips</a> for tips on how to write even better WordPress tips.</li>
<li><strong>Label It Appropriately:</strong> Is it a <a href=\"http://www.blogherald.com/2007/07/10/what-is-a-tip-technique-how-to-advice-guide-and-only-way-to-do-it/\" title=\"What Is A Tip, Technique, How-To, Advice, Guide, And Only Way To Do It?\">tip, technique, how-to, advice, guide, hack</a>, or the only way to do it? A tip shows you one method, a technique explores the method, advice is a suggestion on how to, a guide is a step-by-step instruction, and a hack is a change to the underlying code. Use keywords and make sure the title and opening paragraph defines the lesson to be learned clearly.</li>
<li><strong>Write It If It Fits Your Blog Purpose:</strong> As much fun as we love having with WordPress, if your blog is about sports, don&#8217;t blog a WordPress tip. Don&#8217;t disrupt your blog reader&#8217;s attention with something totally unrelated and unimportant to them. If you REALLY want to write a WordPress tip, add it to the wealth of WordPress information and resources in the <a href=\"http://codex.wordpress.org/\" rel=\"tag\" title=\"WordPress Codex - online manual for WordPress Users\">WordPress Codex</a> so everyone can enjoy it.</li>
<li><strong>Make Code Code:</strong> There is nothing more frustrating to someone who finally finds the answer they&#8217;ve been seeking on WordPress than to copy the code off the page and find out it doesn&#8217;t work because the author failed to convert the quote marks into text-based quote marks. Please, read and following the guidelines for <a href=\"http://www.blogherald.com/2007/07/16/writing-and-publishing-code-in-your-wordpress-blog-posts/\" title=\"Writing and Publishing Code in Your WordPress Blog Posts\">writing and publishing code in your WordPress Blog posts</a>.</li>
<li><strong>It&#8217;s WordPress:</strong> Help searchers find your WordPress tip by spelling it WordPress not wordpress, Wordpress, Word Press, or any of the other many variations. Do not use WP as few actually search for the initials when they are hunting for WordPress tips. It&#8217;s a Plugin not Plug-in nor plugged in. Use the keywords that name and describe what you are doing to help those searching to find your tip. The more you help them find you, the faster you&#8217;ll be the answer to their questions.</li>
<li><strong>Volunteer Your Time on the WordPress Support Forum:</strong> To really get an idea about what tips and needs WordPress users have, spend some time reading and volunteering to help on the <a href=\"http://www.wordpress.org/support\" title=\"WordPress Support Forums\" rel=\"tag\">WordPress Support Forums</a>. An hour or two a week is often enough to share your expertise with other WordPress users. The more you learn about what they are asking, and how to best respond to their needs, the better and more valuable the WordPress tips on your blog will be.</li>
</ul>
<p>They say it takes a village to raise a child. It takes a community to help make WordPress the success it is. Help us make WordPress even better by adding your tips, techniques, guides, and hacks on using WordPress to the community&#8217;s documentation collection. </p>
<h4>Related Articles</h4>
<ul>
<li><a href=\"http://lorelle.wordpress.com/2005/10/28/a-guide-to-the-wordpress-codex-the-online-manual-for-wordpress-users/\" title=\"A Guide to the WordPress Code, The Online Manual for WordPress Users\">A Guide to the WordPress Code, The Online Manual for WordPress Users</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/09/26/volunteering-on-the-wordpress-codex/\" title=\"Volunteering on the WordPress Codex\">Volunteering on the WordPress Codex</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/10/25/the-wonderful-world-of-wordpress-products/\" title=\"The Wonderful World of WordPress Products\">The Wonderful World of WordPress Products</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/12/23/give-the-gift-of-love-to-wordpress/\" title=\"Give the Gift of Love to WordPress\">Give the Gift of Love to WordPress</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/01/10/get-your-free-wordpresscom-blog-now/\" title=\"Get Your Free Wordpress.com Blog Now\">Get Your Free Wordpress.com Blog Now</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/08/30/getting-help-with-wordpresscom/\" title=\"Getting Help With wordpress.com\">Getting Help With WordPress.com</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/08/21/one-year-anniversary-review-helping-wordpresscom-users/\" title=\"Helping Wordpress.com Users\">One Year Anniversary Review: Helping WordPress.com Users</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/06/30/dont-buy-wordpress-its-free/\" title=\"Don’t Buy WordPress - It’s Free\">Don’t Buy WordPress - It’s Free</a></li>
<li><a href=\"http://lorelle.wordpress.com/2006/09/30/wordpress-help-in-your-language/\" title=\"WordPress Help in Your Language\">WordPress Help in Your Language</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/09/29/help-me-find-a-wordpress-theme/\" title=\"Help Me Find a WordPress Theme\">Help Me Find a WordPress Theme</a></li>
<li><a href=\"http://lorelle.wordpress.com/2005/08/16/first-step-to-wordpress-help-search-first/\" title=\"Search First\">First Step to WordPress Help: Search First</a></li>
</ul>
<p><img src=\"http://lorelle.files.wordpress.com/2006/08/sig.gif\" alt=\"\" /><br />
<hr />
<p><font size=\"-1\"><b>Site Search Tags:</b> <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+help\" rel=\"tag\">wordpress help</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+tips\" rel=\"tag\">wordpress tips</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+news\" rel=\"tag\">wordpress news</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+advice\" rel=\"tag\">wordpress advice</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+hack\" rel=\"tag\">wordpress hack</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+codex\" rel=\"tag\">wordpress codex</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+support+forum\" rel=\"tag\">wordpress support forum</a>, <a href=\"http://lorelle.wordpress.com/index.php?s=wordpress+support\" rel=\"tag\">wordpress support</a> <br /><a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/02/rss.png\" alt=\"Feed on Lorelle on WordPress\" /></a> <a href=\"http://lorelle.wordpress.com/feed/\" title=\"Feed on Lorelle on WordPress\">Subscribe</a>  <a href=\"http://feeds.feedburner.com/LorelleOnWordpress\" title=\"Feedburner Lorelle on WordPress Feed\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/04/feedburnericon.gif\" alt=\"Feedburner icon\" />Via Feedburner</a>  <a href=\"http://www.feedblitz.com/f/?Sub=182399\" title=\"Lorelle on WordPress - full site feed email subscription\"><img class=\"wp-smiley\" src=\"http://lorelle.files.wordpress.com/2007/03/email.gif\" alt=\"\" />Subscribe by Email</a></p>
<p><a href=\"http://lorelle.wordpress.com/about/\" title=\"Copyright Protected by Brent and Lorelle VanFossen\">Copyright Lorelle VanFossen</a>, and author of <a href=\"http://lorelle.wordpress.com/books/blogging-tips/\" title=\"Blogging Tips Book By Lorelle VanFossen\"><em>Blogging Tips, What Bloggers Won\'t Tell You About Blogging</em></a>.</font></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2285/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2285/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2285/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2285/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2285/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2285&subd=lorelle&ref=&feed=1\" /></div>\";}i:40;a:7:{s:5:\"title\";s:75:\"Peter Westwood: WordPress weekly digest 24th December to 30th December 2007\";s:4:\"guid\";s:98:\"http://westi.wordpress.com/2008/01/02/wordpress-weekly-digest-24th-december-to-30th-december-2007/\";s:4:\"link\";s:98:\"http://westi.wordpress.com/2008/01/02/wordpress-weekly-digest-24th-december-to-30th-december-2007/\";s:11:\"description\";s:5949:\"<div class=\"snap_preview\"><br /><p>It has been a busy week again for WordPress 2.4, the changes this week were:</p>
<ul>
<li>Improvements and refactoring of the WXR importer including supporting zipped xml files (<a href=\"http://trac.wordpress.org/ticket/5522\">#5522</a>).</li>
<li>Changes to allow the salt used by WordPress in password generation and other areas to be overridden using a define (<a href=\"http://trac.wordpress.org/changeset/6478\">[6478]</a>).</li>
<li>Documentation for <code>author-template.php</code>, <code>bookmark.php</code>, <code>bookmark-template.php</code>, <code>template-loader.php</code>, <code>compat.php</code>, <code>canonical.php</code>, <code>comment-template.php</code> and file level phpdoc for some other files. (<a href=\"http://trac.wordpress.org/ticket/4393\">#4393</a>, <a href=\"http://trac.wordpress.org/ticket/5523\">#5523</a>, <a href=\"http://trac.wordpress.org/ticket/5521\">#5521</a>, <a href=\"http://trac.wordpress.org/ticket/5513\">#5513</a>, <a href=\"http://trac.wordpress.org/ticket/5510\">#5510</a>, <a href=\"http://trac.wordpress.org/ticket/5526\">#5526</a>, <a href=\"http://trac.wordpress.org/ticket/5528\">#5528</a>, and <a href=\"http://trac.wordpress.org/ticket/5527\">#5527</a> ).</li>
<li>Improved implementation of the javascript <code>addLoadEvent</code> function to speed up the execution of javascript on admin pages (<a href=\"http://trac.wordpress.org/changeset/6482\">[6482]</a>).</li>
<li>Changes to <code>wp-mail.php</code> to escape the error messages when displaying them to avoid a possible XSS attack (<a href=\"http://trac.wordpress.org/ticket/5484\">#5484</a>).</li>
<li>Changes to ensure that the post password is only exposed by the xmlrpc method <code>metaWeblog.getRecentPosts</code> to users with rights to edit a post (<a href=\"http://trac.wordpress.org/ticket/5535\">#5535</a>).</li>
<li>Changes to the information exposed the <code>wp.getAuthors</code> xmlrpc method to reduce the information exposed and add a capabilites check (<a href=\"http://trac.wordpress.org/ticket/5534\">#5534</a>).</li>
<li>Addition of extra capabilites checks to xmlrpc methods (<a href=\"http://trac.wordpress.org/changeset/6504\">[6504]</a>).</li>
<li>Addition of extra capabilites checks to APP server (<a href=\"http://trac.wordpress.org/changeset/6508\">[6508]</a>).</li>
<li>Changes to <code>validate_file()</code> to improve its traversal attempt detection when running on windows (<a href=\"http://trac.wordpress.org/changeset/6521\">[6521]</a>).</li>
<li>Changes to the magic number detection for gettext file loading for better support of 64bit systems (<a href=\"http://trac.wordpress.org/ticket/3780\">#3780</a>).</li>
<li>Fixes to the tag extraction code so as to not strip &#8217;s&#8217; from either end (<a href=\"http://trac.wordpress.org/ticket/5539\">#5539</a>).</li>
<li>Updated javascript libraries -Prototype 1.6.0 and script.aculo.us 1.8.0 (<a href=\"http://trac.wordpress.org/ticket/5543\">#5543</a>).</li>
<li>Introduction of deprecated function and file use tracking functionality to allow for theme and plugin developers to easily identify what is deprecated. (<a href=\"http://trac.wordpress.org/ticket/4361\">#4361</a>).</li>
<li>Better documentation for <code>the_author()</code> and <code>prep_atom_text_construct()</code> (<a href=\"http://trac.wordpress.org/changeset/6515\">[6515]</a>, <a href=\"http://trac.wordpress.org/changeset/6516\">[6516]</a>).</li>
<li>Final deprecation of <code>comments_rss()</code> and <code>create_user()</code> (<a href=\"http://trac.wordpress.org/changeset/6517\">[6517]</a>).</li>
<li>A change to avoid variable expansion in the invalid <code>$table_prefix</code> error message (<a href=\"http://trac.wordpress.org/ticket/5546\">#5546</a>).</li>
</ul>
<p>This week the list of changes is quite long event though a lot of time was spent on the preparation and testing of the recent <a href=\"http://wordpress.org/development/2007/12/wordpress-232/\">WordPress 2.3.2 maintenance release</a>  for which <a href=\"http://westi.wordpress.com/2007/12/30/wordpress-232-in-detail/\">you can read a detailed list of the changes here</a> - don&#8217;t forget to upgrade!</p>
<p>You can read more about the support for theme and plugin developers to help identify what deprecated functions or files they might be using in this post - <a href=\"http://blog.ftwr.co.uk/archives/2007/12/28/tracking-deprecated-functions/\">&#8220;Tracking deprecated functions&#8221;</a></p>
<p>For even more information on some of the other little changes that went in this week you can read the whole <a href=\"http://trac.wordpress.org/timeline?from=12%2F30%2F07&amp;daysback=6&amp;changeset=on\">weekly trac timeline</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/23/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/23/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/23/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=23&subd=westi&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Wed, 02 Jan 2008 08:17:00 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Peter Westwood\";}s:7:\"summary\";s:5949:\"<div class=\"snap_preview\"><br /><p>It has been a busy week again for WordPress 2.4, the changes this week were:</p>
<ul>
<li>Improvements and refactoring of the WXR importer including supporting zipped xml files (<a href=\"http://trac.wordpress.org/ticket/5522\">#5522</a>).</li>
<li>Changes to allow the salt used by WordPress in password generation and other areas to be overridden using a define (<a href=\"http://trac.wordpress.org/changeset/6478\">[6478]</a>).</li>
<li>Documentation for <code>author-template.php</code>, <code>bookmark.php</code>, <code>bookmark-template.php</code>, <code>template-loader.php</code>, <code>compat.php</code>, <code>canonical.php</code>, <code>comment-template.php</code> and file level phpdoc for some other files. (<a href=\"http://trac.wordpress.org/ticket/4393\">#4393</a>, <a href=\"http://trac.wordpress.org/ticket/5523\">#5523</a>, <a href=\"http://trac.wordpress.org/ticket/5521\">#5521</a>, <a href=\"http://trac.wordpress.org/ticket/5513\">#5513</a>, <a href=\"http://trac.wordpress.org/ticket/5510\">#5510</a>, <a href=\"http://trac.wordpress.org/ticket/5526\">#5526</a>, <a href=\"http://trac.wordpress.org/ticket/5528\">#5528</a>, and <a href=\"http://trac.wordpress.org/ticket/5527\">#5527</a> ).</li>
<li>Improved implementation of the javascript <code>addLoadEvent</code> function to speed up the execution of javascript on admin pages (<a href=\"http://trac.wordpress.org/changeset/6482\">[6482]</a>).</li>
<li>Changes to <code>wp-mail.php</code> to escape the error messages when displaying them to avoid a possible XSS attack (<a href=\"http://trac.wordpress.org/ticket/5484\">#5484</a>).</li>
<li>Changes to ensure that the post password is only exposed by the xmlrpc method <code>metaWeblog.getRecentPosts</code> to users with rights to edit a post (<a href=\"http://trac.wordpress.org/ticket/5535\">#5535</a>).</li>
<li>Changes to the information exposed the <code>wp.getAuthors</code> xmlrpc method to reduce the information exposed and add a capabilites check (<a href=\"http://trac.wordpress.org/ticket/5534\">#5534</a>).</li>
<li>Addition of extra capabilites checks to xmlrpc methods (<a href=\"http://trac.wordpress.org/changeset/6504\">[6504]</a>).</li>
<li>Addition of extra capabilites checks to APP server (<a href=\"http://trac.wordpress.org/changeset/6508\">[6508]</a>).</li>
<li>Changes to <code>validate_file()</code> to improve its traversal attempt detection when running on windows (<a href=\"http://trac.wordpress.org/changeset/6521\">[6521]</a>).</li>
<li>Changes to the magic number detection for gettext file loading for better support of 64bit systems (<a href=\"http://trac.wordpress.org/ticket/3780\">#3780</a>).</li>
<li>Fixes to the tag extraction code so as to not strip &#8217;s&#8217; from either end (<a href=\"http://trac.wordpress.org/ticket/5539\">#5539</a>).</li>
<li>Updated javascript libraries -Prototype 1.6.0 and script.aculo.us 1.8.0 (<a href=\"http://trac.wordpress.org/ticket/5543\">#5543</a>).</li>
<li>Introduction of deprecated function and file use tracking functionality to allow for theme and plugin developers to easily identify what is deprecated. (<a href=\"http://trac.wordpress.org/ticket/4361\">#4361</a>).</li>
<li>Better documentation for <code>the_author()</code> and <code>prep_atom_text_construct()</code> (<a href=\"http://trac.wordpress.org/changeset/6515\">[6515]</a>, <a href=\"http://trac.wordpress.org/changeset/6516\">[6516]</a>).</li>
<li>Final deprecation of <code>comments_rss()</code> and <code>create_user()</code> (<a href=\"http://trac.wordpress.org/changeset/6517\">[6517]</a>).</li>
<li>A change to avoid variable expansion in the invalid <code>$table_prefix</code> error message (<a href=\"http://trac.wordpress.org/ticket/5546\">#5546</a>).</li>
</ul>
<p>This week the list of changes is quite long event though a lot of time was spent on the preparation and testing of the recent <a href=\"http://wordpress.org/development/2007/12/wordpress-232/\">WordPress 2.3.2 maintenance release</a>  for which <a href=\"http://westi.wordpress.com/2007/12/30/wordpress-232-in-detail/\">you can read a detailed list of the changes here</a> - don&#8217;t forget to upgrade!</p>
<p>You can read more about the support for theme and plugin developers to help identify what deprecated functions or files they might be using in this post - <a href=\"http://blog.ftwr.co.uk/archives/2007/12/28/tracking-deprecated-functions/\">&#8220;Tracking deprecated functions&#8221;</a></p>
<p>For even more information on some of the other little changes that went in this week you can read the whole <a href=\"http://trac.wordpress.org/timeline?from=12%2F30%2F07&amp;daysback=6&amp;changeset=on\">weekly trac timeline</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/23/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/23/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/23/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/23/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/23/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=23&subd=westi&ref=&feed=1\" /></div>\";}i:41;a:7:{s:5:\"title\";s:23:\"Matt: Misery, Happiness\";s:4:\"guid\";s:49:\"http://photomatt.net/2008/01/01/misery-happiness/\";s:4:\"link\";s:49:\"http://photomatt.net/2008/01/01/misery-happiness/\";s:11:\"description\";s:255:\"<p><a href=\"http://news.bbc.co.uk/2/hi/health/6711071.stm\">Misery: the secret to happiness</a>. Found via <a href=\"http://www.bbc.co.uk/blogs/magazinemonitor/2008/01/100_things_we_didnt_know_last_3.shtml\">100 things we didn&#8217;t know last year</a>.</p>\";s:7:\"pubdate\";s:31:\"Wed, 02 Jan 2008 05:06:10 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:255:\"<p><a href=\"http://news.bbc.co.uk/2/hi/health/6711071.stm\">Misery: the secret to happiness</a>. Found via <a href=\"http://www.bbc.co.uk/blogs/magazinemonitor/2008/01/100_things_we_didnt_know_last_3.shtml\">100 things we didn&#8217;t know last year</a>.</p>\";}i:42;a:7:{s:5:\"title\";s:46:\"Weblog Tools Collection: SimplePie Almost Dies\";s:4:\"guid\";s:75:\"http://weblogtoolscollection.com/archives/2008/01/01/simplepie-almost-dies/\";s:4:\"link\";s:75:\"http://weblogtoolscollection.com/archives/2008/01/01/simplepie-almost-dies/\";s:11:\"description\";s:2555:\"<p><a href=\"http://gsnedders.com/\" title=\"http://gsnedders.com/\" target=\"_blank\">Geoffrey Sneddon</a>, one of the developers behind the popular syndication plugin called SimplePie has announced that he will be discontinuing his role as an active developer. In a blog post published on the official <a href=\"http://simplepie.org/blog/2007/12/28/byepie/\">SimplePie dev blog </a>, Geoffrey explains why it&#8217;s time for him to move on. Schoolwork, lack of available time for the project and what free time he has is spent on the HTML 5 specification and Tolerant HTTP Parsing specification. However, a couple of the modules that deal with the SimplePie API will be maintained.</p>
<p>Despite Geoffrey leaving his development duties, he has left himself open to take more of a consulting role with the 1.x SP code base.</p>
<p>The good news? Ryan, the other developer for SimplePie has responded by stating:</p>
<blockquote><p>1) SimplePie is NOT stopping development. I have big plans for where I want to take SimplePie, and those can’t happen if SimplePie is dead. In posts over the past few months, I’ve talked about where I want SimplePie to go, and that is still the plan, although it may take a little longer.</p>
<p>2) Over the past 3.5 years, SimplePie and it’s community have grown larger than Geoffrey and I could properly handle. It’s certainly larger than I alone can handle. Geoffrey and I will be looking for people in the SimplePie community to get involved with development, support, and other various aspects of the project.</p>
<p>3) I’m expecting to release SimplePie 1.1 in a matter of days. We also have a MySQL-capable branch that was likely to be 1.2, and will now definitely be 1.2. SimplePie 1.5/2.0 are no longer on any kind of timeline, as we need to get new people involved and up to speed first before we really plan those releases out.</p>
<p>As soon Geoffrey and I have time to work out more of the details, we’ll be sure to let you know.</p></blockquote>
<p>I currently use the <strong><a href=\"http://simplepie.org/wiki/plugins/wordpress/simplepie_plugin_for_wordpress\" title=\"Visit plugin homepage\">SimplePie Plugin for WordPress</a> </strong> which provides WordPress bloggers the ability to syndicate RSS and Atom feeds to your blog. It works wonderfully well and is the plugin that powers my link blog. I really hope development continues for SimplePie as it would be a real downer if the project were to disappear.</p>
<p>Do you use SimplePie? If so, be sure to let me know your thoughts on the plugin.</p>\";s:7:\"pubdate\";s:31:\"Tue, 01 Jan 2008 15:00:06 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jeffro2pt0\";}s:7:\"summary\";s:2555:\"<p><a href=\"http://gsnedders.com/\" title=\"http://gsnedders.com/\" target=\"_blank\">Geoffrey Sneddon</a>, one of the developers behind the popular syndication plugin called SimplePie has announced that he will be discontinuing his role as an active developer. In a blog post published on the official <a href=\"http://simplepie.org/blog/2007/12/28/byepie/\">SimplePie dev blog </a>, Geoffrey explains why it&#8217;s time for him to move on. Schoolwork, lack of available time for the project and what free time he has is spent on the HTML 5 specification and Tolerant HTTP Parsing specification. However, a couple of the modules that deal with the SimplePie API will be maintained.</p>
<p>Despite Geoffrey leaving his development duties, he has left himself open to take more of a consulting role with the 1.x SP code base.</p>
<p>The good news? Ryan, the other developer for SimplePie has responded by stating:</p>
<blockquote><p>1) SimplePie is NOT stopping development. I have big plans for where I want to take SimplePie, and those can’t happen if SimplePie is dead. In posts over the past few months, I’ve talked about where I want SimplePie to go, and that is still the plan, although it may take a little longer.</p>
<p>2) Over the past 3.5 years, SimplePie and it’s community have grown larger than Geoffrey and I could properly handle. It’s certainly larger than I alone can handle. Geoffrey and I will be looking for people in the SimplePie community to get involved with development, support, and other various aspects of the project.</p>
<p>3) I’m expecting to release SimplePie 1.1 in a matter of days. We also have a MySQL-capable branch that was likely to be 1.2, and will now definitely be 1.2. SimplePie 1.5/2.0 are no longer on any kind of timeline, as we need to get new people involved and up to speed first before we really plan those releases out.</p>
<p>As soon Geoffrey and I have time to work out more of the details, we’ll be sure to let you know.</p></blockquote>
<p>I currently use the <strong><a href=\"http://simplepie.org/wiki/plugins/wordpress/simplepie_plugin_for_wordpress\" title=\"Visit plugin homepage\">SimplePie Plugin for WordPress</a> </strong> which provides WordPress bloggers the ability to syndicate RSS and Atom feeds to your blog. It works wonderfully well and is the plugin that powers my link blog. I really hope development continues for SimplePie as it would be a real downer if the project were to disappear.</p>
<p>Do you use SimplePie? If so, be sure to let me know your thoughts on the plugin.</p>\";}i:43;a:7:{s:5:\"title\";s:25:\"Matt: Hoosgot Lazyweb 2.0\";s:4:\"guid\";s:51:\"http://photomatt.net/2007/12/31/hoosgot-lazyweb-20/\";s:4:\"link\";s:51:\"http://photomatt.net/2007/12/31/hoosgot-lazyweb-20/\";s:11:\"description\";s:136:\"<p><a href=\"http://www.sifry.com/alerts/archives/2007/12/announcing_hoos.html\">Hoosgot: Resurrecting the Lazyweb</a>. <em>Cool!</em></p>\";s:7:\"pubdate\";s:31:\"Mon, 31 Dec 2007 20:11:07 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:136:\"<p><a href=\"http://www.sifry.com/alerts/archives/2007/12/announcing_hoos.html\">Hoosgot: Resurrecting the Lazyweb</a>. <em>Cool!</em></p>\";}i:44;a:7:{s:5:\"title\";s:29:\"Gravatar: Gravatars on Rails!\";s:4:\"guid\";s:55:\"http://blog.gravatar.com/2007/12/31/gravatars-on-rails/\";s:4:\"link\";s:55:\"http://blog.gravatar.com/2007/12/31/gravatars-on-rails/\";s:11:\"description\";s:1729:\"<div class=\"snap_preview\"><br /><p>Mike wrote in with a link to one of his blog posts describing <a href=\"http://overhrd.com/?p=28\">how he integrated gravatars into one of his Ruby on Rails projects</a>.  As always we appreciate the community coming together to fill in the gaps, and help each other.  The blogging community can sometimes be a truly inspiring example of generosity and thoughtfulness!  Thanks Mike!</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/gravatar.wordpress.com/40/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/gravatar.wordpress.com/40/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/gravatar.wordpress.com/40/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=blog.gravatar.com&blog=1886259&post=40&subd=gravatar&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Mon, 31 Dec 2007 18:21:05 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:11:\"apokalyptik\";}s:7:\"summary\";s:1729:\"<div class=\"snap_preview\"><br /><p>Mike wrote in with a link to one of his blog posts describing <a href=\"http://overhrd.com/?p=28\">how he integrated gravatars into one of his Ruby on Rails projects</a>.  As always we appreciate the community coming together to fill in the gaps, and help each other.  The blogging community can sometimes be a truly inspiring example of generosity and thoughtfulness!  Thanks Mike!</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/gravatar.wordpress.com/40/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/gravatar.wordpress.com/40/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/gravatar.wordpress.com/40/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/gravatar.wordpress.com/40/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/gravatar.wordpress.com/40/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=blog.gravatar.com&blog=1886259&post=40&subd=gravatar&ref=&feed=1\" /></div>\";}i:45;a:7:{s:5:\"title\";s:84:\"Lorelle on WP: Adding Avatars and Gravatars to Your WordPress and WordPress.com Blog\";s:4:\"guid\";s:109:\"http://lorelle.wordpress.com/2007/12/31/adding-avatars-and-gravatars-to-your-wordpress-and-wordpresscom-blog/\";s:4:\"link\";s:109:\"http://lorelle.wordpress.com/2007/12/31/adding-avatars-and-gravatars-to-your-wordpress-and-wordpresscom-blog/\";s:11:\"description\";s:4502:\"<div class=\"snap_preview\"><br /><p><a href=\"http://lorelle.wordpress.com/tag/wordpress-tips/\" title=\"WordPress Tips\"><img src=\"http://lorelle.files.wordpress.com/2006/11/wordpresstips.gif\" alt=\"\" align=\"right\" /></a>Avatars, or the well known <a href=\"http://gravatar.com/\" title=\"Gravatar\">Gravatars</a>, are tiny images, often called your <em>online identity</em>, picture, badge, logo, or graphic image which represent you and/or your blog. Some use photographs of their face or body, or a body part like an eye, nose, or hand. Others use pictures of animals, flowers, scenics, or graphic images. Many professional bloggers use their logo.</p>
<p>Many people like to see these graphic representatives of their blog next to their comments, or now, with the new <a href=\"http://wordpress.com/blog/2007/12/21/avatars-in-dashboard/\" title=\"Avatars in Dashboard\">addition of avatars and Gravatars to WordPress.com</a>, in their WordPress Administration Dashboard listing of the top posts, My Comments comment follow panel, and on the Comments Panel, as well as within the comments of many WordPress Themes.</p>
<h3>Adding Gravatars to WordPress and WordPress.com Blogs</h3>
<p>When <a href=\"http://blog.gravatar.com/2007/10/18/automattic-gravatar/\" title=\"Automattic Gravatar\">Automattic bought Gravatar</a>, they updated the infrastructure to speed things up and updated the <a href=\"http://site.gravatar.com/site/implement#section_2_2\" title=\"Gravatar already provides a simple WordPress plugin\">Gravatar WordPress Plugin</a>. </p>
<p>Then <a href=\"http://wordpress.com/blog/2007/12/06/gravatars-everywhere/\" title=\"Gravatars Everywhere\">Gravatars support was enabled for all WordPress.com users</a>. Those with a Gravatar attached to their email will see their Gravatar image appearing on all WordPress.com blogs, as soon as they finish enabling all WordPress.com Themes.</p>
<p><img src=\"http://lorelle.files.wordpress.com/2007/12/avatarwordpresscom.png\" alt=\"WordPress.com User, Your Profile Panel Avatar upload\" align=\"right\" /><a href=\"http://www.wordpress.com/\" title=\"WordPress.com\" rel=\"tag\">WordPress.com</a> bloggers can add an avatar image to their blog by going to the <strong>Users &gt; Your Profile</strong> panel. In a box currently on the left side is where to upload your image. The image should be <em>no bigger than 128 pixels</em>, though 80 pixels square is the standard. The image must withstand &#8220;shrinkage&#8221; down to 16 pixels, the size that appears on the Administration Panels Dashboard. </p>
<p>If you would like to add Gravatars to your blog, begin by registering a Gravatar image on the <a href=\"http://gravatar.com/\" title=\"Gravatar\">Gravatars</a> site by <a href=\"http://site.gravatar.com/signup\" title=\"Signup\">signing up</a> and submitting an image. Then follow the <a href=\"http://site.gravatar.com/site/implement\" title=\"Gravatar Implementation Documentation\">user&#8217;s guide</a> which includes how to enable Gravatars on your blogging platform or program.<br />
 <a href=\"http://lorelle.wordpress.com/2007/12/31/adding-avatars-and-gravatars-to-your-wordpress-and-wordpresscom-blog/#more-2263\" class=\"more-link\">(more&#8230;)</a></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2263/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2263/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2263/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2263&subd=lorelle&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Mon, 31 Dec 2007 11:27:36 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:17:\"Lorelle VanFossen\";}s:7:\"summary\";s:4502:\"<div class=\"snap_preview\"><br /><p><a href=\"http://lorelle.wordpress.com/tag/wordpress-tips/\" title=\"WordPress Tips\"><img src=\"http://lorelle.files.wordpress.com/2006/11/wordpresstips.gif\" alt=\"\" align=\"right\" /></a>Avatars, or the well known <a href=\"http://gravatar.com/\" title=\"Gravatar\">Gravatars</a>, are tiny images, often called your <em>online identity</em>, picture, badge, logo, or graphic image which represent you and/or your blog. Some use photographs of their face or body, or a body part like an eye, nose, or hand. Others use pictures of animals, flowers, scenics, or graphic images. Many professional bloggers use their logo.</p>
<p>Many people like to see these graphic representatives of their blog next to their comments, or now, with the new <a href=\"http://wordpress.com/blog/2007/12/21/avatars-in-dashboard/\" title=\"Avatars in Dashboard\">addition of avatars and Gravatars to WordPress.com</a>, in their WordPress Administration Dashboard listing of the top posts, My Comments comment follow panel, and on the Comments Panel, as well as within the comments of many WordPress Themes.</p>
<h3>Adding Gravatars to WordPress and WordPress.com Blogs</h3>
<p>When <a href=\"http://blog.gravatar.com/2007/10/18/automattic-gravatar/\" title=\"Automattic Gravatar\">Automattic bought Gravatar</a>, they updated the infrastructure to speed things up and updated the <a href=\"http://site.gravatar.com/site/implement#section_2_2\" title=\"Gravatar already provides a simple WordPress plugin\">Gravatar WordPress Plugin</a>. </p>
<p>Then <a href=\"http://wordpress.com/blog/2007/12/06/gravatars-everywhere/\" title=\"Gravatars Everywhere\">Gravatars support was enabled for all WordPress.com users</a>. Those with a Gravatar attached to their email will see their Gravatar image appearing on all WordPress.com blogs, as soon as they finish enabling all WordPress.com Themes.</p>
<p><img src=\"http://lorelle.files.wordpress.com/2007/12/avatarwordpresscom.png\" alt=\"WordPress.com User, Your Profile Panel Avatar upload\" align=\"right\" /><a href=\"http://www.wordpress.com/\" title=\"WordPress.com\" rel=\"tag\">WordPress.com</a> bloggers can add an avatar image to their blog by going to the <strong>Users &gt; Your Profile</strong> panel. In a box currently on the left side is where to upload your image. The image should be <em>no bigger than 128 pixels</em>, though 80 pixels square is the standard. The image must withstand &#8220;shrinkage&#8221; down to 16 pixels, the size that appears on the Administration Panels Dashboard. </p>
<p>If you would like to add Gravatars to your blog, begin by registering a Gravatar image on the <a href=\"http://gravatar.com/\" title=\"Gravatar\">Gravatars</a> site by <a href=\"http://site.gravatar.com/signup\" title=\"Signup\">signing up</a> and submitting an image. Then follow the <a href=\"http://site.gravatar.com/site/implement\" title=\"Gravatar Implementation Documentation\">user&#8217;s guide</a> which includes how to enable Gravatars on your blogging platform or program.<br />
 <a href=\"http://lorelle.wordpress.com/2007/12/31/adding-avatars-and-gravatars-to-your-wordpress-and-wordpresscom-blog/#more-2263\" class=\"more-link\">(more&#8230;)</a></p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/lorelle.wordpress.com/2263/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/lorelle.wordpress.com/2263/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/lorelle.wordpress.com/2263/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/lorelle.wordpress.com/2263/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/lorelle.wordpress.com/2263/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=lorelle.wordpress.com&blog=72&post=2263&subd=lorelle&ref=&feed=1\" /></div>\";}i:46;a:7:{s:5:\"title\";s:57:\"Weblog Tools Collection: Install WordPress Locally 1 Of 2\";s:4:\"guid\";s:86:\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\";s:4:\"link\";s:86:\"http://weblogtoolscollection.com/archives/2007/12/30/install-wordpress-locally-1-of-2/\";s:11:\"description\";s:5631:\"<p><img src=\"http://weblogtoolscollection.com/b2-img/2007/12/wampserverlogo.png\" alt=\"Wamp Server Logo\" /></p>
<p>Welcome to part one of a two part series of articles that will guide you through the process of installing a fresh copy of WordPress or your public WordPress blog to your local machine. The first part of this series will guide you through the installation and configuration of a piece of software called WampServer. Why would you want to do this you ask? Having your WordPress blog installed on your local machine not only acts as a backup, but it gives you the option of really digging into the inner workings of your blog without having to worry about it breaking and therefor, rendering the thing useless to the public. Not only that, but it&#8217;s much faster to play with things on your local machine than it is with a LIVE site on the internet.</p>
<p>For this article, I am using <strong>Windows XP Service Pack 2 </strong>and something called <strong>WampServer</strong>. WampServer is a piece of software that installs everything you need to turn your PC into a webserver. This includes <strong>Apache, MySQL, PHP, SQLitemanager and PHPMyAdmin.</strong> Before we get started, head on over to the official <a href=\"http://www.wampserver.com/en/download.php\" title=\"http://www.wampserver.com/en/download.php\" target=\"_blank\">WampServer download</a> page and grab a copy of WampServer 2.</p>
<h2>WampServer Installation:</h2>
<p>The installation process is pretty simple. After accepting the license agreement and specifying where the WampServer files will be installed to, the installation file will be unpacked, doing all of the heavy work for you. Using a software application such as WampServer to install all of your webserver needs for you automatically, is the easiest way to turn your machine, into a web server. Once the installation is finished, you&#8217;ll be prompted to locate your default browser executable file. In my case, I had to direct the install to my FireFox executable file which is usually within the Mozilla folder.</p>
<p>One of the first things you&#8217;ll have to configure is the PHP mail parameters. For <strong>SMTP</strong>, the default value of localhost is correct. As for the email address, you can choose to type one in, or not. This can always be changed later. Once this setting is configured, you&#8217;ll be greeted with a confirmation box that tells you the installation of WampServer has been completed. Leave the option &#8220;<strong>Launch WampServer 2 now</strong>&#8221; check marked and click the finish button.</p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2007/12/installcomplete.png\" alt=\"Installation Is Completed\" /></p>
<h2>Configuring WampServer Files:</h2>
<p>One important piece of information I have to mention. The webserver acts on port 80 which is the port responsible for HTTP traffic. If you are running Skype with it&#8217;s default configuration, you&#8217;ll notice that your Webserver is offline once you start the program. This is because by default, Skype uses port <strong>80 and 443</strong> for incoming connections. You can either change the port that Skype uses or you can close, then re open Skype after your Webserver is online, forcing Skype to use a different port. In essence, make sure port 80 is clear before you launch WampServer or else the Apache web service will not run.</p>
<p>I&#8217;ve also been informed by <strong>ayusli</strong> that will you also need to disable IIS if that is running on your system. If you don&#8217;t, you may not be able to access localhost.</p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2007/12/phpinifile.png\" alt=\"Accessing PHP.ini\" /></p>
<p>Once your WampServer is online, you&#8217;ll need to edit a few files to change the configuration to allow for larger databases to be imported. These changes will take place within the PHP.ini file. The PHP.ini file is a text file that contains the configuration for the PHP programming language. The first thing you&#8217;ll need to change is the <strong>upload_max_filesize </strong>attribute. By default, this is set to 2Megabytes. This is too small of a value, so increase this to 50 or 100megs. It doesn&#8217;t need to have a specific value so long as it is larger than the size of the database file you will be importing later on in this guide. The other setting you&#8217;ll need to change is <strong>post_max_size</strong>. By default this is set to 8Megabytes. Change this to the same value as the upload_max_filesize limit. After you make this change, left click on the WampServer icon and restart all of the services. This will ensure the changes you made to the php.ini file take effect.</p>
<h2>End Of Part 1:</h2>
<p>If you plan on doing a fresh install of WordPress, you won&#8217;t have to worry about making any changes to the PHP.ini file after you install WampServer. However, if you plan on taking a copy of your public blog and transferring it to your local machine, the changes described above need to happen or else you will likely run into problems such as your database file being too large to import.</p>
<p>Part 2 of this series will go into details on how to install a fresh copy of WordPress as well as how to transfer your existing WordPress blog on the internet onto your local machine. It&#8217;s not as easy as transferring the database and then extracting a backup of files into a folder. There are a few more required tricks that need to be performed before a public blog can be successfully transferred. Look for these tips in part two which should be published in the next few days.</p>\";s:7:\"pubdate\";s:31:\"Sun, 30 Dec 2007 16:15:05 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:10:\"Jeffro2pt0\";}s:7:\"summary\";s:5631:\"<p><img src=\"http://weblogtoolscollection.com/b2-img/2007/12/wampserverlogo.png\" alt=\"Wamp Server Logo\" /></p>
<p>Welcome to part one of a two part series of articles that will guide you through the process of installing a fresh copy of WordPress or your public WordPress blog to your local machine. The first part of this series will guide you through the installation and configuration of a piece of software called WampServer. Why would you want to do this you ask? Having your WordPress blog installed on your local machine not only acts as a backup, but it gives you the option of really digging into the inner workings of your blog without having to worry about it breaking and therefor, rendering the thing useless to the public. Not only that, but it&#8217;s much faster to play with things on your local machine than it is with a LIVE site on the internet.</p>
<p>For this article, I am using <strong>Windows XP Service Pack 2 </strong>and something called <strong>WampServer</strong>. WampServer is a piece of software that installs everything you need to turn your PC into a webserver. This includes <strong>Apache, MySQL, PHP, SQLitemanager and PHPMyAdmin.</strong> Before we get started, head on over to the official <a href=\"http://www.wampserver.com/en/download.php\" title=\"http://www.wampserver.com/en/download.php\" target=\"_blank\">WampServer download</a> page and grab a copy of WampServer 2.</p>
<h2>WampServer Installation:</h2>
<p>The installation process is pretty simple. After accepting the license agreement and specifying where the WampServer files will be installed to, the installation file will be unpacked, doing all of the heavy work for you. Using a software application such as WampServer to install all of your webserver needs for you automatically, is the easiest way to turn your machine, into a web server. Once the installation is finished, you&#8217;ll be prompted to locate your default browser executable file. In my case, I had to direct the install to my FireFox executable file which is usually within the Mozilla folder.</p>
<p>One of the first things you&#8217;ll have to configure is the PHP mail parameters. For <strong>SMTP</strong>, the default value of localhost is correct. As for the email address, you can choose to type one in, or not. This can always be changed later. Once this setting is configured, you&#8217;ll be greeted with a confirmation box that tells you the installation of WampServer has been completed. Leave the option &#8220;<strong>Launch WampServer 2 now</strong>&#8221; check marked and click the finish button.</p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2007/12/installcomplete.png\" alt=\"Installation Is Completed\" /></p>
<h2>Configuring WampServer Files:</h2>
<p>One important piece of information I have to mention. The webserver acts on port 80 which is the port responsible for HTTP traffic. If you are running Skype with it&#8217;s default configuration, you&#8217;ll notice that your Webserver is offline once you start the program. This is because by default, Skype uses port <strong>80 and 443</strong> for incoming connections. You can either change the port that Skype uses or you can close, then re open Skype after your Webserver is online, forcing Skype to use a different port. In essence, make sure port 80 is clear before you launch WampServer or else the Apache web service will not run.</p>
<p>I&#8217;ve also been informed by <strong>ayusli</strong> that will you also need to disable IIS if that is running on your system. If you don&#8217;t, you may not be able to access localhost.</p>
<p><img src=\"http://weblogtoolscollection.com/b2-img/2007/12/phpinifile.png\" alt=\"Accessing PHP.ini\" /></p>
<p>Once your WampServer is online, you&#8217;ll need to edit a few files to change the configuration to allow for larger databases to be imported. These changes will take place within the PHP.ini file. The PHP.ini file is a text file that contains the configuration for the PHP programming language. The first thing you&#8217;ll need to change is the <strong>upload_max_filesize </strong>attribute. By default, this is set to 2Megabytes. This is too small of a value, so increase this to 50 or 100megs. It doesn&#8217;t need to have a specific value so long as it is larger than the size of the database file you will be importing later on in this guide. The other setting you&#8217;ll need to change is <strong>post_max_size</strong>. By default this is set to 8Megabytes. Change this to the same value as the upload_max_filesize limit. After you make this change, left click on the WampServer icon and restart all of the services. This will ensure the changes you made to the php.ini file take effect.</p>
<h2>End Of Part 1:</h2>
<p>If you plan on doing a fresh install of WordPress, you won&#8217;t have to worry about making any changes to the PHP.ini file after you install WampServer. However, if you plan on taking a copy of your public blog and transferring it to your local machine, the changes described above need to happen or else you will likely run into problems such as your database file being too large to import.</p>
<p>Part 2 of this series will go into details on how to install a fresh copy of WordPress as well as how to transfer your existing WordPress blog on the internet onto your local machine. It&#8217;s not as easy as transferring the database and then extracting a backup of files into a folder. There are a few more required tricks that need to be performed before a public blog can be successfully transferred. Look for these tips in part two which should be published in the next few days.</p>\";}i:47;a:7:{s:5:\"title\";s:12:\"Matt: Notcot\";s:4:\"guid\";s:39:\"http://photomatt.net/2007/12/30/notcot/\";s:4:\"link\";s:39:\"http://photomatt.net/2007/12/30/notcot/\";s:11:\"description\";s:185:\"<p>The Notcot group of sites, like <a href=\"http://www.notcot.org/\">NOTCOT.ORG</a>, display information in an interesting way. Very compelling and well done. Not new, but new to me.</p>\";s:7:\"pubdate\";s:31:\"Sun, 30 Dec 2007 08:22:31 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:185:\"<p>The Notcot group of sites, like <a href=\"http://www.notcot.org/\">NOTCOT.ORG</a>, display information in an interesting way. Very compelling and well done. Not new, but new to me.</p>\";}i:48;a:7:{s:5:\"title\";s:41:\"Peter Westwood: WordPress 2.3.2 in detail\";s:4:\"guid\";s:62:\"http://westi.wordpress.com/2007/12/30/wordpress-232-in-detail/\";s:4:\"link\";s:62:\"http://westi.wordpress.com/2007/12/30/wordpress-232-in-detail/\";s:11:\"description\";s:3960:\"<div class=\"snap_preview\"><br /><p><a href=\"http://wordpress.org/development/2007/12/wordpress-232/\">WordPress 2.3.2 has been released</a> and includes a number of changes including one security fix, here is a list of most of the changes in detail:</p>
<ul>
<li>Performance improvements for post sanitization when raw content is required (<a href=\"http://trac.wordpress.org/ticket/5325\">#5325</a>).</li>
<li>Changes to <code>is_admin()</code> to ensure that it is only true for admin pages thereby protecting against exposing draft posts. (<a href=\"http://trac.wordpress.org/ticket/5487\">#5487</a>).</li>
<li>Suppression of database errors unless <a href=\"http://westi.wordpress.com/2007/09/30/wordpress-weekly-digest-24th-september-to-30th-september-2007/\">WP_DEBUG</a> is true (<a href=\"http://trac.wordpress.org/ticket/5473\">#5473</a>).</li>
<li>Check for valid database connection information during install and display and error if the install fails due to database rights (<a href=\"http://trac.wordpress.org/ticket/5495\">#5495</a>).</li>
<li>Support for a custom database down page to be displayed on database connection errors (<a href=\"http://trac.wordpress.org/ticket/5500\">#5500</a>).</li>
<li>Changes to make sure we are more selective in what we make clickable, this introduces different rules for different uri types (<a href=\"http://trac.wordpress.org/changeset/6450\">[6450]</a>).</li>
<li>Changes to <code>wp-mail.php</code> to escape the error messages when displaying them to avoid a possible XSS attack (<a href=\"http://trac.wordpress.org/ticket/5484\">#5484</a>).</li>
<li>Changes to ensure that the post password is only exposed by the xmlrpc method <code>metaWeblog.getRecentPosts</code> to users with rights to edit a post (<a href=\"http://trac.wordpress.org/ticket/5535\">#5535</a>).</li>
<li>Changes to the information exposed the <code>wp.getAuthors</code> xmlrpc method to reduce the information exposed and add a capabilites check (<a href=\"http://trac.wordpress.org/ticket/5534\">#5534</a>).</li>
<li>Addition of extra capabilites checks to xmlrpc methods (<a href=\"http://trac.wordpress.org/changeset/6504\">[6504]</a>).</li>
<li>Addition of extra capabilites checks to APP server (<a href=\"http://trac.wordpress.org/changeset/6508\">[6508]</a>).</li>
<li>Changes to <code>validate_file()</code> to improve its traversal attempt detection when running on windows (<a href=\"http://trac.wordpress.org/changeset/6521\">[6521]</a>).</li>
</ul>
<p>For a complete list of all the changes you can read this section of the <a href=\"http://trac.wordpress.org/log/branches/2.3?action=stop_on_copy&amp;rev=6527&amp;stop_rev=6322&amp;mode=stop_on_copy\">branches/2.3 log</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/22/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/22/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/22/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=22&subd=westi&ref=&feed=1\" /></div>\";s:7:\"pubdate\";s:31:\"Sun, 30 Dec 2007 08:09:12 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:14:\"Peter Westwood\";}s:7:\"summary\";s:3960:\"<div class=\"snap_preview\"><br /><p><a href=\"http://wordpress.org/development/2007/12/wordpress-232/\">WordPress 2.3.2 has been released</a> and includes a number of changes including one security fix, here is a list of most of the changes in detail:</p>
<ul>
<li>Performance improvements for post sanitization when raw content is required (<a href=\"http://trac.wordpress.org/ticket/5325\">#5325</a>).</li>
<li>Changes to <code>is_admin()</code> to ensure that it is only true for admin pages thereby protecting against exposing draft posts. (<a href=\"http://trac.wordpress.org/ticket/5487\">#5487</a>).</li>
<li>Suppression of database errors unless <a href=\"http://westi.wordpress.com/2007/09/30/wordpress-weekly-digest-24th-september-to-30th-september-2007/\">WP_DEBUG</a> is true (<a href=\"http://trac.wordpress.org/ticket/5473\">#5473</a>).</li>
<li>Check for valid database connection information during install and display and error if the install fails due to database rights (<a href=\"http://trac.wordpress.org/ticket/5495\">#5495</a>).</li>
<li>Support for a custom database down page to be displayed on database connection errors (<a href=\"http://trac.wordpress.org/ticket/5500\">#5500</a>).</li>
<li>Changes to make sure we are more selective in what we make clickable, this introduces different rules for different uri types (<a href=\"http://trac.wordpress.org/changeset/6450\">[6450]</a>).</li>
<li>Changes to <code>wp-mail.php</code> to escape the error messages when displaying them to avoid a possible XSS attack (<a href=\"http://trac.wordpress.org/ticket/5484\">#5484</a>).</li>
<li>Changes to ensure that the post password is only exposed by the xmlrpc method <code>metaWeblog.getRecentPosts</code> to users with rights to edit a post (<a href=\"http://trac.wordpress.org/ticket/5535\">#5535</a>).</li>
<li>Changes to the information exposed the <code>wp.getAuthors</code> xmlrpc method to reduce the information exposed and add a capabilites check (<a href=\"http://trac.wordpress.org/ticket/5534\">#5534</a>).</li>
<li>Addition of extra capabilites checks to xmlrpc methods (<a href=\"http://trac.wordpress.org/changeset/6504\">[6504]</a>).</li>
<li>Addition of extra capabilites checks to APP server (<a href=\"http://trac.wordpress.org/changeset/6508\">[6508]</a>).</li>
<li>Changes to <code>validate_file()</code> to improve its traversal attempt detection when running on windows (<a href=\"http://trac.wordpress.org/changeset/6521\">[6521]</a>).</li>
</ul>
<p>For a complete list of all the changes you can read this section of the <a href=\"http://trac.wordpress.org/log/branches/2.3?action=stop_on_copy&amp;rev=6527&amp;stop_rev=6322&amp;mode=stop_on_copy\">branches/2.3 log</a>.</p>
<img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/categories/westi.wordpress.com/22/\" /> <img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/tags/westi.wordpress.com/22/\" /> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gocomments/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/comments/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godelicious/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/delicious/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/gostumble/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/stumble/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/godigg/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/digg/westi.wordpress.com/22/\" /></a> <a rel=\"nofollow\" href=\"http://feeds.wordpress.com/1.0/goreddit/westi.wordpress.com/22/\"><img alt=\"\" border=\"0\" src=\"http://feeds.wordpress.com/1.0/reddit/westi.wordpress.com/22/\" /></a> <img alt=\"\" border=\"0\" src=\"http://stats.wordpress.com/b.gif?host=westi.wordpress.com&blog=15396&post=22&subd=westi&ref=&feed=1\" /></div>\";}i:49;a:7:{s:5:\"title\";s:30:\"Matt: Airport Security Follies\";s:4:\"guid\";s:57:\"http://photomatt.net/2007/12/29/airport-security-follies/\";s:4:\"link\";s:57:\"http://photomatt.net/2007/12/29/airport-security-follies/\";s:11:\"description\";s:323:\"<p><a href=\"http://jetlagged.blogs.nytimes.com/2007/12/28/the-airport-security-follies/index.html\">The Airport Security Follies</a>. &#8220;And rather than rethink our policies, the best we’ve come up with is a way to skirt them — for a fee, naturally — via schemes like Registered Traveler.&#8221;</p>\";s:7:\"pubdate\";s:31:\"Sun, 30 Dec 2007 02:09:08 +0000\";s:2:\"dc\";a:1:{s:7:\"creator\";s:4:\"Matt\";}s:7:\"summary\";s:323:\"<p><a href=\"http://jetlagged.blogs.nytimes.com/2007/12/28/the-airport-security-follies/index.html\">The Airport Security Follies</a>. &#8220;And rather than rethink our policies, the best we’ve come up with is a way to skirt them — for a fee, naturally — via schemes like Registered Traveler.&#8221;</p>\";}}s:7:\"channel\";a:5:{s:5:\"title\";s:16:\"WordPress Planet\";s:4:\"link\";s:28:\"http://planet.wordpress.org/\";s:8:\"language\";s:2:\"en\";s:11:\"description\";s:47:\"WordPress Planet - http://planet.wordpress.org/\";s:7:\"tagline\";s:47:\"WordPress Planet - http://planet.wordpress.org/\";}s:9:\"textinput\";a:0:{}s:5:\"image\";a:0:{}s:9:\"feed_type\";s:3:\"RSS\";s:12:\"feed_version\";s:3:\"2.0\";s:5:\"stack\";a:0:{}s:9:\"inchannel\";b:0;s:6:\"initem\";b:0;s:9:\"incontent\";b:0;s:11:\"intextinput\";b:0;s:7:\"inimage\";b:0;s:13:\"current_field\";s:0:\"\";s:17:\"current_namespace\";b:0;s:19:\"_CONTENT_CONSTRUCTS\";a:6:{i:0;s:7:\"content\";i:1;s:7:\"summary\";i:2;s:4:\"info\";i:3;s:5:\"title\";i:4;s:7:\"tagline\";i:5;s:9:\"copyright\";}s:4:\"etag\";s:25:\"\"293e7-478e970d-c10597\"
\";s:13:\"last_modified\";s:31:\"Wed, 16 Jan 2008 23:45:17 GMT
\";}' WHERE option_name = 'rss_867bd5c64f85878d03a060509cd2f92c'