<?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>seanklein.org &#187; Plugins</title>
	<atom:link href="http://seanklein.org/category/plugins/feed/" rel="self" type="application/rss+xml" />
	<link>http://seanklein.org</link>
	<description></description>
	<lastBuildDate>Sat, 28 Jan 2012 03:56:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>WordPress Autosave</title>
		<link>http://seanklein.org/2010/11/wordpress-autosave/</link>
		<comments>http://seanklein.org/2010/11/wordpress-autosave/#comments</comments>
		<pubDate>Wed, 10 Nov 2010 17:14:12 +0000</pubDate>
		<dc:creator>Sean Klein</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Things I've Learned]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[autosave]]></category>
		<category><![CDATA[TIL]]></category>
		<category><![CDATA[wordpress plugins]]></category>

		<guid isPermaLink="false">http://seanklein.org/?p=75</guid>
		<description><![CDATA[Recently I was having an issue with the WordPress autosave running on my posts in a custom post type.  I am running a lot of scripts in the &#8220;save_post&#8221; action and couldn&#8217;t find a good way to exclude autosaves from running this code. Note that I looked at the info being passed to the functions&#8230;]]></description>
			<content:encoded><![CDATA[<p>Recently I was having an issue with the WordPress autosave running on my posts in a custom post type.  I am running a lot of scripts in the &#8220;save_post&#8221; action and couldn&#8217;t find a good way to exclude autosaves from running this code.</p>
<p>Note that I looked at the info being passed to the functions and the usual suspects for looking at wether it was an autosave or not weren&#8217;t helping.</p>
<p>My biggest problem came when typing a title in the custom post type, then clicking outside of the title field.  Normally this kicks off the autosave feature automatically so the post permalink can be established and displayed below the post title.  Since I wasn&#8217;t using this custom post type on the front of end of the site, I really didn&#8217;t care about that.</p>
<p>So now for the easiest way to disable autosave for the custom post type:</p>
<pre class="prettyprint">
function seans_admin_init() {
	if (!empty($_GET['post']) || (!empty($_GET['post_type']) &#038;&#038; $_GET['post_type'] == '[custom_post_type]')) {
		$post_type = '';

		if (!empty($_GET['post'])) {
			$post_type = get_post_type(intval($_GET['post']));
		}
		else if (!empty($_GET['post_type'])) {
			$post_type = $_GET['post_type'];
		}

		if (!empty($post_type) &#038;&#038; $post_type == '[custom_post_type]') {
			// Hi, I block Autosave from running on posts
			wp_deregister_script('autosave');
		}
	}

}
add_action('admin_init', 'seans_admin_init');
</pre>
]]></content:encoded>
			<wfw:commentRss>http://seanklein.org/2010/11/wordpress-autosave/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Code to Widget Updated to 1.1.1</title>
		<link>http://seanklein.org/2010/05/code-to-widget-updated-to-1-1-1/</link>
		<comments>http://seanklein.org/2010/05/code-to-widget-updated-to-1-1-1/#comments</comments>
		<pubDate>Sat, 29 May 2010 05:25:47 +0000</pubDate>
		<dc:creator>Sean Klein</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[code to widget]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wordpress plugins]]></category>

		<guid isPermaLink="false">http://seanklein.org/?p=69</guid>
		<description><![CDATA[After some discussions with coworkers and a plugin user, I realized the plugin needed a little more documentation on the template directory.  I have added some absolute paths to the plugin settings screen for easier reference. I also added a button to test and make sure that the directory is usable for the plugin.  It&#8230;]]></description>
			<content:encoded><![CDATA[<p>After some discussions with coworkers and a plugin user, I realized the plugin needed a little more documentation on the template directory.  I have added some absolute paths to the plugin settings screen for easier reference.</p>
<p>I also added a button to test and make sure that the directory is usable for the plugin.  It does an AJAX request to check and see if the folder exists and is readable.  After the check it displays either a smiley or an exclamation point in the input field to let you know whether it is good or not.</p>
<p>Again please let me know if you find issues, or have feature requests.  I will try to get more updates out soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://seanklein.org/2010/05/code-to-widget-updated-to-1-1-1/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Code To Widget Plugin Released</title>
		<link>http://seanklein.org/2010/05/code-to-widget-plugin-released/</link>
		<comments>http://seanklein.org/2010/05/code-to-widget-plugin-released/#comments</comments>
		<pubDate>Tue, 25 May 2010 02:48:34 +0000</pubDate>
		<dc:creator>Sean Klein</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[code to widget]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[wordpress plugins]]></category>

		<guid isPermaLink="false">http://seanklein.org/?p=66</guid>
		<description><![CDATA[I&#8217;m very happy to announce the release of the Code To Widget WordPress plugin.  The plugin reads files in a directory and automatically creates widgets to be placed in sidebars.  It gives developers/designers the ability to create widgets without having to write the widget code every time. This plugin was initially written out of frustration.&#8230;]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m very happy to announce the release of the <a href="http://wordpress.org/extend/plugins/code-to-widget/">Code To Widget</a> WordPress plugin.  The plugin reads files in a directory and automatically creates widgets to be placed in sidebars.  It gives developers/designers the ability to create widgets without having to write the widget code every time.</p>
<p>This plugin was initially written out of frustration.  About a year ago I got tired of writing widget initialization code over and over again just to create widgets.  I also thought it would be cool for people who didn&#8217;t know how to write PHP as well to have an easy way to create widgets.</p>
<p>The first version of this plugin has support for the new PHP Class based widgets that were implemented in WordPress 2.8.  Though it does technically have support for WordPress 2.8, I focused on 2.9+.</p>
<p>I have already had some feedback from my co-workers, so a 1.1 release should be out soon.  It will have support for multiple folders, and also use native PHP functions for reading the files in the folders which should speed up rebuilding of the widgets.  I also plan on adding a disable feature for widgets that might not be needed right at the moment, but could be needed in the future.</p>
<p>Please let me know if you have any questions/suggestions regarding the plugin.  Feel free to download the plugin here: <a href="http://wordpress.org/extend/plugins/code-to-widget/">http://wordpress.org/extend/plugins/code-to-widget/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://seanklein.org/2010/05/code-to-widget-plugin-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TIL: Adding Admin Menu Pages</title>
		<link>http://seanklein.org/2009/07/til-adding-admin-menu-pages/</link>
		<comments>http://seanklein.org/2009/07/til-adding-admin-menu-pages/#comments</comments>
		<pubDate>Tue, 21 Jul 2009 16:29:56 +0000</pubDate>
		<dc:creator>Sean Klein</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Themes]]></category>
		<category><![CDATA[Things I've Learned]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[admin pages]]></category>

		<guid isPermaLink="false">http://seanklein.org/?p=32</guid>
		<description><![CDATA[When using functions like add_submenu_page etc, make sure that you add them at the admin_menu action. If you try to add them any place other than that you will get &#8220;Insufficient Privileges&#8221; errors when trying to go to the page. NOTE: If you are in WP 2.8 WordPress allows you to run those functions at&#8230;]]></description>
			<content:encoded><![CDATA[<p>When using functions like add_submenu_page etc, make sure that you add them at the admin_menu action.  If you try to add them any place other than that you will get &#8220;Insufficient Privileges&#8221; errors when trying to go to the page.</p>
<p>NOTE: If you are in WP 2.8 WordPress allows you to run those functions at admin_init, but don&#8217;t be fooled they will break again in WP 2.8.1.</p>
]]></content:encoded>
			<wfw:commentRss>http://seanklein.org/2009/07/til-adding-admin-menu-pages/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

