<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WordPress Expert</title>
	<atom:link href="http://johnlamansky.com/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnlamansky.com/wordpress</link>
	<description></description>
	<lastBuildDate>Mon, 25 Feb 2013 15:26:51 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>How to Remove Dates from WordPress Posts</title>
		<link>http://johnlamansky.com/wordpress/remove-post-dates/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=remove-post-dates</link>
		<comments>http://johnlamansky.com/wordpress/remove-post-dates/#comments</comments>
		<pubDate>Wed, 01 Jun 2011 17:27:56 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[Tutorials]]></category>

		<guid isPermaLink="false">http://johnlamansky.com/wordpress/?p=132</guid>
		<description><![CDATA[If your content is not time-oriented (such as when using WordPress in non-blog contexts), you may wish to remove the publication date from your posts since this information is not relevant and can give the impression that your older content is outdated. 1. The Manual Method The &#8220;proper&#8221; way to do this would be to [...]]]></description>
				<content:encoded><![CDATA[<p>If your content is not time-oriented (such as when using WordPress in non-blog contexts), you may wish to remove the publication date from your posts since this information is not relevant and can give the impression that your older content is outdated.</p>
<h3>1. The Manual Method</h3>
<p>The &#8220;proper&#8221; way to do this would be to edit your theme and remove the code that displays the post dates.</p>
<ol>
<li><a href="http://johnlamansky.com/wordpress/backup-theme/">Backup your theme</a>, just in case</li>
<li>Go to &#8220;Appearance > Editor&#8221; and repeat the following steps for each of your theme&#8217;s PHP files</li>
<li>Look for these function calls in your theme&#8217;s code: <code>the_date()</code>, <code>echo get_the_date()</code>, <code>the_modified_date()</code>, and <code>the_time()</code></li>
<li>Surround the function calls with PHP comment markers (<code>/*</code> and <code>*/</code>); here are some examples:
<pre>&lt;?php /*the_date();*/ ?&gt;
&lt;?php /*the_date('F j, Y');*/ ?&gt;
&lt;?php /*echo get_the_date();*/ ?&gt;
&lt;?php /*the_modified_date();*/ ?&gt;
&lt;?php /*the_modified_date('', 'Last modified ');*/ ?&gt;
&lt;?php /*the_time( get_option('date_format') );*/ ?&gt;</pre>
</li>
<li>You may want to remove other text surrounding the function call. For example, if your theme has this code&#8230;
<pre>&lt;div&gt;Published on &lt;?php the_time( get_option('date_format') ); ?&gt;&lt;/div&gt;</pre>
<p>&#8230;and you replace it with this&#8230;</p>
<pre>&lt;div&gt;Published on &lt;?php /*the_time( get_option('date_format') );*/ ?&gt;&lt;/div&gt;</pre>
<p>&#8230;your theme will output &#8220;Published on,&#8221; but not the date. Deleting &#8220;Published on&#8221; from your theme file will remove it from your site. Just be aware that you may have to remove text like this from your theme files to get a clean-looking result.</li>
<li>Click &#8220;Update File&#8221;</li>
</ol>
<h3>2. The Automatic Method</h3>
<p>If you&#8217;re looking for a quick fix, just go to &#8220;Appearance > Editor&#8221; in your WordPress admin and add this code to your theme&#8217;s functions.php file. Put it at the top of the file, but <em>after</em> the opening <code>&lt;?php</code> line.</p>
<pre>function jl_remove_post_dates() {
	add_filter('the_date', '__return_false');
	add_filter('the_time', '__return_false');
	add_filter('the_modified_date', '__return_false');
} add_action('loop_start', 'jl_remove_post_dates');</pre>
<p>(Note: This method requires WordPress 3.0 or above)</p>
<p>Now check your site and verify that the post dates are gone. If they&#8217;re not, try replacing the code above with this more &#8220;aggressive&#8221; version:</p>
<pre>function jl_remove_post_dates() {
	add_filter('the_date', '__return_false');
	add_filter('the_time', '__return_false');
	add_filter('the_modified_date', '__return_false');
	add_filter('get_the_date', '__return_false');
	add_filter('get_the_time', '__return_false');
	add_filter('get_the_modified_date', '__return_false');
} add_action('loop_start', 'jl_remove_post_dates');</pre>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/remove-post-dates/feed/</wfw:commentRss>
		<slash:comments>53</slash:comments>
		</item>
		<item>
		<title>WordPress Tweaks 2.0 Released!</title>
		<link>http://johnlamansky.com/wordpress/wordpress-tweaks-2-0/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-tweaks-2-0</link>
		<comments>http://johnlamansky.com/wordpress/wordpress-tweaks-2-0/#comments</comments>
		<pubDate>Sat, 28 May 2011 02:40:43 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[WordPress Tweaks]]></category>

		<guid isPermaLink="false">http://johnlamansky.com/wordpress/?p=151</guid>
		<description><![CDATA[I recently rewrote my WordPress Tweaks plugin and have launched the new edition as version 2.0. The previous version of WordPress Tweaks (version 1.8) was released 3 years ago (back when WordPress was at version 2.5), so the plugin was definitely in need of an upgrade! Version 2.0 adds 5 new tweaks, removes 13 outdated [...]]]></description>
				<content:encoded><![CDATA[<p>I recently rewrote my <a href="http://johnlamansky.com/wordpress/plugins/tweaks/">WordPress Tweaks</a> plugin and have launched the new edition as version 2.0. The previous version of WordPress Tweaks (version 1.8) was released 3 years ago (back when WordPress was at version 2.5), so the plugin was definitely in need of an upgrade!</p>
<p>Version 2.0 adds 5 new tweaks, removes 13 outdated tweaks, fixes a few tweaks that broke between WordPress 2.5 and 3.1, adheres to new plugin development best practices that have emerged since WP 2.5, adds an instant search bar, and ups the minimum WordPress requirement from 2.1 to 3.1 (quite the jump!).</p>
<p>For those who aren&#8217;t familiar with the plugin, WordPress Tweaks gathers a plethora of assorted options into a convenient list of checkboxes and dropdowns. (WordPress Tweaks is in the same vein as Microsoft&#8217;s abandoned TweakUI program, for those who remember it.)</p>
<p>Here&#8217;s the current list of supported tweaks:</p>
<ul>
<li>Admin
<ul>
<li>Automatically scroll to the post editor</li>
<li>Disable the admin bar</li>
<li>Disable the Dashboard</li>
<li>Disable the &#8220;Search Engines Blocked&#8221; notice</li>
<li>Disable tag autocomplete</li>
<li>Disable WordPress&#8217;s admin footer text/links</li>
</ul>
</li>
<li>Comments and Pings
<ul>
<li>Disable self-pinging</li>
<li>Dofollow comment author links</li>
<li>Dofollow comment body links</li>
<li>Open external comment links in new windows</li>
</ul>
</li>
<li>Media
<ul>
<li>Disable the Flash uploader</li>
<li>Default media inserter tab
<ul>
<li>From Computer</li>
<li>From URL</li>
<li>Gallery</li>
<li>Media Library</li>
</ul>
</li>
<li>JPEG Quality</li>
</ul>
</li>
<li>Posts
<ul>
<li>Disable post revisions</li>
<li>Force excerpts on archives</li>
<li>Open external post links in new windows</li>
<li>Add a &#8220;Continue reading&#8221; link to excerpts</li>
</ul>
</li>
</ul>
<h3>Install Now</h3>
<p>Ready to start tweaking? Just enter the homepage URL of your WordPress site:<br />

<form action='http://johnlamansky.com/wordpress/wp-content/plugins/autoinstaller/install.php' method='post' target='_blank' class='jl-ai'>
	<input type='hidden' name='plugin' value='wordpress-tweaks' />
	<input type='text' class='textbox' name='wpurl' value='http://' /><input type='submit' class='button' value='Launch Installer' />
</form>
</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/wordpress-tweaks-2-0/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>How to Fix Missing Post Dates in Your WordPress Theme</title>
		<link>http://johnlamansky.com/wordpress/missing-post-dates/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=missing-post-dates</link>
		<comments>http://johnlamansky.com/wordpress/missing-post-dates/#comments</comments>
		<pubDate>Thu, 26 May 2011 14:41:02 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>

		<guid isPermaLink="false">http://johnlamansky.com/wordpress/?p=124</guid>
		<description><![CDATA[The problem: When you have multiple posts published on the same day, the post date only shows up for the first one when you view the posts on your site. The fix: Go to &#8220;Appearance > Editor&#8221; and repeat the following steps for each of your theme files Look for instances of this code: &#60;?php [...]]]></description>
				<content:encoded><![CDATA[<p><strong>The problem:</strong><br />
When you have multiple posts published on the same day, the post date only shows up for the first one when you view the posts on your site.</p>
<p><strong>The fix:</strong></p>
<ol class="spaced">
<li>Go to &#8220;Appearance > Editor&#8221; and repeat the following steps for each of your theme files</li>
<li>Look for instances of this code:
<pre>&lt;?php the_date(); ?&gt;</pre>
</li>
<li>Replace that code with this code:
<pre>&lt;?php echo get_the_date(); ?&gt;</pre>
</li>
<li>Click &#8220;Update File&#8221;</li>
</ol>
<p><strong>The explanation:</strong><br />
Most WordPress template tag functions that start with &#8220;the_&#8221; will merely output the values returned by their equivalent &#8220;get_the_&#8221; functions. However, &#8220;the_date()&#8221; is an exception to this standard because it adds functionality that&#8217;s not present in &#8220;get_the_date()&#8221;, namely, not outputting the same date more than once per page, which can be a feature or an annoyance depending on your desired functionality.</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/missing-post-dates/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>New URL and Site Design</title>
		<link>http://johnlamansky.com/wordpress/new-url-and-site-design/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=new-url-and-site-design</link>
		<comments>http://johnlamansky.com/wordpress/new-url-and-site-design/#comments</comments>
		<pubDate>Thu, 26 May 2011 14:40:35 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://johnlamansky.com/wordpress/?p=120</guid>
		<description><![CDATA[My &#8220;WordPress Expert&#8221; blog recently got a redesign and has moved from wordpress.jdwebdev.com to johnlamansky.com/wordpress, joining my technology how-to blog which is now located at johnlamansky.com/tech. I decided it would be nice to consolidate my blogs under one domain name, plus the &#8220;jdwebdev&#8221; domain didn&#8217;t make much sense anymore since I&#8217;m no longer seeking out [...]]]></description>
				<content:encoded><![CDATA[<p>My &#8220;WordPress Expert&#8221; blog recently got a redesign and has moved from wordpress.jdwebdev.com to johnlamansky.com/wordpress, joining my technology how-to blog which is now located at johnlamansky.com/tech. I decided it would be nice to consolidate my blogs under one domain name, plus the &#8220;jdwebdev&#8221; domain didn&#8217;t make much sense anymore since I&#8217;m no longer seeking out new web development clients.</p>
<p>For you RSS subscribers out there, the RSS URL will remain the same for now, and if I do change it, I&#8217;ll be sure to 301-redirect it so you don&#8217;t have to update it manually.</p>
<p>The new design isn&#8217;t anything too fancy since I&#8217;m definitely more a developer than a designer, but if you have any comments I&#8217;d be interested to hear them. It&#8217;s my first time developing a WordPress theme from scratch instead of basing it off another theme (e.g. Sandbox).</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/new-url-and-site-design/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Tip for Plugin Developers: Inline Changelogs</title>
		<link>http://johnlamansky.com/wordpress/inline-changelogs/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=inline-changelogs</link>
		<comments>http://johnlamansky.com/wordpress/inline-changelogs/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 16:51:12 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[inline changelogs]]></category>
		<category><![CDATA[plugin development]]></category>
		<category><![CDATA[SEO Ultimate]]></category>

		<guid isPermaLink="false">http://wordpress.jdwebdev.com/?p=106</guid>
		<description><![CDATA[Recently, the Dev4Press and Weblog Tools Collection blogs made posts about integrating plugin changelogs into the Plugins dashboard. This functionality was something I was already doing in the SEO Ultimate plugin, so I thought I&#8217;d share my technique for doing this. (My method is different because it&#8217;s simpler and it integrates directly into WordPress&#8217;s update [...]]]></description>
				<content:encoded><![CDATA[<p>Recently, the <a href="http://www.dev4press.com/2009/05/28/expanding-plugins-panel/">Dev4Press</a> and <a href="http://weblogtoolscollection.com/archives/2009/06/18/notify-users-about-changes-in-plugins-in-plugin-dashboard/">Weblog Tools Collection</a> blogs made posts about integrating plugin changelogs into the Plugins dashboard. This functionality was something I was already doing in the <a href="http://wordpress.jdwebdev.com/blog/seo-ultimate-0.6/">SEO Ultimate</a> plugin, so I thought I&#8217;d share my technique for doing this. (My method is different because it&#8217;s simpler and it integrates directly into WordPress&#8217;s update message.)</p>
<p>Here&#8217;s what an inline changelog looks like when implemented:</p>
<p><img src="http://wordpress.jdwebdev.com/wp-content/uploads/2009/07/seo-ultimate-05-inline-changelog.jpg" alt="Example of inline changelog from SEO Ultimate" width="574" height="124" class="aligncenter size-full wp-image-137" /></p>
<p>As you can see, a small notice like this helps users know at-a-glance what&#8217;s new in your plugin update.</p>
<p>Here&#8217;s the code you can incorporate into your plugin:</p>
<p><span id="more-106"></span></p>
<pre>
&lt;?php
function my_plugin_update_info() {
	if ( $info = wp_remote_fopen("http://www.example.com/my-plugin-updates.txt") )
		echo '&lt;br /&gt;' . strip_tags( $info, "&lt;br&gt;&lt;a&gt;&lt;b&gt;&lt;i&gt;&lt;span&gt;" );
}
add_action('in_plugin_update_message-'.plugin_basename(__FILE__), 'my_plugin_update_info');
?&gt;
</pre>
<p>Of course, to keep plugin users happy, be sure that your inline changelogs are informative and unobtrusive. Happy coding!</p>
<p>(Plugin users, if you&#8217;d like to see this feature implemented in your favorite plugins, you could try sending the plugin author a link to this post! You could also check out the new <a href="http://wordpress.org/extend/plugins/changelogger/">Changelogger</a> plugin.)</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/inline-changelogs/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Announcing the &#8220;SEO Ultimate&#8221; Plugin</title>
		<link>http://johnlamansky.com/wordpress/seo-ultimate-0-6/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=seo-ultimate-0-6</link>
		<comments>http://johnlamansky.com/wordpress/seo-ultimate-0-6/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 23:10:08 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[SEO plugin]]></category>
		<category><![CDATA[SEO Ultimate]]></category>

		<guid isPermaLink="false">http://wordpress.jdwebdev.com/?p=109</guid>
		<description><![CDATA[Normally when I set up plugin-level SEO on a WordPress blog, I&#8217;ll need 5-8 plugins to provide all the desired SEO functionality. Wouldn&#8217;t it be cool if there was one plugin that incorporated all that functionality and more into one easy-to-use suite? That&#8217;s the goal of SEO Ultimate, which is a free plugin I&#8217;m developing [...]]]></description>
				<content:encoded><![CDATA[<p>Normally when I set up plugin-level SEO on a WordPress blog, I&#8217;ll need 5-8 plugins to provide all the desired SEO functionality. Wouldn&#8217;t it be cool if there was one plugin that incorporated all that functionality and more into one easy-to-use suite?</p>
<p>That&#8217;s the goal of <a href="http://wordpress.org/extend/plugins/seo-ultimate/">SEO Ultimate</a>, which is a free plugin I&#8217;m developing on behalf of <a href="http://www.seodesignsolutions.com/">SEO Design Solutions</a>.</p>
<p><span id="more-109"></span></p>
<p>Right now the plugin is in its early stages (currently at version 0.6). There are many more features yet to come; as more functionality is added, I expect SEO Ultimate to become the all-in-one WordPress SEO solution of choice for more people as time goes on.</p>
<h4>Features</h4>
<p>Current functionality includes the standard <a href="http://wordpress.org/extend/plugins/all-in-one-seo-pack/">All in One SEO Pack</a> features:</p>
<ul>
<li>Title rewriting</li>
<li>Noindex checkboxes</li>
<li>Meta editing</li>
<li>Canonical tags</li>
<li>Post meta box	</li>
</ul>
<p>SEO Ultimate also has these additional capabilities:</p>
<ul>
<li>404 monitoring</li>
<li>Linkbox insertion</li>
<li>Settings import/export functions</li>
</ul>
<p>Upcoming features include robots.txt editing, 301 logging, XHTML validation status monitoring, and much more. (If you install the plugin now, you can get these features delivered to you on a regular basis via WordPress&#8217;s semi-automatic plugin updater!)</p>
<p>I&#8217;ve also incorporated these extra features into SEO Ultimate:</p>
<ul>
<li><a href="http://wordpress.jdwebdev.com/blog/inline-changelogs/">Inline changelogs</a></li>
<li><a href="http://westi.wordpress.com/2009/06/20/changelogs-changelogs-changelogs/">Readme changelog</a></li>
<li><a href="http://striderweb.com/nerdaphernalia/2008/06/give-your-wordpress-plugin-credit/">Footer branding</a></li>
<li>WordPress 2.7 menu integration</li>
<li>Integration with WordPress&#8217;s Help system</li>
<li>Inline phpDoc documentation</li>
</ul>
<h4>Auto-Installer</h4>
<p>Also, be sure to check out this cool auto-installer system I invented. Just type in your blog&#8217;s URL, click &#8220;Launch Installer,&#8221; then click &#8220;Install Now,&#8221; and voila, SEO Ultimate will be installed on your blog! You can then enable it by clicking the Activate link.</p>
<p>Try it out:</p>
<form action="http://www.seodesignsolutions.com/wordpress-seo/su-install.php" method="post"></form>
<p>You can also <a href="http://downloads.wordpress.org/plugin/seo-ultimate.zip">download the zip file</a>. SEO Ultimate requires WordPress 2.7 or above.</p>
<p>Let me know what you think!</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/seo-ultimate-0-6/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>WordPress Tweaks 1.8</title>
		<link>http://johnlamansky.com/wordpress/wordpress-tweaks-1-8/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-tweaks-1-8</link>
		<comments>http://johnlamansky.com/wordpress/wordpress-tweaks-1-8/#comments</comments>
		<pubDate>Mon, 30 Jun 2008 16:10:23 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[WordPress Tweaks]]></category>
		<category><![CDATA[plugin update]]></category>

		<guid isPermaLink="false">http://wordpress.jdwebdev.com/?p=89</guid>
		<description><![CDATA[Version 1.8 of the WordPress Tweaks plugin has been released! Here are the changes for this version: Added the &#8220;Automatically scroll to the post editor&#8221; tweak (based on the WriteScroll plugin) Removed unnecessary JavaScript HTTP calls (hat tip to user Doug) Removed unused code Added a POT file to the plugin distribution Fixed a WordPress [...]]]></description>
				<content:encoded><![CDATA[<p>Version 1.8 of the <a href="http://wordpress.jdwebdev.com/plugins/tweaks/">WordPress Tweaks</a> plugin has been released! Here are the changes for this version:</p>
<ul>
<li>Added the &#8220;Automatically scroll to the post editor&#8221; tweak (based on the <a href="http://wordpress.org/extend/plugins/writescroll/">WriteScroll</a> plugin)</li>
<li>Removed unnecessary JavaScript HTTP calls (hat tip to user Doug)</li>
<li>Removed unused code</li>
<li>Added a POT file to the plugin distribution</li>
<li>Fixed a WordPress 2.6 compatibility bug (<a href="http://wordpress.jdwebdev.com/blog/wordpress-tweaks-1.7/#comment-914">reported</a> by user Chris)</li>
<li>Other minor enhancements</li>
</ul>
<p><a href="http://wordpress.jdwebdev.com/plugins/tweaks/">Learn more about WordPress Tweaks</a> or <a href="http://wordpress.jdwebdev.com/plugins/tweaks/download/">download the latest version here</a>!</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/wordpress-tweaks-1-8/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Top 3 Underrated WordPress Plugins</title>
		<link>http://johnlamansky.com/wordpress/underrated-wordpress-plugins/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=underrated-wordpress-plugins</link>
		<comments>http://johnlamansky.com/wordpress/underrated-wordpress-plugins/#comments</comments>
		<pubDate>Thu, 26 Jun 2008 14:00:38 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Broken Link Checker]]></category>
		<category><![CDATA[WP SEO Master]]></category>
		<category><![CDATA[WP-Project]]></category>

		<guid isPermaLink="false">http://wordpress.jdwebdev.com/?p=80</guid>
		<description><![CDATA[There are a ton of WordPress plugins out there, so it&#8217;s no surprise that many are lost in the crowd. Here are three great plugins that I think deserve more attention (inspired by this post from a year ago): Broken Link Checker &#8212; Automatically checks your posts for broken links and images and reports its [...]]]></description>
				<content:encoded><![CDATA[<p>There are a ton of <a href="http://wordpress.org/extend/plugins/">WordPress plugins</a> out there, so it&#8217;s no surprise that many are lost in the crowd. Here are three great plugins that I think deserve more attention (inspired by <a href="http://www.dailyblogtips.com/top-10-underrated-wordpress-plugins/">this post</a> from a year ago):</p>
<p><span id="more-80"></span></p>
<ol>
<li>
<p><strong><a href="http://wordpress.org/extend/plugins/broken-link-checker/">Broken Link Checker</a></strong> &#8212; Automatically checks your posts for broken links and images and reports its findings in the dashboard. Its AJAX capabilities even allow you to fix the offending links without editing the posts!</p>
</li>
<li>
<p><strong><a href="http://wordpress.org/extend/plugins/wp-project/">WP-Project</a></strong> &#8212; This plugin adds lightweight project management to WordPress. If you want the ability to track clients, projects, and tasks from within your blog, this plugin is for you.</li>
<li>
<p><strong><a href="http://www.bercongroup.com/products/wordpress-plugins/wp-seo-master">WP SEO Master</a></strong> &#8212; The WordPress SEO arena is usually dominated by plugins like All in One SEO Pack, but this plugin provides some unique functionality, including keyword autolinking and comprehensive noindex/nofollow options.</p>
</li>
</ol>
<p>What&#8217;s on your top list of cool plugins that aren&#8217;t mentioned that often? Let us know in the comments!</p>
<p>This would also make a cool blog meme: if WordPress-using bloggers could post a list of plugins that they think should have more limelight, we could promote plugin authors&#8217; works and help each other discover some cool plugins.</p>
<p>I&#8217;ll tag the following bloggers: <a href="http://hackwordpress.com/">Kyle at Hack WordPress</a>, <a href="http://www.wpproject.com/">Richard at WP Project</a> (not to be confused with the plugin listed above), and <a href="http://themeshaper.com/">Ian at ThemeShaper</a>. If others would like to participate, feel free to do so! (If you don&#8217;t blog about WordPress, perhaps you could discuss plugins related to your niche.) Just post your list on your blog, link to this post if you want to register a pingback, and then tag additional bloggers.</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/underrated-wordpress-plugins/feed/</wfw:commentRss>
		<slash:comments>22</slash:comments>
		</item>
		<item>
		<title>WordPress 2.6 Beta 1 Released</title>
		<link>http://johnlamansky.com/wordpress/wordpress-2-6-beta-1-released/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-2-6-beta-1-released</link>
		<comments>http://johnlamansky.com/wordpress/wordpress-2-6-beta-1-released/#comments</comments>
		<pubDate>Tue, 24 Jun 2008 13:02:35 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[Asides]]></category>
		<category><![CDATA[Updates]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[WordPress 2.6]]></category>

		<guid isPermaLink="false">http://wordpress.jdwebdev.com/?p=88</guid>
		<description><![CDATA[Beta 1 of WordPress 2.6 has been released! If you want to test it safely, you should be able to do so as soon as the WordPress 2.6 demo site is updated. Update: Robert posted a comment pointing out an alternate demo site.]]></description>
				<content:encoded><![CDATA[<p><a href="http://wordpress.org/wordpress-2.6-beta1.zip">Beta 1</a> of <a href="http://wordpress.jdwebdev.com/blog/wordpress-26-features/">WordPress 2.6</a> <a href="http://boren.nu/archives/2008/06/23/wordpress-26-beta-1/">has been released</a>! If you want to test it safely, you should be able to do so as soon as the <a href="http://wp.chrisjohnston.org/">WordPress 2.6 demo site</a> is updated.</p>
<p><strong>Update:</strong> Robert posted a comment pointing out an <a href="http://demo.talkpress.de/trunk/">alternate demo site</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/wordpress-2-6-beta-1-released/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress 2.6 Now Expected in Early July</title>
		<link>http://johnlamansky.com/wordpress/wordpress-2-6-july-release-date/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-2-6-july-release-date</link>
		<comments>http://johnlamansky.com/wordpress/wordpress-2-6-july-release-date/#comments</comments>
		<pubDate>Mon, 23 Jun 2008 20:38:06 +0000</pubDate>
		<dc:creator>John Lamansky</dc:creator>
				<category><![CDATA[Updates]]></category>
		<category><![CDATA[Trac]]></category>
		<category><![CDATA[WordPress 2.6]]></category>
		<category><![CDATA[WordPress 2.7]]></category>

		<guid isPermaLink="false">http://wordpress.jdwebdev.com/?p=87</guid>
		<description><![CDATA[WordPress 2.6 was previously slated for an August 2008 release, but the WordPress Trac Roadmap has recently been updated with the following information on the WordPress 2.6 release date: July 7 stretch with July 14 fallback That&#8217;s pretty terse, but I&#8217;d interpret it to mean &#8220;we&#8217;ll try to get it done July 7; it would [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://wordpress.jdwebdev.com/blog/wordpress-26-features/">WordPress 2.6</a> was previously slated for an August 2008 release, but the <a href="http://trac.wordpress.org/roadmap">WordPress Trac Roadmap</a> has recently been updated with the following information on the WordPress 2.6 release date:</p>
<p><span id="more-87"></span></p>
<blockquote><p>July 7 stretch with July 14 fallback</p></blockquote>
<p>That&#8217;s pretty terse, but I&#8217;d interpret it to mean &#8220;we&#8217;ll try to get it done July 7; it would be a stretch though, so we&#8217;ll have July 14 as a fallback.&#8221;</p>
<p>Considering the new release date is only 2 weeks away, and the Trac only shows 12% progress on WordPress 2.6 so far, I&#8217;d say it&#8217;s likely that many changes previously planned for 2.6 will be bumped to version 2.7.</p>
]]></content:encoded>
			<wfw:commentRss>http://johnlamansky.com/wordpress/wordpress-2-6-july-release-date/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: johnlamansky.com @ 2013-05-22 19:05:18 -->