<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: WordPress Plugin Update Notification</title>
	<atom:link href="http://mtdewvirus.com/archives/2005/06/24/wordpress-plugin-update-notification/feed/" rel="self" type="application/rss+xml" />
	<link>http://mtdewvirus.com/archives/2005/06/24/wordpress-plugin-update-notification/</link>
	<description>Nick Momrik</description>
	<pubDate>Sat, 30 Aug 2008 05:03:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Miles Baker</title>
		<link>http://mtdewvirus.com/archives/2005/06/24/wordpress-plugin-update-notification/#comment-56464</link>
		<dc:creator>Miles Baker</dc:creator>
		<pubDate>Mon, 02 Oct 2006 17:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://mtdewvirus.com/?p=896#comment-56464</guid>
		<description>I had the same idea, in fact, I was searching to see if there was such a plugin and that's how I found this article.  Hopefully Wordpress is working on something, with over 20 plugins and growing it takes a full weekend for me to update them all, at least knowing if I need to look for an update would save me some time.</description>
		<content:encoded><![CDATA[<p>I had the same idea, in fact, I was searching to see if there was such a plugin and that&#8217;s how I found this article.  Hopefully Wordpress is working on something, with over 20 plugins and growing it takes a full weekend for me to update them all, at least knowing if I need to look for an update would save me some time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Plugin Idea: Plugin Update Notification - Stupid Wordpress Tricks</title>
		<link>http://mtdewvirus.com/archives/2005/06/24/wordpress-plugin-update-notification/#comment-34252</link>
		<dc:creator>Plugin Idea: Plugin Update Notification - Stupid Wordpress Tricks</dc:creator>
		<pubDate>Thu, 20 Apr 2006 08:15:18 +0000</pubDate>
		<guid isPermaLink="false">http://mtdewvirus.com/?p=896#comment-34252</guid>
		<description>[...] This is a really good idea - a central repository for notification of plugin updates. - from mtdewvirus.com [...]</description>
		<content:encoded><![CDATA[<p>[...] This is a really good idea - a central repository for notification of plugin updates. - from mtdewvirus.com [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markku</title>
		<link>http://mtdewvirus.com/archives/2005/06/24/wordpress-plugin-update-notification/#comment-30344</link>
		<dc:creator>markku</dc:creator>
		<pubDate>Sat, 25 Jun 2005 18:20:59 +0000</pubDate>
		<guid isPermaLink="false">http://mtdewvirus.com/?p=896#comment-30344</guid>
		<description>I definitely agree --- finding updates to plugins you're currently using can be be daunting. Sometimes I try to modify someone else's plugin only to find out that the feature I want was already added right after I downloaded the version I have.

The current plugin system in WP has the "Plugin URI" field that points to the plugin's homepage. Unfortunately, some point to an entry on their blog, and fail to update/revise it when they update the plugin, and users never notice the new versions unless they start digging.

I think we can use RSS for this, for displaying the current version as reported by the plugin writer. Even textfiles can do this. In the plugin file, we can add the field "Current version URI" or something, pointing to myserver.com/project/mypluginversion.txt, which may simply contain "1.5" or the current stable version.</description>
		<content:encoded><![CDATA[<p>I definitely agree &#8212; finding updates to plugins you&#8217;re currently using can be be daunting. Sometimes I try to modify someone else&#8217;s plugin only to find out that the feature I want was already added right after I downloaded the version I have.</p>
<p>The current plugin system in WP has the &#8220;Plugin URI&#8221; field that points to the plugin&#8217;s homepage. Unfortunately, some point to an entry on their blog, and fail to update/revise it when they update the plugin, and users never notice the new versions unless they start digging.</p>
<p>I think we can use RSS for this, for displaying the current version as reported by the plugin writer. Even textfiles can do this. In the plugin file, we can add the field &#8220;Current version URI&#8221; or something, pointing to myserver.com/project/mypluginversion.txt, which may simply contain &#8220;1.5&#8243; or the current stable version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://mtdewvirus.com/archives/2005/06/24/wordpress-plugin-update-notification/#comment-30341</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Sat, 25 Jun 2005 16:28:42 +0000</pubDate>
		<guid isPermaLink="false">http://mtdewvirus.com/?p=896#comment-30341</guid>
		<description>I have the same problem with firefox extensions. At least firefox enables you to autodownload them. However as I want to ensure I have the latest copy on a usb drive (for installation on other machines) I have to find the download sites.
What I do now is to bookmark each extension homepage into a specified bookmark folder called extensions in my browser and then when a new one comes out I just go to my extension bookmarks folder. If I want to see them all at once, I just open all of them in individual tabs.</description>
		<content:encoded><![CDATA[<p>I have the same problem with firefox extensions. At least firefox enables you to autodownload them. However as I want to ensure I have the latest copy on a usb drive (for installation on other machines) I have to find the download sites.<br />
What I do now is to bookmark each extension homepage into a specified bookmark folder called extensions in my browser and then when a new one comes out I just go to my extension bookmarks folder. If I want to see them all at once, I just open all of them in individual tabs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
