<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WordPress Plugin Standards</title>
	<atom:link href="http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/</link>
	<description>News, plugins and themes for blogging applications</description>
	<lastBuildDate>Sun, 21 Mar 2010 18:56:44 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: sohbet</title>
		<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/comment-page-1/#comment-214379</link>
		<dc:creator>sohbet</dc:creator>
		<pubDate>Wed, 23 Jul 2008 21:51:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/#comment-214379</guid>
		<description>I don’t like the sound of “strict enforcement” of the things you are suggesting. It limits plugin auhtors too much</description>
		<content:encoded><![CDATA[<p>I don’t like the sound of “strict enforcement” of the things you are suggesting. It limits plugin auhtors too much</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derrick Love</title>
		<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/comment-page-1/#comment-211011</link>
		<dc:creator>Derrick Love</dc:creator>
		<pubDate>Tue, 29 Jan 2008 16:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/#comment-211011</guid>
		<description>I do not agree with number #1. Using the &quot;wp-&quot; in the file makes things easier for me when I have files all over the place.</description>
		<content:encoded><![CDATA[<p>I do not agree with number #1. Using the &#8220;wp-&#8221; in the file makes things easier for me when I have files all over the place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Weathervane</title>
		<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/comment-page-1/#comment-210967</link>
		<dc:creator>Weathervane</dc:creator>
		<pubDate>Sat, 26 Jan 2008 17:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/#comment-210967</guid>
		<description>To paraphrase: you don&#039;t publish with the post you want; you publish with the post you&#039;ve got.

I admit, there are are few tweaks I&#039;d make to that post but the overall idea was to ask for wider professionalism in plugins because of the number of non-technical, new WordPress publishers whose blogs get broken by plugins.

As for &quot;Tell us where we’ll find your plugin access. If your plugin options are in the Admin Area under Options, say so,&quot; it was more a plea for author&#039;s to tell us, somewhere, where their plugin&#039;s configuration has been added. And, yes, it&#039;s a surprise to find plugins with an entry in Options and another in, say, Management or Plugins—not mentioned in the documentation.

I would ask that you take into consideration that I am addressing plugins from the non-technical, new WordPress publisher&#039;s point-of-view.

Regards.</description>
		<content:encoded><![CDATA[<p>To paraphrase: you don&#8217;t publish with the post you want; you publish with the post you&#8217;ve got.</p>
<p>I admit, there are are few tweaks I&#8217;d make to that post but the overall idea was to ask for wider professionalism in plugins because of the number of non-technical, new WordPress publishers whose blogs get broken by plugins.</p>
<p>As for &#8220;Tell us where we’ll find your plugin access. If your plugin options are in the Admin Area under Options, say so,&#8221; it was more a plea for author&#8217;s to tell us, somewhere, where their plugin&#8217;s configuration has been added. And, yes, it&#8217;s a surprise to find plugins with an entry in Options and another in, say, Management or Plugins—not mentioned in the documentation.</p>
<p>I would ask that you take into consideration that I am addressing plugins from the non-technical, new WordPress publisher&#8217;s point-of-view.</p>
<p>Regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JamieO</title>
		<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/comment-page-1/#comment-210864</link>
		<dc:creator>JamieO</dc:creator>
		<pubDate>Wed, 16 Jan 2008 21:36:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/#comment-210864</guid>
		<description>Individual plugin options being accessible via the plugins page makes a lot of sense for plugins which don&#039;t get touched / used during day-to-day blogging. For those that need regular interaction, convert the dashboard into something similar to the widget version sidebar. Each plugin can create it&#039;s own admin widget and the blog user can decide if they want it on or not.</description>
		<content:encoded><![CDATA[<p>Individual plugin options being accessible via the plugins page makes a lot of sense for plugins which don&#8217;t get touched / used during day-to-day blogging. For those that need regular interaction, convert the dashboard into something similar to the widget version sidebar. Each plugin can create it&#8217;s own admin widget and the blog user can decide if they want it on or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wp Wordpress &#187; Blog Archive &#187; WordPress Plugin Standards</title>
		<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/comment-page-1/#comment-210853</link>
		<dc:creator>Wp Wordpress &#187; Blog Archive &#187; WordPress Plugin Standards</dc:creator>
		<pubDate>Tue, 15 Jan 2008 23:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/#comment-210853</guid>
		<description>[...] Appeared on » [...]</description>
		<content:encoded><![CDATA[<p>[...] Appeared on » [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Peralty</title>
		<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/comment-page-1/#comment-210850</link>
		<dc:creator>David Peralty</dc:creator>
		<pubDate>Tue, 15 Jan 2008 20:48:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/#comment-210850</guid>
		<description>I agree that plugin pages need to be managed better, but I don&#039;t like the idea of scattering them everywhere. While it would be nice to have them under the &quot;logical&quot; choices, I like that there are only certain options listed under nearly all of the admin pages, and they don&#039;t change, and I don&#039;t have to search for plugin options... they are all under Options...

There almost needs to be an options button in the plugins page to deal with options... to get them away from creating any extra menus in the WP admin system.</description>
		<content:encoded><![CDATA[<p>I agree that plugin pages need to be managed better, but I don&#8217;t like the idea of scattering them everywhere. While it would be nice to have them under the &#8220;logical&#8221; choices, I like that there are only certain options listed under nearly all of the admin pages, and they don&#8217;t change, and I don&#8217;t have to search for plugin options&#8230; they are all under Options&#8230;</p>
<p>There almost needs to be an options button in the plugins page to deal with options&#8230; to get them away from creating any extra menus in the WP admin system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen R</title>
		<link>http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/comment-page-1/#comment-210846</link>
		<dc:creator>Stephen R</dc:creator>
		<pubDate>Tue, 15 Jan 2008 16:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.bloggingpro.com/archives/2008/01/15/wordpress-plugin-standards/#comment-210846</guid>
		<description>I don&#039;t like the sound of &quot;strict enforcement&quot; of the things you are suggesting.  It limits plugin auhtors too much.  I have, for example, a plugin with an options page located under Presentation.  Why is it there?  Because it displays pull-quotes in the post content -- it&#039;s purely presentational, and Presentation is a logical location for it.  I sometimes wish plugin designers would do this a bit more intelligently instead of blindly dumping everything under &quot;options&quot;.  Spam Karma?  That should be under &quot;Comments&quot;.  Ditto &quot;Bad Behavior&quot;.

As it is my Options tab has a sub-list that&#039;s almost three lines deep!  Ack!</description>
		<content:encoded><![CDATA[<p>I don&#8217;t like the sound of &#8220;strict enforcement&#8221; of the things you are suggesting.  It limits plugin auhtors too much.  I have, for example, a plugin with an options page located under Presentation.  Why is it there?  Because it displays pull-quotes in the post content &#8212; it&#8217;s purely presentational, and Presentation is a logical location for it.  I sometimes wish plugin designers would do this a bit more intelligently instead of blindly dumping everything under &#8220;options&#8221;.  Spam Karma?  That should be under &#8220;Comments&#8221;.  Ditto &#8220;Bad Behavior&#8221;.</p>
<p>As it is my Options tab has a sub-list that&#8217;s almost three lines deep!  Ack!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
