<?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>Mike Van WinkleWordPress Admin Makeover Coming in 3.2 | Mike Van Winkle</title>
	<atom:link href="http://www.mikevanwinkle.com/tag/development/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mikevanwinkle.com</link>
	<description>Wordpress/PHP Developer</description>
	<lastBuildDate>Tue, 31 Jan 2012 00:02:30 +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 Admin Makeover Coming in 3.2</title>
		<link>http://www.mikevanwinkle.com/wordpress/wordpress-admin-makeover-coming-in-3-2/</link>
		<comments>http://www.mikevanwinkle.com/wordpress/wordpress-admin-makeover-coming-in-3-2/#comments</comments>
		<pubDate>Sat, 07 May 2011 14:03:47 +0000</pubDate>
		<dc:creator>Mike Van Winkle</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[3.2]]></category>
		<category><![CDATA[cms]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[WordPress 3.2]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[WP 3.2]]></category>

		<guid isPermaLink="false">http://www.mikevanwinkle.com/?p=1019</guid>
		<description><![CDATA[I somehow had missed that WordPress 3.2 was going to feature a makeover of the WordPress admin theme. The new theme looks sharp. Here&#8217;s a preview. Let&#8217;s hope this doesn&#8217;t create issues with plugins.]]></description>
			<content:encoded><![CDATA[<p>I somehow had missed that WordPress 3.2 was going to feature a makeover of the WordPress admin theme. The new theme looks sharp. Here&#8217;s a preview. Let&#8217;s hope this doesn&#8217;t create issues with plugins.</p>

<a href='http://www.mikevanwinkle.com/wordpress/wordpress-admin-makeover-coming-in-3-2/attachment/screen-shot-2011-05-06-at-7-41-45-am/' title='WordPress Admin Preview'><img width="150" height="150" src="http://www.mikevanwinkle.com/wp-content/uploads/2011/05/Screen-shot-2011-05-06-at-7.41.45-AM-150x150.png" class="attachment-thumbnail" alt="WordPress Admin Preview" title="WordPress Admin Preview" /></a>
<a href='http://www.mikevanwinkle.com/wordpress/wordpress-admin-makeover-coming-in-3-2/attachment/screen-shot-2011-05-06-at-7-39-51-am/' title='WordPress Admin Preview'><img width="150" height="150" src="http://www.mikevanwinkle.com/wp-content/uploads/2011/05/Screen-shot-2011-05-06-at-7.39.51-AM-150x150.png" class="attachment-thumbnail" alt="WordPress Admin Preview" title="WordPress Admin Preview" /></a>
<a href='http://www.mikevanwinkle.com/wordpress/wordpress-admin-makeover-coming-in-3-2/attachment/screen-shot-2011-05-06-at-7-28-35-am/' title='Wordpress Admin Theme Preview'><img width="150" height="150" src="http://www.mikevanwinkle.com/wp-content/uploads/2011/05/Screen-shot-2011-05-06-at-7.28.35-AM-150x150.png" class="attachment-thumbnail" alt="Wordpress Admin Theme Preview" title="Wordpress Admin Theme Preview" /></a>

]]></content:encoded>
			<wfw:commentRss>http://www.mikevanwinkle.com/wordpress/wordpress-admin-makeover-coming-in-3-2/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Registration Forms: What&#8217;s New in 1.5</title>
		<link>http://www.mikevanwinkle.com/wordpress/registration-forms-whats-new-in-1-5/</link>
		<comments>http://www.mikevanwinkle.com/wordpress/registration-forms-whats-new-in-1-5/#comments</comments>
		<pubDate>Tue, 26 Oct 2010 13:23:45 +0000</pubDate>
		<dc:creator>Mike Van Winkle</dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[Registration Forms]]></category>
		<category><![CDATA[user management]]></category>
		<category><![CDATA[wordpress as cms]]></category>
		<category><![CDATA[WP]]></category>

		<guid isPermaLink="false">http://www.mikevanwinkle.com/?p=628</guid>
		<description><![CDATA[Last week I released version 1.5 of my Simplr Registration Forms plugin. The new version includes some big fixes and requested features. Particularly, this version now supports WP Multisite and has a few addition profile fields that can be added to the default form. It also includes better security, via WP nonces, and better field [...]]]></description>
			<content:encoded><![CDATA[<p>Last week I released version 1.5 of my <a title="WordPress registration forms" href="http://www.mikevanwinkle.com/wordpress/custom-wordpress-registration-page/">Simplr Registration Forms</a> plugin. The new version includes some big fixes and requested features. Particularly, this version now supports WP Multisite and has a few addition profile fields that can be added to the default form. It also includes better security, via WP nonces, and better field validation.</p>
<p>But the most important change is that it includes hooks and filters that allow it to be extended by you, the user.</p>
<p>For instance, let&#8217;s add a field to our form that requests the user&#8217;s zip code. First, in your functions.php file create a function for displaying the field:</p>
<pre>function sample_zip_field($form) {
 $form .=  '&lt;div&gt;';
 $form .=  '&lt;label for="zip"&gt;Zip Code:&lt;/label&gt;';
 $form .=  '&lt;input type="text" name="zip" value="'.$_POST['zip'] .'"/&gt;&lt;br/&gt;';
 $form .=  '&lt;/div&gt;';
 return $form;
}
</pre>
<p>Note that this function receives the parameter $form and then returns $form. Failing to return the form will make the entire registration form disappear. To add this form to the registration use:</p>
<pre>add_filter('simplr_add_form_fields', 'sample_zip_field');
</pre>
<p>But then we also need to make sure this data gets saved when the for gets saved. So you&#8217;ll need to create a function for that as well.</p>
<pre>function sample_save_meta($user_id) {
if(isset($_POST['zip'])) {
 add_user_meta($user_id, 'user_zip', $_POST['zip']);
 }
return $user_id;
}
</pre>
<p>Note that in order for this function to work properly it has to receive the $user_id. It is also good practice to return the $user_id at the end of the function, though not necessary.</p>
<p>To make sure your save function is called use the hook:</p>
<pre>add_action('simplr_profile_save_meta','sample_save_meta');
</pre>
<p>With these two &#8220;hooks&#8221;, you can customize the registration form however you want. You could even set up your field function to only display on certain pages, making it form-specific.</p>
<p>Finally, I&#8217;ve also added filters to the labels on the default form fields so you can change them at will. For instance, to change username to &#8220;screen name&#8221; use the following.</p>
<pre>function sample_label_username($label) {
 $label = "Screen name: ";
 return $label;
}
add_filter('simplr_label_username','sample_label_username');
</pre>
<p>I hope you find the changes useful.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mikevanwinkle.com/wordpress/registration-forms-whats-new-in-1-5/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>WordPress 2.8 Release &#8211; Widgets Upgraded Big Time</title>
		<link>http://www.mikevanwinkle.com/geek-think/wordpress-2-8-release/</link>
		<comments>http://www.mikevanwinkle.com/geek-think/wordpress-2-8-release/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 15:19:40 +0000</pubDate>
		<dc:creator>Mike Van Winkle</dc:creator>
				<category><![CDATA[Geek Think]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.mikevanwinkle.com/?p=259</guid>
		<description><![CDATA[WordPress 2.8 is finally out. There are some key improvements for the casual WordPress user including easier theme addition. Like plugins, you can now browse the WordPress.org theme gallery from within your WordPress admin screen. One click and your theme is installed. For the wordHeavy user, that is the designer/developer building their content management system [...]]]></description>
			<content:encoded><![CDATA[<p><a title="Wordpress 2.8 Released" href="http://wordpress.org/development/2009/06/wordpress-28/">WordPress 2.8 is finally out</a>. There are some key improvements for the casual WordPress user including easier theme addition. Like plugins, you can now browse the WordPress.org theme gallery from within your WordPress admin screen. One click and your theme is installed.</p>
<p>For the wordHeavy user, that is the designer/developer building their content management system on the wordpress platform, there isn&#8217;t all that much to be excited about. The easy theme feature is likely to further centralize theme development within the grips of WordPress.org theming rules. Not that there&#8217;s anything inherently wrong with this, I just worry about those designers who charge for their creations loosing market share to &#8220;free&#8221; themes.</p>
<p>Perhaps WordPress will come up with a more inclusive gallery system? Or maybe an enterprising developer will develop a competing gallery that can be installed with a simple plugin.</p>
<p>The one development I&#8217;m looking forward to using is the widgets. As a freelancer, you have clients who need a specific sidebar widget. A special campaign logo for instance. The need is small enough that it isn&#8217;t worth the time developing a custom plugin for the widget (even though it really doesn&#8217;t take that long). Instead, I routinely use simple text widgets to paste in the small bits of code.</p>
<p>Trouble is you can&#8217;t save a text widget for later use. So the client one day feels a little adventurous, start playing with widgets &#8230; they are fun to play with &#8230; and accidentally delete your modified text widget. Doh! Not that big of a deal, but a real pain in the ass.</p>
<p>But starting with 2.8, widgets can be made &#8220;inactive,&#8221; which means they are saved in the system. Sweet!!! Now all those little widgets can be safe from unnecessary annihilation at the hands of the unsophisticated end user.</p>
<p>Actually, they are not entirely safe. For some reason the WordPress developers didn&#8217;t take the next logical step. When you have a widget in the sidebar and click the &#8220;remove&#8221; action, the widget doesn&#8217;t dump into the inactive bin, it is DELETED! I think it would make sense for the to go to the inactive bin first and to have widgets only deleted from the inactive bin. That&#8217;s what I get for not keeping up with the WordPress developers email list. Oh well, maybe 2.9 right?</p>
<p>The other improvement on widget management is that you no longer have to click which sidebar you want to show. Nor do you have to save the widget (clicking the &#8220;done&#8221; button) and then also save the sidebar (clicking &#8220;save changes&#8221;). Now all the options and functionality are on one page. That reduces the number of needed clicks to add a widget by half. Little stuff for most, but big stuff for heavy WordPress users.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mikevanwinkle.com/geek-think/wordpress-2-8-release/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Object Caching 665/700 objects using apc

Served from: www.mikevanwinkle.com @ 2012-02-04 19:50:20 -->
